chore: sync release-please manifest + version files to 0.8.0#105
Merged
Conversation
v0.8.0 was cut out-of-band (git tag on 8c9a20d / #103 only, no GitHub Release), so release-please's manifest and the version-marked extra-files were never bumped and stayed at 0.7.0. With the manifest at 0.7.0, release-please recomputes 0.8.0 from the feat commits since v0.7.0 and collides with the existing v0.8.0 tag ("proposes wrong versions"). Adopt v0.8.0 as the released version by bumping the manifest plus the three release-please extra-files (build.zig.zon, README.md, installation.mdx) to match the existing tag. After this merges, release-please diffs from v0.8.0 and proposes 0.8.1 for the #104 fix. Also fixes build.zig.zon self-reporting 0.7.0 while downstream (gator, perpcity-zig-sdk) pins v0.8.0. Does not delete the v0.8.0 tag (load-bearing: downstream pins its SHA) and leaves CHANGELOG.md for the separate v0.8.0 GitHub Release backfill.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (4)
📝 WalkthroughWalkthroughThis pull request bumps the eth.zig version reference from 0.7.0 to 0.8.0 across the release manifest, build.zig.zon package version, and documentation (README.md and installation.mdx), including fetch commands and dependency URL examples. ChangesVersion Bump
Estimated code review effort: 1 (Trivial) | ~3 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
koko1123
added a commit
that referenced
this pull request
Jul 10, 2026
Follow-up to #105. v0.8.1 was hand-tagged out-of-band at 0b5a320 (#104, the KMS fix) after #105 had already synced main to 0.8.0, leaving main's manifest one version behind the latest tag -- the same drift #105 fixed, shifted up a notch. Bump the manifest and the three release-please extra-files (build.zig.zon, README.md, installation.mdx) 0.8.0 -> 0.8.1 to match the existing v0.8.1 tag. With the org "Actions can create PRs" setting now enabled, this lets release-please treat 0.8.1 as already released (tag exists at 0b5a320), retire its stranded release-please--branches--main branch, and cleanly propose 0.8.2 for the next real change -- without re-tagging the load-bearing v0.8.1 (pinned by perpcity-zig-sdk and gator).
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Release Please can't cut releases for eth.zig. Two independent causes; this PR fixes one of them (the version desync). The other — the org setting Allow GitHub Actions to create and approve pull requests being off — must be toggled separately in GitHub settings.
v0.8.0was cut out-of-band: only a git tag (8c9a20d, #103) was pushed, with no GitHub Release, so Release Please's manifest and the version-marked files were never bumped and stayed at0.7.0:.github/.release-please-manifest.json->0.7.0build.zig.zon.version->0.7.0README.md/docs/content/docs/installation.mdxinstall snippets ->#v0.7.0With the manifest at
0.7.0, Release Please recomputes0.8.0from the feat commits sincev0.7.0and collides with the existingv0.8.0tag -- i.e. it proposes a version that's already been cut.Fix
Adopt
v0.8.0as the released version by manually doing what Release Please's release PR would have done: bump the manifest and the threeextra-filesto0.8.0. After merge, Release Please diffs from thev0.8.0tag and proposes0.8.1for thefix:in #104 (once the org PR-creation setting is enabled).This also fixes the real bug that
build.zig.zonself-reports0.7.0while downstream consumers (gator-liquidators,perpcity-zig-sdk) pin?ref=v0.8.0#8c9a20d....Scope / non-goals
v0.8.0tag -- it's load-bearing (downstream pins its exact SHA).CHANGELOG.mdalone -- its[Unreleased]block holds v0.8.0's content (kzg Add real EIP-4844 KZG support (vendored blst + c-kzg-4844) #99, abigen Add abigen state-changing writes via Wallet (extends #68) #98, signer Add Signer abstraction with LocalSigner and AWS KMS-backed KmsSigner #103) and belongs in the separatev0.8.0GitHub Release backfill, not this metadata-only change.Verification
ZIG=$HOME/.zig-0.16.0/zig make ci(build +fmt --check+ test) -- green.rg "v?0.7.0"across the four tracked files -- no stray refs remain.Summary by CodeRabbit