Skip to content

release: bump workspace version to 0.2.7#60

Merged
lunarthegrey merged 1 commit into
mainfrom
chore/bump-0.2.7
May 20, 2026
Merged

release: bump workspace version to 0.2.7#60
lunarthegrey merged 1 commit into
mainfrom
chore/bump-0.2.7

Conversation

@lunarthegrey
Copy link
Copy Markdown
Contributor

Summary

Slice 1-6 (PR #52, RFC 7911 ADD-PATH + LP-tier ECMP aggregation) merged without a corresponding workspace version bump. The v0.2.7 release tag was cut against main afterwards, but the published .deb's binary reports --version as 0.2.6 because the source still carried that string in Cargo.toml and VERSION.

This commit bumps both files to 0.2.7 so a re-cut tag produces a binary whose --version matches its package label.

Plan after merge

  1. Delete the existing v0.2.7 release + tag.
  2. Re-tag v0.2.7 at this commit on main.
  3. Push, release workflow re-runs.

Test plan

  • CI: fmt + clippy + test, four cross-builds, two qemu-verifier kernels.
  • After re-release: dpkg -i packetframe_0.2.7_arm64.deb && packetframe --version reports 0.2.7.

Slice 1-6 (RFC 7911 ADD-PATH + LP-tier ECMP aggregation) merged in
PR #52 without a corresponding workspace version bump, so the
binary built from the v0.2.7 tag reported `--version` as 0.2.6.
Bump Cargo.toml and VERSION so the tag's release matches what
`packetframe --version` prints.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@lunarthegrey lunarthegrey merged commit 6298940 into main May 20, 2026
9 checks passed
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