release: v0.1.0 - #4
Conversation
Cut the 0.1.0 changelog entry from Unreleased and add comparison links. package.json is already at 0.1.0; merging this PR and tagging v0.1.0 triggers the npm publish workflow. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Free Run ID: 📒 Files selected for processing (1)
Walkthrough
ChangesCHANGELOG 0.1.0 Release Entry
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Poem
Note 🎁 Summarized by CodeRabbit FreeYour organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Pro by visiting https://app.coderabbit.ai/login. Comment |
Deploying with
|
| Status | Name | Latest Commit | Updated (UTC) |
|---|---|---|---|
| ✅ Deployment successful! View logs |
drizzle-kv-cache-docs | 2ead7c4 | Jun 20 2026, 06:05 PM |
Initial public release of drizzle-cloudflare-kv-cache-adapter.
Changes
0.1.0entry inCHANGELOG.md(from[Unreleased]) dated 2026-06-20, with compare/release links.package.jsonis already at0.1.0.Release steps (after merge)
main.release.ymlworkflow runs typecheck + test + build, thennpm publish --provenance --access public.The
NPM_TOKENrepository secret must be set, or the publish step will fail.What ships to npm
ESM build + types only:
dist/,README.md,LICENSE(verified earlier viabun pm pack).🤖 Generated with Claude Code
Summary by CodeRabbit