chore(main): release cachekit-core 0.2.1 - #38
Conversation
The Phase 1 bedrock PR squash-merged as `perf/security:`, which is not a valid Conventional Commit type, so release-please neither bumped for it nor listed it. The HIGH-2/HIGH-3 nonce-seed fix ships in the 0.2.1 code; this adds the Security entry so the release notes reflect that.
|
@coderabbitai full review (Manual CHANGELOG patch a65751f added a |
|
Tip For best results, initiate chat on the files or code changes. 🧩 Analysis chain🏁 Script executed: #!/bin/bash
# Get PR details
gh pr view 38 --repo cachekit-io/cachekit-core
echo "---FILES CHANGED---"
gh pr diff 38 --repo cachekit-io/cachekit-core
echo "---COMMITS---"
gh pr view 38 --repo cachekit-io/cachekit-core --json commits --jq '.commits[] | {oid: .oid, message: .messageHeadline}'Length of output: 4173
All four version references are mutually consistent at The manually patched No issues found. Approving. [approve] |
|
@coderabbitai approve |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
✅ Action performedComments resolved and changes approved. |
|
🤖 Created releases: 🌻 |
cachekit-release-bot
Bot
added
autorelease: tagged
and removed
autorelease: pending
labels
…non-release pushes (#58) Step env: templates are evaluated when the step is materialized, regardless of the if: guard. On any push to main where release-please creates/updates no release PR, steps.release.outputs.pr is empty and fromJson('') throws a template error that fails the release-please job — which skips the publish job (needs: release-please). Since the push that merges a release PR also has an empty pr output, the next real release would tag on GitHub but never publish to crates.io. Select the release PR by release-please's deterministic head branch (release-please--branches--main--components--cachekit-core, verified against release PRs #38 and #49) instead of parsing the PR number in a template position that can see an empty string. Closes LAB-865
1 participant
🤖 I have created a release beep boop
0.2.1 (2026-05-31)
Bug Fixes
Security
This PR was generated with Release Please. See documentation.
Note
Security entry added manually: #36 squash-merged as
perf/security:(not a valid Conventional Commit type), so release-please did not auto-list it. The fix is in the 0.2.1 code. Do not let release-please regenerate this PR before merging — merge it before any other push tomain.