Skip to content
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

Dependency Dashboard #309

Open
2 tasks
renovate bot opened this issue May 19, 2023 · 0 comments
Open
2 tasks

Dependency Dashboard #309

renovate bot opened this issue May 19, 2023 · 0 comments

Comments

@renovate
Copy link
Contributor

renovate bot commented May 19, 2023

This issue lists Renovate updates and detected dependencies. Read the Dependency Dashboard docs to learn more.

Awaiting Schedule

These updates are awaiting their schedule. Click on a checkbox to get an update now.

  • chore(deps): Update compatible (anstream, anstyle)

Detected dependencies

cargo
Cargo.toml
  • git2 >=0.16, <=0.19
  • git-config-env 0.2.1
  • clap 4.5.4
  • clap-verbosity-flag 2.2.0
  • log 0.4.21
  • env_logger 0.11
  • colorchoice-clap 1.0.3
  • anstyle 1.0.6
  • anstream 0.6.13
  • proc-exit 2.0.1
  • eyre 0.6.12
  • human-panic 2.0.0
  • termtree 0.5.0
  • indexmap 2.2.6
  • git2-ext 0.6.1
  • git-branch-stash 0.10.1
  • humantime 2.1.0
  • itertools 0.13.0
  • ignore 0.4.22
  • bstr 1.9.1
  • maplit 1.0.2
  • petgraph 0.6.4
  • downcast-rs 1.2.1
  • names 0.14.0
  • elsa 1.10.0
  • shlex 1.3.0
  • git-fixture 0.3.4
  • assert_fs 1.1.1
  • snapbox 0.6.0
  • automod 1.0.14
github-actions
.github/workflows/audit.yml
  • actions/checkout v4
  • actions-rs/audit-check v1
  • actions/checkout v4
  • EmbarkStudios/cargo-deny-action v2
.github/workflows/ci.yml
  • actions/checkout v4
  • Swatinem/rust-cache v2
  • actions/checkout v4
  • Swatinem/rust-cache v2
  • actions/checkout v4
  • Swatinem/rust-cache v2
  • actions/checkout v4
  • Swatinem/rust-cache v2
  • actions/checkout v4
  • Swatinem/rust-cache v2
  • actions/checkout v4
  • Swatinem/rust-cache v2
  • github/codeql-action v3
  • actions/checkout v4
  • Swatinem/rust-cache v2
.github/workflows/committed.yml
  • actions/checkout v4
.github/workflows/post-release.yml
  • actions/checkout v4
  • actions/create-release v1
  • actions/checkout v4
  • actions/upload-release-asset v1.0.2
.github/workflows/pre-commit.yml
  • actions/checkout v4
  • actions/setup-python v5
  • pre-commit/action v3.0.1
.github/workflows/rust-next.yml
  • actions/checkout v4
  • Swatinem/rust-cache v2
  • actions/checkout v4
  • Swatinem/rust-cache v2
.github/workflows/spelling.yml
  • actions/checkout v4
regex
.github/workflows/ci.yml
  • STABLE 1.82.0
  • STABLE 1.82.0
  • STABLE 1.82.0

  • Check this box to trigger a request for Renovate to run again on this repository
bors added a commit to rust-lang/cargo that referenced this issue Jul 12, 2023
chore: Automatically update dependencies monthly

### What does this PR try to resolve?

This will create PRs that will update `Cargo.toml` and `Cargo.lock` at the same time.  By default, RenovateBot will update all dependencies, so we pull out the compatible dependencies into a consolidated PR to reduce disruptions and CI load.

This doesn't just cover Rust dependencies but github workflows as well.

### How should we test and review this PR?

This starts off with the dependency dashboard and automerging being disabled but explicitly specified to call attention to the potential for this.  We can evaluate these later.

The frequency of monthly was chosen to consolidate disruptions.  The main risk is doing an update right before a beta branch but we can't have a cron schedule for once every 6 weeks (I assume) which would be ideal.  At least its not daily or instant.

I chose `json5` over `json` for comments and trailing commas, to make human-editing easier.

I pulled the config from https://github.com/gitext-rs/git-stack/blob/main/.github/renovate.json5
- [Dependency dashboard](gitext-rs/git-stack#309)
- [Compatible PR](gitext-rs/git-stack#255)
- [Incompatible PR](gitext-rs/git-stack#310)

CC `@Turbo87`
@epage epage pinned this issue Apr 1, 2024
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

No branches or pull requests

0 participants