Skip to content

Repository navigation

chore: bump salt version to 1.0.6 #151

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
flyq merged 1 commit into from
Sep 2, 2026
Merged

chore: bump salt version to 1.0.6 #151

Show file tree
Hide file tree
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.lock
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion salt/Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
[package]
name = "salt"
version = "1.0.5"
version = "1.0.6"

@chatgpt-codex-connector chatgpt-codex-connector Bot Aug 31, 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.

P1 Badge Use a breaking version for the new public error variant

When a downstream crate specifies a semver-compatible requirement such as salt = "1.0.5" and exhaustively matches the public SaltError enum, Cargo may upgrade it to 1.0.6, but compilation will then fail because this release adds SaltError::UnchainedTransition to an enum that is not marked #[non_exhaustive]. Publish these changes under a breaking version, or avoid extending the exhaustive public enum, so a nominally compatible patch update cannot break downstream builds.

Useful? React with 👍 / 👎.

edition = "2021"

[dependencies]
Expand Down
Loading