Skip to content

ostree-ext: specify zeroed patch version for ostree #1365

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

Closed
jeckersb wants to merge 1 commit into from
Closed

ostree-ext: specify zeroed patch version for ostree #1365

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 ostree-ext/Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,7 +14,7 @@ version = "0.15.3"
# semver here you must also bump our semver.
containers-image-proxy = "0.7.0"
# We re-export this library too.
ostree = { features = ["v2025_2"], version = "0.20" }
ostree = { features = ["v2025_2"], version = "0.20.0" }
Copy link
Copy Markdown
Contributor

@gemini-code-assist gemini-code-assist Bot Jun 12, 2025

Choose a reason for hiding this comment

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

medium

Consider using an exact version pin for ostree to ensure API stability for ostree-ext consumers, given that ostree is re-exported.

ostree = { features = ["v2025_2"], version = "=0.20.0" }


# Private dependencies
anyhow = { workspace = true }
Expand Down