Repository navigation
chore(deps): Bump the cargo-major group across 1 directory with 2 updates - #2464
dependabot[bot] wants to merge 1 commit into
Conversation
dependabot
Bot
added
dependencies
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: c687c3ab48
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| # its own templates need, and states why in its manifest. | ||
| minijinja = { version = "2.24", default-features = false } | ||
| miniz_oxide = "=0.8.5" | ||
| miniz_oxide = "=0.9.1" |
There was a problem hiding this comment.
The root Cargo.lock still resolves miniz_oxide 0.8.5 and saphyr-parser 0.1.0, while these workspace dependencies are now exact-pinned to 0.9.1 and 0.2.2. Only the standalone WASM SDK lockfile was updated, so the root workspace cannot run its required cargo check --locked --workspace --all-targets or cargo test --locked --workspace without changing the lockfile; regenerate and commit the root Cargo.lock for both updated pins.
AGENTS.md reference: AGENTS.md:L290-L297
Useful? React with 👍 / 👎.
c687c3a to
192b238
Compare
…ates Bumps the cargo-major group with 2 updates in the /products/breg/wasm-handler-sdk directory: [miniz_oxide](https://github.com/Frommi/miniz_oxide) and [saphyr-parser](https://github.com/saphyr-rs/saphyr). Updates `miniz_oxide` from 0.8.5 to 0.9.1 - [Changelog](https://github.com/Frommi/miniz_oxide/blob/master/CHANGELOG.md) - [Commits](https://github.com/Frommi/miniz_oxide/commits) Updates `saphyr-parser` from 0.1.0 to 0.3.2 - [Release notes](https://github.com/saphyr-rs/saphyr/releases) - [Commits](saphyr-rs/saphyr@v0.1.0...v0.3.2) --- updated-dependencies: - dependency-name: miniz_oxide dependency-version: 0.9.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: cargo-major - dependency-name: saphyr-parser dependency-version: 0.2.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: cargo-major ... Signed-off-by: dependabot[bot] <support@github.com>
192b238 to
d110799
Compare
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d1107990dd
ℹ️ About Codex in GitHub
Codex has been enabled to automatically review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
When you sign up for Codex through ChatGPT, Codex can also answer questions or update the PR, like "@codex address that feedback".
| rustls-native-certs = { version = "0.8.4" } | ||
| ryu-js = { version = "=1.0.3" } | ||
| saphyr-parser = { version = "=0.1.0" } | ||
| saphyr-parser = { version = "=0.3.2" } |
There was a problem hiding this comment.
When this pin takes effect after regenerating the root lockfile, the configuration reader will run 0.3.2, but crates/registry-platform-yaml/README.md lines 427-474 records its safety and behavioral vetting only for exactly 0.1.0 and explicitly requires every version bump to re-audit ScanError call sites, suite compatibility, depth handling, and empty-value behavior. This matters because classify_syntax_error forwards every parser message except those beginning with unexpected character; without the required audit, the guarantee that diagnostics cannot disclose configuration input is no longer supported. Re-vet 0.3.2 and update the evidence and affected tests with the pin.
AGENTS.md reference: products/platform/AGENTS.md:L14-L17
Useful? React with 👍 / 👎.
|
Looks like these dependencies are updatable in another way, so this is no longer needed. |
Bumps the cargo-major group with 2 updates in the /products/breg/wasm-handler-sdk directory: miniz_oxide and saphyr-parser.
Updates
miniz_oxidefrom 0.8.5 to 0.9.1Changelog
Sourced from miniz_oxide's changelog.
... (truncated)
Commits
Updates
saphyr-parserfrom 0.1.0 to 0.3.2Commits
31fd871saphyr v0.3.22a3e03dMerge pull request #145 from spicysharkco/fix/emitter-quote-bom8716b9eloader: remove DEFAULT_ALIAS_LIMIT from the public APIdae4235loader: simplify the DEFAULT_ALIAS_LIMIT comment8a665befix(emitter): quote strings holding a byte order markfb8be68garden: add remote for@spicysharkco38254d1saphyr v0.3.19c80c43CHANGELOG: update release notes draft8808dd8Merge pull request #120 from patchwright/fix/alias-node-budget502d12bsaphyr: expose DEFAULT_ALIAS_LIMIT