Skip to content

chore: bump version to 2.2.0-alpha.1#383

Merged
tobyhede merged 1 commit intomainfrom
release/2.2.0-alpha.1
Mar 25, 2026
Merged

chore: bump version to 2.2.0-alpha.1#383
tobyhede merged 1 commit intomainfrom
release/2.2.0-alpha.1

Conversation

@tobyhede
Copy link
Copy Markdown
Contributor

@tobyhede tobyhede commented Mar 25, 2026

Summary

  • Bump workspace version to 2.2.0-alpha.1
  • Bump cipherstash-proxy package version to 2.2.0-alpha.1
  • Update CHANGELOG.md for 2.2.0-alpha.1

Post-merge

After merge, tag and release from main:

mise run release v2.2.0-alpha.1

Summary by CodeRabbit

  • Changed
    • Version updated to 2.2.0-alpha.1 (alpha release)
    • Changelog updated with release entry 2.2.0-alpha.1 (2026-03-25)
    • Log target renamed: KEYSET → ZEROKMS
    • Environment variable CS_LOG__KEYSET_LEVEL renamed to CS_LOG__ZEROKMS_LEVEL — update your configuration accordingly

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Mar 25, 2026

Warning

Rate limit exceeded

@tobyhede has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 19 minutes and 1 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b931e234-e2df-49ea-8409-0e8af9faacba

📥 Commits

Reviewing files that changed from the base of the PR and between e95577a and 6654068.

⛔ Files ignored due to path filters (1)
  • Cargo.lock is excluded by !**/*.lock
📒 Files selected for processing (3)
  • CHANGELOG.md
  • Cargo.toml
  • packages/cipherstash-proxy/Cargo.toml
📝 Walkthrough

Walkthrough

The PR bumps workspace and crate versions to 2.2.0-alpha.1 and adds a CHANGELOG release entry documenting a log target rename KEYSETZEROKMS and environment variable rename CS_LOG__KEYSET_LEVELCS_LOG__ZEROKMS_LEVEL.

Changes

Cohort / File(s) Summary
Version Updates
Cargo.toml, packages/cipherstash-proxy/Cargo.toml
Updated workspace package version and cipherstash-proxy crate version from 2.1.x → 2.2.0-alpha.1.
Release Documentation
CHANGELOG.md
Added [2.2.0-alpha.1] - 2026-03-25 entry under Unreleased; documented log target rename (KEYSETZEROKMS) and env var rename (CS_LOG__KEYSET_LEVELCS_LOG__ZEROKMS_LEVEL).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

Poem

🐰 I hopped a version up today,
Alpha bells in springtime play,
KEYSET renamed to ZEROKMS bright,
Env vars follow — snug and right,
A tiny hop, release in sight. 🌱🐇

🚥 Pre-merge checks | ✅ 3
✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately and concisely summarizes the main change: bumping the version to 2.2.0-alpha.1, which is confirmed by all three modified files (Cargo.toml, packages/cipherstash-proxy/Cargo.toml, and CHANGELOG.md).
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch release/2.2.0-alpha.1

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@freshtonic
Copy link
Copy Markdown
Contributor

@tobyhede looks like you need to run a build then also commit the lock file

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
CHANGELOG.md (1)

252-252: ⚠️ Potential issue | 🟡 Minor

Update version link references.

The [Unreleased] comparison link should point to the newly released version v2.2.0-alpha.1 instead of v2.1.20, and a new link reference for [2.2.0-alpha.1] should be added.

🔗 Proposed fix to add missing version links
-[Unreleased]: https://github.com/cipherstash/proxy/compare/v2.1.20...HEAD
+[Unreleased]: https://github.com/cipherstash/proxy/compare/v2.2.0-alpha.1...HEAD
+[2.2.0-alpha.1]: https://github.com/cipherstash/proxy/compare/v2.1.22...v2.2.0-alpha.1
+[2.1.22]: https://github.com/cipherstash/proxy/compare/v2.1.21...v2.1.22
 [2.1.20]: https://github.com/cipherstash/proxy/releases/tag/v2.1.20
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@CHANGELOG.md` at line 252, Update the CHANGELOG link reference for
[Unreleased] to compare v2.2.0-alpha.1...HEAD instead of v2.1.20 and add a new
link reference entry for [2.2.0-alpha.1] that points to the appropriate tag
comparison (e.g., v2.1.20...v2.2.0-alpha.1 or the repo tag URL), making sure the
link text “[Unreleased]” and the new “[2.2.0-alpha.1]” reference are
added/updated so the markdown link references resolve correctly.
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@CHANGELOG.md`:
- Line 252: Update the CHANGELOG link reference for [Unreleased] to compare
v2.2.0-alpha.1...HEAD instead of v2.1.20 and add a new link reference entry for
[2.2.0-alpha.1] that points to the appropriate tag comparison (e.g.,
v2.1.20...v2.2.0-alpha.1 or the repo tag URL), making sure the link text
“[Unreleased]” and the new “[2.2.0-alpha.1]” reference are added/updated so the
markdown link references resolve correctly.

ℹ️ Review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 1618b54f-9a53-4788-8890-0c3bd9901584

📥 Commits

Reviewing files that changed from the base of the PR and between 5103ece and 768a34e.

📒 Files selected for processing (3)
  • CHANGELOG.md
  • Cargo.toml
  • packages/cipherstash-proxy/Cargo.toml

@tobyhede tobyhede force-pushed the release/2.2.0-alpha.1 branch from 813cd23 to e95577a Compare March 25, 2026 01:00
@tobyhede tobyhede force-pushed the release/2.2.0-alpha.1 branch from e95577a to 6654068 Compare March 25, 2026 01:04
@tobyhede tobyhede merged commit 6906b18 into main Mar 25, 2026
6 checks passed
@tobyhede tobyhede deleted the release/2.2.0-alpha.1 branch March 25, 2026 01:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants