Skip to content

chore: release 0.3.0 - #36

Merged
luckyPipewrench merged 1 commit into
mainfrom
chore/release-0.3.0
Jul 25, 2026
Merged

luckyPipewrench merged 1 commit into
mainfrom
chore/release-0.3.0

Conversation

@luckyPipewrench

Copy link
Copy Markdown
Member

What this does

Prepares the 0.3.0 release and records what changed since the last published version.

0.2.0 was never published. It carries a version in pyproject.toml and a changelog entry, but there is no v0.2.0 tag and nothing on PyPI. Anyone upgrading from 0.1.1 therefore picks up both the v2 evidence receipt support described under 0.2.0 and the parity work landed since, so the changelog entry says that plainly rather than leaving people to work it out.

A gap this surfaced

The declared version lived in two places and only one of them was ever checked. The release workflow compares the git tag against pyproject.toml. Nothing compared pyproject.toml against the version the package reports about itself, which is a separate hard-coded string. The package could have shipped announcing a version it was not, and at 0.2.0 it already disagreed.

A test now asserts the two agree. It was verified by making them disagree and confirming it fails.

The version is parsed with a regex rather than tomllib, because tomllib is 3.11 and up while this package still supports 3.10 and CI tests it.

Also

Removes hard-coded version numbers from comments and from the error message about v2 chain support, so they cannot go stale at the next bump.

Verification

The distributions build and pass the packaging check. The installed artifact reports 0.3.0 and still verifies the captured release-binary chain with the expected root hash.

Bumps the packaging version and records what changed since the last published release.

The declared version lived in two places and only one of them was checked. The release workflow compares the git tag against pyproject.toml, and nothing compared pyproject.toml against the version the package reports about itself, so it could ship announcing a version it was not. A test now asserts the two agree, verified by making them disagree and watching it fail.

Also removes hard-coded version numbers from comments and from an error message about v2 chain support, so those cannot go stale at the next bump.
@coderabbitai

coderabbitai Bot commented Jul 25, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@luckyPipewrench, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 8 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 9b0662f2-a1da-416b-8435-c61e4195f5f4

📥 Commits

Reviewing files that changed from the base of the PR and between fc16c53 and 3c669b6.

📒 Files selected for processing (6)
  • CHANGELOG.md
  • pipelock_verify/__init__.py
  • pipelock_verify/_evidence.py
  • pipelock_verify/_verify.py
  • pyproject.toml
  • tests/test_regressions.py
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/release-0.3.0

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@luckyPipewrench
luckyPipewrench merged commit d2e0d47 into main Jul 25, 2026
14 checks passed
@luckyPipewrench
luckyPipewrench deleted the chore/release-0.3.0 branch July 25, 2026 01:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant