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

chore(deps): update rust crate git2-ext to 0.1.0 #255

Merged
merged 1 commit into from
Dec 3, 2022

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented Dec 2, 2022

Mend Renovate

This PR contains the following updates:

Package Type Update Change
git2-ext dependencies minor 0.0.7 -> 0.1.0

Release Notes

gitext-rs/git2-ext

v0.1.0

Compare Source

Features
  • Commit filtering

Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@epage epage merged commit fbfe724 into main Dec 3, 2022
@epage epage deleted the renovate/git2-ext-0.x branch December 3, 2022 04:38
bors added a commit to rust-lang/cargo that referenced this pull request 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`
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.

1 participant