chore(deps): bump rand from 0.9.2 to 0.10.0 in /bots/echidnabot#51
Merged
Merged
Conversation
dependabot
Bot
added
dependencies
hyperpolymath
approved these changes
Apr 13, 2026
Bumps [rand](https://github.com/rust-random/rand) from 0.9.2 to 0.10.0. - [Release notes](https://github.com/rust-random/rand/releases) - [Changelog](https://github.com/rust-random/rand/blob/master/CHANGELOG.md) - [Commits](rust-random/rand@rand_core-0.9.2...0.10.0) --- updated-dependencies: - dependency-name: rand dependency-version: 0.10.0 dependency-type: direct:production update-type: version-update:semver-minor ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
force-pushed
the
dependabot/cargo/bots/echidnabot/rand-0.10.0
branch
from
f15bd6e to
a8bafcf
Compare
hyperpolymath
added a commit
that referenced
this pull request
Apr 19, 2026
Two-way merge resolving the structural drift between hyperpolymath/gitbot-fleet
(this repo) and the content absorbed into /var/mnt/eclipse/repos (the meta-repo
repos-monorepo) at fleet-ecosystem/git-automation-ecosystem/gitbot-fleet/.
The two histories had diverged with no common ancestor. Meta-repo held real
feature work (exclusion registry, SCM->A2ML directive migration, sha2 0.11 +
hmac 0.13 compat fixes, contractile refactors, wave2c sweeps). This repo held
a small set of housekeeping commits (LICENSE update to PMPL-1.0-or-later,
panic-attacker docs, supervised-fleet-scan GITHUB_TOKEN/FLEET_SCAN_PAT fix,
M5 CI sweep, ~7 Dependabot dep bumps) plus an accidentally-committed
BuckleScript build artefact set under bots/sustainabot/bot-integration/lib/bs/
(120 files — .cmi/.cmj/.cmt/.ast/.res.js/bindings/).
Merge resolution:
- Meta-repo content adopted as base (823 tracked files, cleaner .gitignore
that correctly excludes the bs/ artefacts).
- 45 files modified: meta's versions adopted (newer bot feature work,
newer Cargo.toml/.lock with sha2/hmac bumps, newer directive parsers).
- 9 files added from meta: exclusion_registry.rs + registry_guard.rs in
shared-context/ and robot-repo-automaton/, plus 4 flake.lock / Justfile
files that meta had but this repo didn't.
- 120 files removed: the accidentally-committed bs/ build artefacts.
- LICENSE restored from origin/main (PMPL-1.0-or-later per estate rule;
meta's was an older MPL-2.0-labelled version).
- .github/workflows/supervised-fleet-scan.yml restored from origin/main
(meta's predated the GITHUB_TOKEN/FLEET_SCAN_PAT + HYPATIA_SEVERITY=low
fixes from cd67367). No meta-only content was lost in this file.
Other GitHub-unique commits verified already present in meta:
- 7ae485e (panic-attacker docs in finishingbot README) — already in meta.
- c692816 (M5 CI sweep, SCM bot_directives removal) — SCM files already
purged in meta per 2026-04-12 A2ML migration; Justfile already imports
contractile.just.
- Dependabot rand/tokio bumps (#48/#50/#51/#55/#56) — meta has rand 0.10
and tokio 1 at-or-above these versions.
After this commit merges, the meta-repo side will remove the absorbed
gitbot-fleet/ directory from its tree and re-add it as a submodule pointing
at the new origin/main HEAD, eliminating the dual-truth situation.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
3 tasks
hyperpolymath
added a commit
that referenced
this pull request
Apr 19, 2026
Two-way merge resolving the structural drift between hyperpolymath/gitbot-fleet
(this repo) and the content absorbed into /var/mnt/eclipse/repos (the meta-repo
repos-monorepo) at fleet-ecosystem/git-automation-ecosystem/gitbot-fleet/.
The two histories had diverged with no common ancestor. Meta-repo held real
feature work (exclusion registry, SCM->A2ML directive migration, sha2 0.11 +
hmac 0.13 compat fixes, contractile refactors, wave2c sweeps). This repo held
a small set of housekeeping commits (LICENSE update to PMPL-1.0-or-later,
panic-attacker docs, supervised-fleet-scan GITHUB_TOKEN/FLEET_SCAN_PAT fix,
M5 CI sweep, ~7 Dependabot dep bumps) plus an accidentally-committed
BuckleScript build artefact set under bots/sustainabot/bot-integration/lib/bs/
(120 files — .cmi/.cmj/.cmt/.ast/.res.js/bindings/).
Merge resolution:
- Meta-repo content adopted as base (823 tracked files, cleaner .gitignore
that correctly excludes the bs/ artefacts).
- 45 files modified: meta's versions adopted (newer bot feature work,
newer Cargo.toml/.lock with sha2/hmac bumps, newer directive parsers).
- 9 files added from meta: exclusion_registry.rs + registry_guard.rs in
shared-context/ and robot-repo-automaton/, plus 4 flake.lock / Justfile
files that meta had but this repo didn't.
- 120 files removed: the accidentally-committed bs/ build artefacts.
- LICENSE restored from origin/main (PMPL-1.0-or-later per estate rule;
meta's was an older MPL-2.0-labelled version).
- .github/workflows/supervised-fleet-scan.yml restored from origin/main
(meta's predated the GITHUB_TOKEN/FLEET_SCAN_PAT + HYPATIA_SEVERITY=low
fixes from cd67367). No meta-only content was lost in this file.
Other GitHub-unique commits verified already present in meta:
- 7ae485e (panic-attacker docs in finishingbot README) — already in meta.
- c692816 (M5 CI sweep, SCM bot_directives removal) — SCM files already
purged in meta per 2026-04-12 A2ML migration; Justfile already imports
contractile.just.
- Dependabot rand/tokio bumps (#48/#50/#51/#55/#56) — meta has rand 0.10
and tokio 1 at-or-above these versions.
After this commit merges, the meta-repo side will remove the absorbed
gitbot-fleet/ directory from its tree and re-add it as a submodule pointing
at the new origin/main HEAD, eliminating the dual-truth situation.
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps rand from 0.9.2 to 0.10.0.
Changelog
Sourced from rand's changelog.
Commits
acc5f24Prepare v0.10.0 releases (#1729)95c5165Add fn rand::make_rng (#1734)146da58CHANGELOG: add PR links (#1738)8cacd6dREADME tweaks (#1737)28e3df8Update chacha20: use ChaChaCore directly; remove bytes_until_reseed field (#1...03db311Replace fn reseed_and_generate with try_to_reseedb14483eApply inline attr to fn generatefda8f74Remove bytes_until_reseed field213bb3bBump chacha20 to 0.10.0-rc.1172afe1eMinor tweaks; prepare v0.10.0-rc.9 (#1736)