Skip to content

chore: Configure Renovate #266

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

chore: Configure Renovate #266

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link

@renovate renovate bot commented Apr 15, 2025

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

  • crates/deno_task_shell/Cargo.toml (cargo)
  • crates/shell/Cargo.toml (cargo)
  • .devcontainer/devcontainer.json (devcontainer)
  • .github/workflows/coverage.yml (github-actions)
  • .github/workflows/enforce-sha.yaml (github-actions)
  • .github/workflows/release.yml (github-actions)
  • .github/workflows/rust-linting.yml (github-actions)
  • .github/workflows/rust-tests.yml (github-actions)
  • .github/workflows/typos.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.
  • 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 18 Pull Requests:

fix(deps): update rust crate tokio [security]
  • Branch name: renovate/crate-tokio-vulnerability
  • Merge into: main
  • Upgrade tokio to 1.43.1
  • Upgrade tokio to 1.38.2
chore(deps): update crate-ci/typos digest to 6f0717a
  • Schedule: ["at any time"]
  • Branch name: renovate/crate-ci-typos-digest
  • Merge into: main
  • Upgrade crate-ci/typos to 6f0717a519ab213fb298181cd37b80d02451bb20
chore(deps): update swatinem/rust-cache digest to 9d47c6a
  • Schedule: ["at any time"]
  • Branch name: renovate/swatinem-rust-cache-digest
  • Merge into: main
  • Upgrade Swatinem/rust-cache to 9d47c6ad4b02e050fd481d890b2ea34778fd09d6
chore(deps): update zgosalvez/github-actions-ensure-sha-pinned-actions digest to 4830be2
fix(deps): update rust crate chrono to v0.4.40
  • Schedule: ["at any time"]
  • Branch name: renovate/chrono-0.x-lockfile
  • Merge into: main
  • Upgrade chrono to 0.4.40
fix(deps): update rust crate clap to v4.5.36
  • Schedule: ["at any time"]
  • Branch name: renovate/clap-4.x-lockfile
  • Merge into: main
  • Upgrade clap to 4.5.36
fix(deps): update rust crate ctrlc to v3.4.6
  • Schedule: ["at any time"]
  • Branch name: renovate/ctrlc-3.x-lockfile
  • Merge into: main
  • Upgrade ctrlc to 3.4.6
fix(deps): update rust crate libc to v0.2.172
  • Schedule: ["at any time"]
  • Branch name: renovate/libc-0.x-lockfile
  • Merge into: main
  • Upgrade libc to 0.2.172
fix(deps): update rust crate serde to v1.0.219
  • Schedule: ["at any time"]
  • Branch name: renovate/serde-monorepo
  • Merge into: main
  • Upgrade serde to 1.0.219
fix(deps): update rust crate uu_date to 0.0.30
  • Schedule: ["at any time"]
  • Branch name: renovate/uu_date-0.x
  • Merge into: main
  • Upgrade uu_date to 0.0.30
fix(deps): update rust crate uu_ls to 0.0.30
  • Schedule: ["at any time"]
  • Branch name: renovate/uu_ls-0.x
  • Merge into: main
  • Upgrade uu_ls to 0.0.30
fix(deps): update rust crate uu_touch to 0.0.30
  • Schedule: ["at any time"]
  • Branch name: renovate/uu_touch-0.x
  • Merge into: main
  • Upgrade uu_touch to 0.0.30
fix(deps): update rust crate uu_uname to 0.0.30
  • Schedule: ["at any time"]
  • Branch name: renovate/uu_uname-0.x
  • Merge into: main
  • Upgrade uu_uname to 0.0.30
fix(deps): update rust crate which to v7.0.3
  • Schedule: ["at any time"]
  • Branch name: renovate/which-7.x-lockfile
  • Merge into: main
  • Upgrade which to 7.0.3
chore(deps): update actions/checkout action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/actions-checkout-4.x
  • Merge into: main
  • Upgrade actions/checkout to 11bd71901bbe5b1630ceea73d27597364c9af683
chore(deps): update actions/upload-artifact action to v4
  • Schedule: ["at any time"]
  • Branch name: renovate/major-github-artifact-actions
  • Merge into: main
  • Upgrade actions/upload-artifact to ea165f8d65b6e75b540449e92b4886f43607fa02
chore(deps): update codecov/codecov-action action to v5
  • Schedule: ["at any time"]
  • Branch name: renovate/codecov-codecov-action-5.x
  • Merge into: main
  • Upgrade codecov/codecov-action to ad3126e916f78f00edff4ed0317cf185271ccc2d
chore(deps): update softprops/action-gh-release action to v2
  • Schedule: ["at any time"]
  • Branch name: renovate/softprops-action-gh-release-2.x
  • Merge into: main
  • Upgrade softprops/action-gh-release to c95fe1489396fe8a9eb87c0abf8aa5b2ef267fda

🚸 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants