release: 2.2.0-beta.1 & 0.2.0-beta.1

[dev-jodee]

Important

Update version numbers to 2.2.0-beta.1 for Rust components and 0.2.0-beta.1 for TypeScript SDK in preparation for release.

• Version Updates:
  • Update version to 2.2.0-beta.1 in Cargo.toml, crates/cli/Cargo.toml, and crates/lib/Cargo.toml.
  • Update version to 0.2.0-beta.1 in sdks/ts/package.json.
• Changelog:
  • Add entry for 2.2.0-beta.1 in CHANGELOG.md with placeholders for bug fixes, documentation, features, and refactoring.

^{This description was created by for 8850bcc. You can customize this summary. It will automatically update as commits are pushed.}

---

📊 Unit Test Coverage

Unit Test Coverage: 81.0%

View Detailed Coverage Report

[github-actions]

📊 TypeScript Coverage Report

Coverage: 82.5%

View detailed report

Coverage artifacts have been uploaded to this workflow run.
View Artifacts

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 83d7555 in 2 minutes and 12 seconds. Click for details.

• Reviewed 142 lines of code in 6 files
• Skipped 0 files when reviewing.
• Skipped posting 5 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. Cargo.toml:15

• Draft comment:
  Workspace Cargo.toml configuration is consistent with the beta update.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

2. crates/cli/Cargo.toml:13

• Draft comment:
  CLI Cargo.toml correctly uses workspace deps; verify the 'docs' feature path 'kora-lib/docs' is intended.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50% None

3. crates/lib/Cargo.toml:1

• Draft comment:
  Library Cargo.toml is updated and uses workspace dependencies; ensure 'unsafe-debug' is not enabled in production.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

4. sdks/ts/package.json:1

• Draft comment:
  TypeScript SDK package.json updated to beta; review scripts and peerDependencies for beta consistency.
• Reason this comment was not posted:
  Confidence changes required: 0% <= threshold 50% None

5. CHANGELOG.md:30

• Draft comment:
  Typo detected: The word "paymen…" seems to be truncated and might be intended to be "payment". Please verify and correct.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 15% vs. threshold = 50% This is a changelog file, and the entry appears to reference PR #286. The truncation with "…" is likely intentional - either the changelog was auto-generated and truncated long titles, or the author intentionally abbreviated it. Changelog entries often have truncated descriptions with ellipses. The comment is technically correct that there's a truncation, but this may be intentional formatting. More importantly, this violates the rule about not making comments on obvious or unimportant issues. A truncated word in a changelog entry is not a critical issue that requires a code change. The PR reference (#286) is still there, so anyone can look up the full details if needed. The truncation might actually be unintentional and could be a real typo that should be fixed for clarity. Changelogs are user-facing documentation, and having clear, complete descriptions is important for users understanding what changed in the release. While changelogs are user-facing, the truncation includes an ellipsis which suggests it's intentional, and the PR number (#286) provides a way to get full details. This is a minor documentation issue at best, and falls under "obvious or unimportant" comments that should not be made. The comment also asks the author to "verify and correct" which is asking them to confirm intention, violating the rules. This comment should be deleted. It's about a minor truncation in a changelog entry that appears intentional (includes ellipsis), and the comment asks the author to "verify" which violates the rule against asking for confirmation. This is an unimportant issue that doesn't require a code change.

Workflow ID: wflow_mO9p6phf5UTJITzZ

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed 8850bcc in 2 minutes and 2 seconds. Click for details.

• Reviewed 52 lines of code in 1 files
• Skipped 0 files when reviewing.
• Skipped posting 4 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. CHANGELOG.md:4

• Draft comment:
  Duplicate bug fix sections: '### Bug Fixes' (L4) and '### Bugfix' (L17) seem redundant. Consider consolidating them for consistency.
• Reason this comment was not posted:
  Comment was on unchanged code.

2. CHANGELOG.md:7

• Draft comment:
  Several sections (Documentation, Refactoring, and Bugfix) are empty in release 2.2.0-beta.1. Consider removing these empty headers to improve clarity.
• Reason this comment was not posted:
  Comment was on unchanged code.

3. CHANGELOG.md:12

• Draft comment:
  Only one feature appears for 2.2.0-beta.1. Please verify that other removed entries (bug fixes, documentation, workflow updates) have been correctly reallocated to their intended releases.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50% This comment is asking the PR author to verify that other entries have been correctly reallocated, which violates the rule against asking the author to confirm or verify things. It does not provide a specific suggestion or point out a specific issue with the code.

4. CHANGELOG.md:25

• Draft comment:
  The prerelease detection entry was shortened for 2.1.0-beta.0 (omitting '& pre-release beta publish'). Confirm that this update accurately reflects the intended changes.
• Reason this comment was not posted:
  Comment was not on a location in the diff, so it can't be submitted as a review comment.

Workflow ID: wflow_Cd2vBIb8pcDQAr8c

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}