Skip to content

chore: release main#54

Closed
cachekit-release-bot[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main
Closed

chore: release main#54
cachekit-release-bot[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main

Conversation

@cachekit-release-bot
Copy link
Copy Markdown

🤖 I have created a release beep boop

cachekit: 0.1.3

0.1.3 (2026-05-17)

Features

  • CachekitIO backend full parity — session, metrics, SSRF, errors, locking, TTL (985cf09)
  • CachekitIO backend full parity (session, metrics, SSRF, locking, TTL) (d408364)
  • initial commit (048585c)
  • intent-based cache API (createCache.io, .minimal, .production, .secure) (#42) (c551bfb)
  • wire ByteStorage into cache pipeline for protocol-compliant wire format (#27) (d246294)
cachekit-core-ts: 0.1.3

0.1.3 (2026-05-17)

Features

  • CachekitIO backend full parity (session, metrics, SSRF, locking, TTL) (d408364)
  • initial commit (048585c)
  • wire ByteStorage into cache pipeline for protocol-compliant wire format (#27) (d246294)

This PR was generated with Release Please. See documentation.

@coderabbitai
Copy link
Copy Markdown

coderabbitai Bot commented May 17, 2026

Important

Review skipped

Bot user detected.

To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Free

Run ID: 98951c09-cf86-4a51-a0cf-86643e13c182

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

  • 🔍 Trigger review

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

@27Bslash6
Copy link
Copy Markdown
Contributor

Bogus PR from release-please during the 0.1.2 bootstrap (manifest claimed 0.1.2 before the cachekit-v0.1.2 GitHub release existed; release-please scanned old commits between 0.1.1 tag and HEAD and proposed 0.1.3 from them). Closing — future commits in package paths will trigger clean release-please PRs.

@27Bslash6 27Bslash6 closed this May 17, 2026
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