Skip to content

chore(main): release cachekit-core 0.2.1#38

Merged
27Bslash6 merged 2 commits into
mainfrom
release-please--branches--main--components--cachekit-core
Jun 6, 2026
Merged

chore(main): release cachekit-core 0.2.1#38
27Bslash6 merged 2 commits into
mainfrom
release-please--branches--main--components--cachekit-core

Conversation

@cachekit-release-bot

@cachekit-release-bot cachekit-release-bot Bot commented May 31, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

0.2.1 (2026-05-31)

Bug Fixes

  • use local> preset ref for private renovate-config repo (#29) (80355a4)

Security

  • seed nonce instance counter with 8 random bytes, raising cross-process collision resistance from 2^32 to 2^64 (HIGH-2/HIGH-3) (#36) (af3d5fe)

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 to main.

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.
@27Bslash6

Copy link
Copy Markdown
Contributor

@coderabbitai full review

(Manual CHANGELOG patch a65751f added a ### Security entry for the #36 nonce fix that release-please dropped; requesting fresh approval to satisfy last-push-approval before merge.)

@coderabbitai

coderabbitai Bot commented Jun 6, 2026

Copy link
Copy Markdown

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



@27Bslash6 Full review of the four changed files:

File Change Status
.release-please-manifest.json "0.2.0""0.2.1"
Cargo.toml version = "0.2.0""0.2.1"
Cargo.lock cachekit-core version 0.2.0"0.2.1"
CHANGELOG.md 0.2.1 entry added with Bug Fixes + Security sections

All four version references are mutually consistent at 0.2.1.

The manually patched ### Security entry in commit a65751f is accurate — it correctly cites PR #36, commit af3d5fe, and the description (nonce instance counter seeded with 8 random bytes, 2³²→2⁶⁴ cross-process collision resistance, HIGH-2/HIGH-3) matches the squash-merged fix. The > encoding for > in the local> renovate-config entry is standard release-please output and not a defect.

No issues found. Approving.

[approve]

@27Bslash6

Copy link
Copy Markdown
Contributor

@coderabbitai approve

@coderabbitai

coderabbitai Bot commented Jun 6, 2026

Copy link
Copy Markdown
✅ Action performed

Comments resolved and changes approved.

@27Bslash6 27Bslash6 merged commit a7737ec into main Jun 6, 2026
30 checks passed
@27Bslash6 27Bslash6 deleted the release-please--branches--main--components--cachekit-core branch June 6, 2026 00:27
@cachekit-release-bot

Copy link
Copy Markdown
Contributor Author

🤖 Created releases:

🌻

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant