chore(deps): bump the cargo group across 1 directory with 7 updates - #489
chore(deps): bump the cargo group across 1 directory with 7 updates#489dependabot[bot] wants to merge 1 commit into
Conversation
|
For the record, since this is the first cargo batch built under #484's rules — it came back with the right contents. 7 crates instead of #478's 17, all genuinely minor/patch. Gone from the batch: It is still red, but on exactly one thing and it is the documented one: That is the crate↔npm parity guard — the other half of these Tauri plugin bumps is in #487, and neither PR is green on its own. They have to be merged as a pair; the red build on whichever goes first is expected rather than a reason to close it. No |
….0 npm (#490) Follow-up to #484, which is now doing its job -- the recreated cargo batch (#489) came back with 7 minor/patch crates instead of 16 with majors inside. Three things that first pass did not cover, and one that was planned and is not here. **Cadence.** npm and cargo move to `quarterly`; github-actions stays `monthly`. Security advisories never use this schedule -- they are a repository setting and open their own pull requests as they land -- so version updates exist only to stop drift, and drift costs what somebody else's deadline costs. On Actions somebody else always sets it: runner images retire toolchains on their own timetable, which is how `build.yml` came to build releases on a Node pulled from the image toolcache (#485). An Actions bump is also usually a one-line tag move. Nothing external forces a TypeScript or a serde upgrade, and a quarter of them in one grouped pull request is less interrupting and more reviewable than three monthly ones. **`minor` does not mean compatible below 1.0, and the two ecosystems disagree about it.** Dependabot types an npm update from the literal position of the number, so katex 0.16.47 -> 0.18.1 is a `minor` and went straight into #487 -- the batch whose whole premise is that it is safe to skim. It is not: KaTeX 0.18.0 renamed every internal CSS class and 0.17.0 changed `__defineFunction`, both flagged BREAKING upstream. npm's own caret rule agrees, since `^0.16.47` stops before 0.17. Cargo does not have this bug. `Dependabot::Cargo::Version` implements the pre-1.0 rule, so windows 0.61.3 -> 0.62.2 counts as a major -- which is visible in #489, where those crates are absent from the batch. The npm side has no equivalent subclass. There is no `update-types` value for "pre-1.0 minor", and `patterns` match names rather than versions, so this cannot be written as a rule. It can be written as a list: `exclude-patterns` names the three pre-1.0 npm dependencies, and they get individual pull requests. The test derives that list from package.json, so a new 0.x dependency -- or an existing one reaching 1.0 -- fails the suite instead of quietly rejoining the batch. **Two crates held.** `tauri` requires `windows ^0.61` and `webview2-com ^0.38`, still true at 2.11.5. Taking `windows` 0.62 or `webview2-com` 0.39 puts two `windows-core` versions in one graph and the build stops in our own WebView2 call with E0599. Grouping already keeps them out of the batch; what is left is an individual pull request every quarter that cannot be merged at any published tauri 2.x. Bounded to one minor series each rather than written as a semver level, so the entries lapse. The semver-level form would work -- `Cargo::Version` overrides `ignored_major_versions` so ">= 0.62" is what major means for a 0.61 crate -- but it would also swallow 0.63 and 0.64 in silence. `windows` 0.63 does not exist yet; the day it does, Dependabot proposes it and we find out whether tauri has moved. The Tauri packages themselves are deliberately not ignored, and the file says so: the lockfile is on 2.10.2 while 2.11.5 shipped 2026-07-01, and the red pull request is the only notification there is. **The cooldown is not here, because the case for it does not survive being checked.** The mechanism is fine -- `cooldown` is valid alongside `groups`, dependabot-core passes it on both the grouped and the individual path, and it cannot touch a security update (`update_cooldown: job.security_updates_only? ? nil : job.cooldown` in both). What fails is the premise that the red pull requests are red because their targets are fresh: - typescript 7.0.2 shipped 2026-07-08; svelte-check 4.7.4 shipped 2026-07-27, nineteen days later, and narrowed its peer range to `^5.0.0 || ^6.0.0` -- excluding 7 on purpose. - windows 0.62.2 has been out since 2025-10-06 and webview2-com 0.39.1 since 2026-03-11. Ten months and five. - katex 0.18.1 is three weeks old, but it is breaking at any age. - the rest is the Tauri parity guard, which is not about age at all. None of them is a freshness problem. And on a quarterly schedule a major caught by an N-day window is not delayed N days, it is delayed a quarter. Also worth recording: GitHub Actions does not support `semver-major-days` at all, so a cooldown could never have applied to the one ecosystem that stays monthly. Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
Bumps the cargo group with 7 updates in the /src-tauri directory: | Package | From | To | | --- | --- | --- | | [tauri-plugin-opener](https://github.com/tauri-apps/plugins-workspace) | `2.5.3` | `2.5.4` | | [tauri-plugin-dialog](https://github.com/tauri-apps/plugins-workspace) | `2.6.0` | `2.7.2` | | [tauri-plugin-single-instance](https://github.com/tauri-apps/plugins-workspace) | `2.4.0` | `2.4.3` | | [serde](https://github.com/serde-rs/serde) | `1.0.228` | `1.0.229` | | [serde_json](https://github.com/serde-rs/json) | `1.0.149` | `1.0.151` | | [regex](https://github.com/rust-lang/regex) | `1.12.3` | `1.13.1` | | [tauri-build](https://github.com/tauri-apps/tauri) | `2.5.5` | `2.6.3` | Updates `tauri-plugin-opener` from 2.5.3 to 2.5.4 - [Release notes](https://github.com/tauri-apps/plugins-workspace/releases) - [Commits](tauri-apps/plugins-workspace@http-v2.5.3...http-v2.5.4) Updates `tauri-plugin-dialog` from 2.6.0 to 2.7.2 - [Release notes](https://github.com/tauri-apps/plugins-workspace/releases) - [Commits](tauri-apps/plugins-workspace@log-v2.6.0...dialog-v2.7.2) Updates `tauri-plugin-single-instance` from 2.4.0 to 2.4.3 - [Release notes](https://github.com/tauri-apps/plugins-workspace/releases) - [Commits](tauri-apps/plugins-workspace@fs-v2.4.0...fs-v2.4.3) Updates `serde` from 1.0.228 to 1.0.229 - [Release notes](https://github.com/serde-rs/serde/releases) - [Commits](serde-rs/serde@v1.0.228...v1.0.229) Updates `serde_json` from 1.0.149 to 1.0.151 - [Release notes](https://github.com/serde-rs/json/releases) - [Commits](serde-rs/json@v1.0.149...v1.0.151) Updates `regex` from 1.12.3 to 1.13.1 - [Release notes](https://github.com/rust-lang/regex/releases) - [Changelog](https://github.com/rust-lang/regex/blob/master/CHANGELOG.md) - [Commits](rust-lang/regex@1.12.3...1.13.1) Updates `tauri-build` from 2.5.5 to 2.6.3 - [Release notes](https://github.com/tauri-apps/tauri/releases) - [Commits](tauri-apps/tauri@tauri-build-v2.5.5...tauri-build-v2.6.3) --- updated-dependencies: - dependency-name: regex dependency-version: 1.13.1 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: cargo - dependency-name: serde dependency-version: 1.0.229 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: cargo - dependency-name: serde_json dependency-version: 1.0.151 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: cargo - dependency-name: tauri-build dependency-version: 2.6.3 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: cargo - dependency-name: tauri-plugin-dialog dependency-version: 2.7.2 dependency-type: direct:production update-type: version-update:semver-minor dependency-group: cargo - dependency-name: tauri-plugin-opener dependency-version: 2.5.4 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: cargo - dependency-name: tauri-plugin-single-instance dependency-version: 2.4.3 dependency-type: direct:production update-type: version-update:semver-patch dependency-group: cargo ... Signed-off-by: dependabot[bot] <support@github.com>
e5cd9b1 to
bd574ae
Compare
|
Closing this without merging, and recording why so the next quarterly run is not re-litigated from scratch. These two batches are two halves of one bump. #491 carries the npm side of the Tauri family, this carries the crate side, and That work is only worth doing if the bump is worth having, and I could not establish that it is. What is actually in here, checked against the upstream changelogs rather than assumed:
So the batch clears no bug and adds no capability this app uses. Merging it would be motion, not progress. What would change the answer. Since #490 moved npm and cargo to a quarterly schedule, this returns on its own in about three months. Nothing is lost by closing it now. |
|
This pull request was built based on a group rule. Closing it will not ignore any of these versions in future pull requests. To ignore these dependencies, configure ignore rules in dependabot.yml |
Bumps the cargo group with 7 updates in the /src-tauri directory:
2.5.32.5.42.6.02.7.22.4.02.4.31.0.2281.0.2291.0.1491.0.1511.12.31.13.12.5.52.6.3Updates
tauri-plugin-openerfrom 2.5.3 to 2.5.4Release notes
Sourced from tauri-plugin-opener's releases.
... (truncated)
Commits
e7a68fapublish new versions (#3068)b5550a3chore: temp delete updater changefile93426f8fix: fix docsrs builds4ee61e0Revert "chore: temp delete updater changefile"Updates
tauri-plugin-dialogfrom 2.6.0 to 2.7.2Release notes
Sourced from tauri-plugin-dialog's releases.
... (truncated)
Commits
03afae6publish new versions (#3500)57ac986chore(deps): update dependency@tauri-apps/clito v2.11.4 (#3463)2ed6d6cfix(store):StoreOptions.defaultsshould not be required (#3499)cdfd462chore(example): setcolor-cheme(#3493)d6e0b6bchore(example): clean up and migrate to ts partially (#3492)40ae0a7enhance(dialog): useMaterialAlertDialogBuilder(#3491)edc52eachore(deps): bump create-pull-request to v8 (#3489)a0d949dchore(deps): update pnpm to v11 (#3487)13c63afchore: fix clippy (#3488)cad301fpublish new versions (#3447)Updates
tauri-plugin-single-instancefrom 2.4.0 to 2.4.3Release notes
Sourced from tauri-plugin-single-instance's releases.
... (truncated)
Commits
06124afpublish new versions (#2972)060219echore(deps): update dependency@rollup/plugin-typescriptto v12.3.0 (#3067)c7e9766chore(deps): update tauri monorepo (v2) (#3058)d4a8ce9chore(deps): update rust crate tokio-tungstenite to 0.28 (#3016)cdc7eecchore(deps): update dependency@rollup/plugin-typescriptto v12.2.0 (#3066)6314b00chore: temp delete updater changefilefb4c8aechore(deps): update dependency typescript-eslint to v8.46.2 (#3060)fccc1cfchore(deps): update eslint monorepo to v9.38.0 (#3044)3702308chore(deps): update dependency rollup to v4.52.5 (#3043)c9c8b39chore(deps): update dependency typescript-eslint to v8.46.1 (#3025)Updates
serdefrom 1.0.228 to 1.0.229Release notes
Sourced from serde's releases.
Commits
7fc3b4cRelease 1.0.2296d6e9a1Merge pull request #3085 from dtolnay/syn36dec3b7Update to syn 3cfe6692Resolve mut_mut pedantic clippy lint1023d07Update actions/upload-artifact@v6 -> v7dd682c2Update actions/checkout@v6 -> v75f0f18bUpdate ui test suite to nightly-2026-06-0163a1498Regenerate stderr with trybuild normalization fixesfa7da4aFix unused_features warning6b1a178Unpin CI miri toolchainUpdates
serde_jsonfrom 1.0.149 to 1.0.151Release notes
Sourced from serde_json's releases.
Commits
de85007Release 1.0.1513b2b3c5Merge pull request #1331 from WonderLawrence/rawvalue-from-string-unchecked0406d96Debug-assert well-formedness and no-whitespace in from_string_uncheckedcf16f75Add RawValue::from_string_unchecked827a315Update actions/upload-artifact@v6 -> v7cea36a5Update actions/checkout@v6 -> v7a1ae73aRelease 1.0.1501a360b0Merge pull request #1324 from puneetdixit200/reject-non-string-enum-keys2037b63Reject non-string enum object keys5d30df6Resolve manual_assert_eq pedantic clippy lintUpdates
regexfrom 1.12.3 to 1.13.1Changelog
Sourced from regex's changelog.
... (truncated)
Commits
2b527591.13.1, redux40e98231.13.175fcb96changelog: 1.13.164ad0b6automata: fix bug in reverse suffix/inner optimizationfa91c31automata: fix a bug caught by Codex review30390ecautomata: formatting tweaks821a8ebautomata: refactor reverse suffix/inner search slightly10afd70automata: expose the extracted literals for inner literal extraction8c34f41automata: avoid reverse suffix optimization for non-leftmost-first5524f02test: add regression tests for failed reverse suffix/inner optimizationsUpdates
tauri-buildfrom 2.5.5 to 2.6.3Release notes
Sourced from tauri-build's releases.
... (truncated)
Commits