chore(deps): bump thiserror from 1.0.69 to 2.0.18 in /panoptes#146
chore(deps): bump thiserror from 1.0.69 to 2.0.18 in /panoptes#146dependabot[bot] wants to merge 1 commit into
Conversation
Bumps [thiserror](https://github.com/dtolnay/thiserror) from 1.0.69 to 2.0.18. - [Release notes](https://github.com/dtolnay/thiserror/releases) - [Commits](dtolnay/thiserror@1.0.69...2.0.18) --- updated-dependencies: - dependency-name: thiserror dependency-version: 2.0.18 dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
|
Closing as superseded by ambientops#153 (estate dependabot policy conformance, standards#301). The canonical |
|
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting If you change your mind, just re-open this PR and I'll resolve any conflicts on it. |
…andards#301) (#153) ## Summary - Adds the canonical estate `ignore: dependency-name "*" version-update:semver-major` block to each non-github-actions ecosystem entry in `.github/dependabot.yml` - 9 entries get the ignore (5 cargo: root + czech-file-knife + panoptes + personal-sysadmin + displace; mix; npm; pip; nix). github-actions is left as-is per estate doc — SHA pins make action majors safe. - Brings ambientops into conformance with standards#301 / docs/DEPENDABOT-POLICY.adoc ## Context Per the 2026-05-29 echidna incident (#120-#124 broke main for ~24h), unattended dependabot semver-major merges fly through the estate validation gates (K9 / A2ML / language-policy) but break the actual compile gates on subsequent pushes. Estate policy now: majors land via author-supplied PRs paired with call-site updates. This PR closes 7 risky in-flight dependabot PRs as superseded: - #147 reqwest 0.12.28→0.13.4 (0.x minor breaking) - #145 config 0.14.1→0.15.23 (0.x minor breaking, multi-version) - #144 symphonia 0.5.5→0.6.0 (0.x minor breaking) - #146 thiserror 1.0.69→2.0.18 (major) - #142 colored 2.2.0→3.1.1 (major) - #136 rusqlite 0.31.0→0.40.0 (0.x huge jump) - #135 nix 0.30.1→0.31.3 (0.x minor breaking) Each needs a paired code-side migration that hasn't been done; this PR parks them safely via the canonical policy. ## Test plan - [ ] dependabot config check passes (YAML valid) - [ ] CI green (existing gates) - [ ] After merge, dependabot does not re-file the 7 closed PRs
Rebasing might not happen immediately, so don't worry if this takes some time.
Note: if you make any changes to this PR yourself, they will take precedence over the rebase.
Bumps thiserror from 1.0.69 to 2.0.18.
Release notes
Sourced from thiserror's releases.
... (truncated)
Commits
dc0f6a2Release 2.0.180275292Touch up PR 4433c33bc6Merge pull request #443 from LucaCappelletti94/master995939cReproduce issue 44221653d1Made clippy lifetime allows conditional45e5388Update actions/upload-artifact@v5 -> v6386aac1Update actions/upload-artifact@v4 -> v5ec50561Update actions/checkout@v5 -> v6247eab5Update name of empty_enum clippy lint91b181fRaise required compiler to Rust 1.68Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)