Skip to content

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

Open
cachekit-release-bot[bot] wants to merge 2 commits into
mainfrom
release-please--branches--main--components--cachekit-core
Open

chore(main): release cachekit-core 0.2.1#38
cachekit-release-bot[bot] wants to merge 2 commits into
mainfrom
release-please--branches--main--components--cachekit-core

Conversation

@cachekit-release-bot
Copy link
Copy Markdown
Contributor

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

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