chore: sync release-please manifest + version files to 0.8.1#106
Merged
Conversation
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).
|
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 PR bumps the version from 0.8.0 to 0.8.1 across the release-please manifest, build.zig.zon, README.md, and docs/content/docs/installation.mdx, updating tag references and version fields consistently. ChangesVersion bump
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
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
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.
Follow-up to #105.
Why
v0.8.1was hand-tagged out-of-band at0b5a320(#104, the KMS fix) soperpcity-zig-sdkcould bump -- and that happened after #105 had already syncedmainto0.8.0. Somain's manifest is one version behind the latest tag: the exact drift #105 fixed, shifted up a notch.v0.8.1tag (#104)main(pre-this-PR)main(this PR)What
Bump the manifest + the three release-please
extra-files(build.zig.zon,README.md,docs/content/docs/installation.mdx)0.8.0 -> 0.8.1to match the existingv0.8.1tag.Effect on release-please
Now that the org "Allow GitHub Actions to create and approve PRs" setting is enabled, merging this lets release-please:
0.8.1as already released (thev0.8.1tag exists at0b5a320),release-please--branches--mainbranch, and0.8.2for the next realfeat:/fix:change.It does not re-tag or move
v0.8.1-- that tag is load-bearing (pinned byperpcity-zig-sdkandgator-liquidatorsat its exact SHA).Not in scope (follow-up)
Backfilling the missing
v0.8.0+v0.8.1GitHub Releases (git tags exist, but no GitHub Release for either).Verification
ZIG=$HOME/.zig-0.16.0/zig make ci(build +fmt --check+ test) -- green.0.8.0refs remain in the four tracked files.Summary by CodeRabbit