Conversation
Promote the Unreleased changelog block into a dated [0.1.0] section and bump build.zig.zon to match. This is the Release PR pattern: merging this PR finalizes the changelog and sets the package version, then pushing the v0.1.0 tag fires .github/workflows/release.yml, which produces zopa-v0.1.0.wasm with SLSA provenance and cosign signatures. The 0.1.0 entry pulls in everything that was sitting under Unreleased: the initial wasm32-freestanding build, the JSON parser and arena allocator, the policy AST, the proxy-wasm 0.2.1 lifecycle exports, the Node/wasmtime/Envoy integration tests, the new release pipeline, and the README badge fix.
|
Warning Rate limit exceeded
To continue reviewing without waiting, purchase usage credits in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. 📝 WalkthroughWalkthroughThe pull request bumps the package version from 0.0.0 to 0.1.0 in build metadata and adds corresponding release notes to the changelog documenting the initial stable release, including build artifacts, core features, exports, test coverage, and automated release infrastructure. ChangesRelease 0.1.0 Version Bump and Changelog
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request increments the project version to 0.1.0 in build.zig.zon and documents the first tagged release in CHANGELOG.md. Reviewers suggested enhancing the changelog by linking the 'Unreleased' section to a GitHub comparison and consolidating all link references at the bottom of the file for consistency.
…re link Address gemini-code-assist review on PR #4: - Promote 'Unreleased' to a linked header '[Unreleased]' so the GitHub v0.1.0...HEAD compare view is one click away. This is the same pattern Keep a Changelog uses on its own changelog and lets readers see what's queued for the next release without scrolling the file. - Move the kac/semver link references from the top of the file down to the link reference block at the bottom, alongside [Unreleased] and [0.1.0]. Mixing reference definitions across the top and bottom of a file makes them easy to drift out of sync; one block at the end is the convention Keep a Changelog itself follows.
1 participant
Summary
Release PR for v0.1.0, the first tagged release of zopa. This is the Keep a Changelog "promote Unreleased to a dated section" step that has to land before we push the
v0.1.0tag.## [0.1.0] - 2026-05-07, leaving an empty Unreleased on top for the next cycle.build.zig.zonversionfrom0.0.0to0.1.0so the package metadata matches the tag.[0.1.0]link reference at the bottom of CHANGELOG pointing at the GitHub Releases page (which the release workflow will populate once the tag fires).Why a separate PR
zopa follows Keep a Changelog. The convention is: implementation lands under
## Unreleased, then on release-day a Release PR promotes that block to a versioned section and bumps anyversion =field in the build manifest. The dated, frozen[0.1.0]section becomes the canonical changelog entry going forward, whileUnreleasedstays empty until the next feature lands. This separation also gives reviewers a single, reviewable artifact ("here's what's going out as 0.1.0") instead of having the version cut hidden inside an unrelated PR.What 0.1.0 contains (now frozen in the changelog)
Inherited from #3, which merged to main right before this PR:
wasm32-freestandingbuild (~50 KB), in-tree JSON parser, per-request arena allocatorv*tags with SLSA v1.0 build provenance and cosign keyless signatureskanywst/zopa→0-draft/zopa)Tag flow after merge
git checkout main && git pull git tag v0.1.0 git push origin v0.1.0That fires
.github/workflows/release.ymland produceszopa-v0.1.0.wasm+.sha256+.sigstore.json+.intoto.jsonlon the GitHub Releases page. The[0.1.0]link reference at the bottom of CHANGELOG will start resolving once the release page exists.Test plan
Summary: 0 error(s))build.zig.zonbuild/provenance/sign/release) go green and the four artifacts are attachedcosign verify-blobandslsa-verifier verify-artifactsucceed against the publishedv0.1.0artifactsSummary by CodeRabbit
New Features
Bug Fixes