Skip to content

chore: bump version to 0.2.2 #10

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
prom3theu5 merged 1 commit into from
Jun 2, 2026
Merged

chore: bump version to 0.2.2 #10

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "synapse"
version = "0.2.1"
version = "0.2.2"

@qodo-code-review qodo-code-review Bot Jun 2, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Action required

1. Cargo.lock not updated 🐞 Bug ☼ Reliability

Cargo.toml bumps synapse to 0.2.2 but Cargo.lock still records the root package as 0.2.1, making
the lockfile inconsistent with the manifest. CI/release workflows use --locked, so Cargo will fail
with “lock file needs to be updated but --locked was passed”.
Agent Prompt 
## Issue description
`Cargo.toml` was updated to version 0.2.2, but `Cargo.lock` still contains the root package entry for `synapse` at 0.2.1. Since CI/release runs Cargo with `--locked`, the build/test will fail if the lockfile is considered out-of-date.

## Issue Context
The repo’s CI (`cargo test --locked`) and release workflow (`cargo build --locked`) require a lockfile that matches the manifest.

## Fix Focus Areas
- Cargo.lock[1989-2026]
- .github/workflows/ci.yml[43-46]
- .github/workflows/release.yml[62-66]

## Recommended fix
1. Regenerate/update the lockfile after the version bump (e.g., run `cargo generate-lockfile` or run a normal `cargo build` once to let Cargo rewrite the lockfile).
2. Commit the resulting `Cargo.lock` changes so `--locked` workflows pass.

ⓘ Copy this prompt and use it to remediate the issue with your preferred AI generation tools

edition = "2024"

[[bin]]
Expand Down
Loading