Skip to content

build(deps): bump getrandom from 0.3.4 to 0.4.3 in /ui/src-tauri - #37

Merged
Chris-ObtuseAI merged 2 commits into
mainfrom
dependabot/cargo/ui/src-tauri/getrandom-0.4.3
Aug 1, 2026
Merged

build(deps): bump getrandom from 0.3.4 to 0.4.3 in /ui/src-tauri#37
Chris-ObtuseAI merged 2 commits into
mainfrom
dependabot/cargo/ui/src-tauri/getrandom-0.4.3

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Jul 30, 2026

Copy link
Copy Markdown
Contributor

Bumps getrandom from 0.3.4 to 0.4.3.

Changelog

Sourced from getrandom's changelog.

0.4.3 - 2026-06-17

Added

  • wasm64-unknown-unknown target support for wasm_js backend #848

Changed

  • Drop wasip2 and wasip3 dependencies in favor of manual bindings #830

#830: rust-random/getrandom#830 #848: rust-random/getrandom#848

0.4.2 - 2026-03-03

Changed

  • Bump r-efi dependency to v6 #814

Fixed

  • Read errno only when it is set #810
  • Check the return value of ProcessPrng on Windows #811

#810: rust-random/getrandom#810 #811: rust-random/getrandom#811 #814: rust-random/getrandom#814

0.4.1 - 2026-02-03

Fixed

  • Documentation build on docs.rs #801

#801: rust-random/getrandom#801

0.4.0 - 2026-02-02

Added

  • RawOsError type alias #739
  • SysRng behind new feature sys_rng #751
  • WASIp3 support #779
  • extern_impl opt-in backend #786 #794
  • Motor OS support #797

Changed

  • Use Edition 2024 and MSRV 1.85 #749

#739: rust-random/getrandom#739 #749: rust-random/getrandom#749 #751: rust-random/getrandom#751 #779: rust-random/getrandom#779

... (truncated)

Commits

Dependabot compatibility score

