Skip to content

deps: bump cap-std-ext from 4.0 to 5.0#56

Merged
jmarrero merged 2 commits into
bootc-dev:mainfrom
jlebon:pr/cap-std-ext-5
Feb 17, 2026
Merged

deps: bump cap-std-ext from 4.0 to 5.0#56
jmarrero merged 2 commits into
bootc-dev:mainfrom
jlebon:pr/cap-std-ext-5

Conversation

@jlebon

@jlebon jlebon commented Feb 12, 2026

Copy link
Copy Markdown
Contributor

So things that pull in both this crate and cap-std-ext can actually update to 5.0.0. :)

This bumps the underlying cap-std from 3.x to 4.x. Also bumps
cap-tempfile from 3.x to 4.x to match.

Assisted-by: Claude Opus 4

Signed-off-by: Jonathan Lebon <jonathan@jlebon.com>
Semver break due to cap-std-ext bump.

Signed-off-by: Jonathan Lebon <jonathan@jlebon.com>

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Code Review

This pull request updates the cap-std-ext dependency to a new major version, and also updates the related cap-tempfile dev-dependency. The crate's own version is correctly bumped from 0.6.0 to 0.7.0 to signal that this dependency update may introduce breaking changes, which is good practice for a pre-1.0.0 crate. The changes are straightforward and appear correct.

@jlebon

jlebon commented Feb 17, 2026

Copy link
Copy Markdown
Contributor Author

I don't have ACLs here, but would appreciate a merge and release soon-ish to unblock some bumps in my crates.

@jmarrero
jmarrero merged commit 6f4fc05 into bootc-dev:main Feb 17, 2026
4 checks passed
@jmarrero

Copy link
Copy Markdown
Contributor

I can merge, I can't push this to crates.io.

@cgwalters

Copy link
Copy Markdown
Collaborator

I can't push this to crates.io.

The new model is automatic publishing (no manual human pushes) should just need #58 plus a release tag.

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.

3 participants