Skip to content

chore: sync release-please manifest + version files to 0.8.1#106

Merged
koko1123 merged 1 commit into
mainfrom
koko/release-please-manifest-sync-081
Jul 10, 2026
Merged

chore: sync release-please manifest + version files to 0.8.1#106
koko1123 merged 1 commit into
mainfrom
koko/release-please-manifest-sync-081

Conversation

@koko1123

@koko1123 koko1123 commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Follow-up to #105.

Why

v0.8.1 was hand-tagged out-of-band at 0b5a320 (#104, the KMS fix) so perpcity-zig-sdk could bump -- and that happened after #105 had already synced main to 0.8.0. So main's manifest is one version behind the latest tag: the exact drift #105 fixed, shifted up a notch.

ref manifest build.zig.zon
v0.8.1 tag (#104) 0.7.0 0.7.0
main (pre-this-PR) 0.8.0 0.8.0
main (this PR) 0.8.1 0.8.1

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.1 to match the existing v0.8.1 tag.

Effect on release-please

Now that the org "Allow GitHub Actions to create and approve PRs" setting is enabled, merging this lets release-please:

  • treat 0.8.1 as already released (the v0.8.1 tag exists at 0b5a320),
  • retire its stranded release-please--branches--main branch, and
  • cleanly propose 0.8.2 for the next real feat:/fix: change.

It does not re-tag or move v0.8.1 -- that tag is load-bearing (pinned by perpcity-zig-sdk and gator-liquidators at its exact SHA).

Not in scope (follow-up)

Backfilling the missing v0.8.0 + v0.8.1 GitHub 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.
  • No stray 0.8.0 refs remain in the four tracked files.

Summary by CodeRabbit

  • Chores
    • Bumped the project version to 0.8.1.
  • Documentation
    • Updated installation instructions to reference v0.8.1 in the README and docs.
    • Adjusted the build dependency example to match the new release version.

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).
@vercel

vercel Bot commented Jul 9, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
eth-zig Ready Ready Preview, Comment Jul 9, 2026 7:45pm

Request Review

@coderabbitai

coderabbitai Bot commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Review Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 7537ca9b-2100-4088-a8c1-639de8cc5667

📥 Commits

Reviewing files that changed from the base of the PR and between 5f6edab and f2bcebf.

📒 Files selected for processing (4)
  • .github/.release-please-manifest.json
  • README.md
  • build.zig.zon
  • docs/content/docs/installation.mdx

📝 Walkthrough

Walkthrough

This 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.

Changes

Version bump

Layer / File(s) Summary
Update version references to 0.8.1
.github/.release-please-manifest.json, build.zig.zon, README.md, docs/content/docs/installation.mdx
Version strings and v0.8.0 tag references are updated to 0.8.1/v0.8.1 in the manifest, build config version field, and installation snippets in README and docs.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Possibly related PRs

  • StrobeLabs/eth.zig#101: Same pattern of syncing the release-please manifest version with README, build.zig.zon, and docs version references.
  • StrobeLabs/eth.zig#94: Prior version-alignment update to the same set of files (v0.6.0→v0.7.0).
  • StrobeLabs/eth.zig#90: Prior analogous version bump across build.zig.zon, README, and docs installation page.
🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly matches the PR’s main change: syncing release-please and versioned files to 0.8.1.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch koko/release-please-manifest-sync-081

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

@koko1123
koko1123 merged commit 2860a47 into main Jul 10, 2026
13 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