Dependabot 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 rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will 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 version will 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 dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [getrandom](https://github.com/rust-random/getrandom) from 0.3.4 to 0.4.3.
- [Changelog](https://github.com/rust-random/getrandom/blob/master/CHANGELOG.md)
- [Commits](rust-random/getrandom@v0.3.4...v0.4.3)

---
updated-dependencies:
- dependency-name: getrandom
  dependency-version: 0.4.3
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot Bot added dependencies Pull requests that update a dependency file rust Pull requests that update rust code labels Jul 30, 2026
@Chris-ObtuseAI
Chris-ObtuseAI merged commit 8c7c4a1 into main Aug 1, 2026
10 checks passed
@dependabot
dependabot Bot deleted the dependabot/cargo/ui/src-tauri/getrandom-0.4.3 branch August 1, 2026 03:55
Chris-ObtuseAI added a commit that referenced this pull request Aug 1, 2026
`concurrency.group` was the fixed string `pages`, so every pull request
and every push to main contended for a single slot. With
`cancel-in-progress: false` GitHub keeps only the newest queued run and
supersedes the rest, and because `Build synthetic-only Organism` is a
REQUIRED status check on main, any PR whose run was superseded became
permanently unmergeable — the check never reports at all, so it can
never be satisfied by re-running CI.

Observed on four open dependabot PRs, all `completed/cancelled` for this
workflow while a fifth succeeded:

  cancelled  dependabot/cargo/ui/src-tauri/reqwest-0.13   3385339  #19
  cancelled  dependabot/npm_and_yarn/ui/vitest-4.1.10     50eef14  #15
  cancelled  dependabot/npm_and_yarn/ui/multi-223fb6760   e32b73b  #20
  cancelled  dependabot/github_actions/actions/setup-py   2a9c4d3  #11
  success    dependabot/cargo/ui/src-tauri/getrandom-0.   cd54a61  #37

Keying the group by `github.ref` serialises per branch, so pushes to
main still queue against each other and real Pages deployments remain
ordered, while pull requests no longer compete for the same slot.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
Chris-ObtuseAI added a commit that referenced this pull request Aug 1, 2026
* Rotate the pinned supply-chain digests dependabot cannot reach

Dependabot proposes a dependency bump but cannot update the pins that
guard it, so these PRs could never go green on their own:

  - tests/test_runtime_dependency_lock.py pins the exact runtime version
    and asserts requirements-runtime.lock matches the uv resolution
  - tests/test_validation_dependency_lock.py pins every validation tool
    version across pyproject, uv.lock and requirements-validation.lock
  - tests/test_release_build_trust.py and
    tests/test_doofus_external_trial_workflow.py pin the exact commit
    digest of each attestation action, so a workflow-only bump fails

Every digest below was verified against the upstream tag before use,
not taken from dependabot's word:

  actions/attest v4.2.0 = f7c74d28b9d84cb8768d0b8ca14a4bac6ef463e6
  actions/attest v4.2.1 = 508db95dd578ae2727ebd6217d5ba78e4fbda05d
  actions/attest-build-provenance v4.1.1
                        = 0f67c3f4856b2e3261c31976d6725780e5e4c373

Changes:
  - cryptography 48.0.1 -> 49.0.0, constraint <49 -> <50 (closes #13)
  - pip-audit 2.9.0 -> 2.10.1, which drops toml for tomli/tomli-w
    (closes #17)
  - actions/attest v4.2.0 -> v4.2.1 in ui.yml and
    nimrod-external-witness.yml (closes #10)
  - actions/attest-build-provenance v3 -> v4.1.1 in
    doofus-external-trial.yml (closes #12)

Both lock files were regenerated with the pinned uv 0.11.15 rather than
hand-edited, so every hash is machine-derived.

ruff 0.16.0 is deliberately NOT included. It changes default rule
behaviour and reports 893 errors (497 auto-fixable) against this tree.
That is a lint migration, not a dependency bump, and it belongs in its
own change. #16 stays open.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

* Export requirements-validation.lock with the canonical gate flags

validate_release_python.py regenerates the file with
--only-group validation --no-annotate and byte-compares. The first
export omitted --no-annotate, so the committed file carried 37 lines of
"# via" provenance comments the gate never produces, and
validation_lock_reproducible failed.

Both lock files are now written with exactly the commands the gate uses:
  runtime:    uv export --locked --no-default-groups --format requirements-txt --no-header --no-emit-project
  validation: uv export --locked --only-group validation --no-annotate --format requirements-txt --no-header --no-emit-project

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

* Rotate the fifth pip-audit pin in the release validator

EXPECTED_TOOL_VERSIONS in scripts/validate_release_python.py asserts the
INSTALLED tool versions match the contract, so pip-audit is pinned in
five places, not four: pyproject.toml, uv.lock,
requirements-validation.lock, tests/test_validation_dependency_lock.py,
and this validator.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

* Key the pages concurrency group by ref so PRs stop starving each other

`concurrency.group` was the fixed string `pages`, so every pull request
and every push to main contended for a single slot. With
`cancel-in-progress: false` GitHub keeps only the newest queued run and
supersedes the rest, and because `Build synthetic-only Organism` is a
REQUIRED status check on main, any PR whose run was superseded became
permanently unmergeable — the check never reports at all, so it can
never be satisfied by re-running CI.

Observed on four open dependabot PRs, all `completed/cancelled` for this
workflow while a fifth succeeded:

  cancelled  dependabot/cargo/ui/src-tauri/reqwest-0.13   3385339  #19
  cancelled  dependabot/npm_and_yarn/ui/vitest-4.1.10     50eef14  #15
  cancelled  dependabot/npm_and_yarn/ui/multi-223fb6760   e32b73b  #20
  cancelled  dependabot/github_actions/actions/setup-py   2a9c4d3  #11
  success    dependabot/cargo/ui/src-tauri/getrandom-0.   cd54a61  #37

Keying the group by `github.ref` serialises per branch, so pushes to
main still queue against each other and real Pages deployments remain
ordered, while pull requests no longer compete for the same slot.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dependencies Pull requests that update a dependency file rust Pull requests that update rust code

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant