chore: Configure Renovate

[renovate]

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

---

Detected Package Files

• Cargo.toml (cargo)
• bitcoind-tests/Cargo.toml (cargo)
• embedded/Cargo.toml (cargo)
• fuzz/Cargo.toml (cargo)
• .github/workflows/cron-daily-fuzz.yml (github-actions)
• .github/workflows/cron-weekly-update-nightly.yml (github-actions)
• .github/workflows/rust.yml (github-actions)
• .github/workflows/shellcheck.yml (github-actions)

Configuration Summary

Based on the default config's presets, Renovate will:

• Start dependency updates only once this onboarding PR is merged
• Hopefully safe environment variables to allow users to configure.
• Show all Merge Confidence badges for pull requests.
• Enable Renovate Dependency Dashboard creation.
• Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
• Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
• Group known monorepo packages together.
• Use curated list of recommended non-monorepo package groupings.
• Show only the Age and Confidence Merge Confidence badges for pull requests.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.

---

What to Expect

With your current configuration, Renovate will create 8 Pull Requests:

fix(deps): update rust crate actual-rand to 0.9.0

• Schedule: ["at any time"]
• Branch name: renovate/actual-rand-0.x
• Merge into: master
• Upgrade actual-rand to 0.9.0

fix(deps): update rust crate bitcoind to 0.8.0

• Schedule: ["at any time"]
• Branch name: renovate/bitcoind-0.x
• Merge into: master
• Upgrade bitcoind to 0.8.0

fix(deps): update rust crate cortex-m to 0.7.0

• Schedule: ["at any time"]
• Branch name: renovate/cortex-m-0.x
• Merge into: master
• Upgrade cortex-m to 0.7.0

fix(deps): update rust crate cortex-m-rt to 0.7.0

• Schedule: ["at any time"]
• Branch name: renovate/cortex-m-rt-0.x
• Merge into: master
• Upgrade cortex-m-rt to 0.7.0

fix(deps): update rust crate cortex-m-semihosting to 0.5.0

• Schedule: ["at any time"]
• Branch name: renovate/cortex-m-semihosting-0.x
• Merge into: master
• Upgrade cortex-m-semihosting to 0.5.0

fix(deps): update rust crate secp256k1 to 0.31.0

• Schedule: ["at any time"]
• Branch name: renovate/secp256k1-0.x
• Merge into: master
• Upgrade secp256k1 to 0.31.0

chore(deps): update actions/checkout action to v4

• Schedule: ["at any time"]
• Branch name: renovate/actions-checkout-4.x
• Merge into: master
• Upgrade actions/checkout to v4

fix(deps): update rust crate panic-halt to v1

• Schedule: ["at any time"]
• Branch name: renovate/panic-halt-1.x
• Merge into: master
• Upgrade panic-halt to 1.0.0

🚸 Branch creation will be limited to maximum 2 per hour, so it doesn't swamp any CI resources or overwhelm the project. See docs for prhourlylimit for details.

---

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

---

This PR was generated by Mend Renovate. View the repository job log.

[apoelstra]

Lol what the fuck.

I was looking into ways to replace the update-nightly-compiler script to be more reliable (or at least, not involve me generating a zillion tokens and copying them everywhere) (or at least, not be making PRs under my own name). I only half-installed this thing -- I refused to sign their privacy policy etc. and figured that was the end of it.

But apparently not.

[apoelstra]

This is an obnoxious textwall and the claimed changes would break tons of stuff. Plonk.