Skip to content

renovate: Use github-tags datasource for Rust updates #7243

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

Merged
merged 2 commits into from
Oct 6, 2023

Conversation

Turbo87
Copy link
Member

@Turbo87 Turbo87 commented Oct 6, 2023

GitHub releases are sometimes a bit delayed and need manual work from the release team for patch releases. GitHub tags appear to be more reliable, so let's use those instead.

This should avoid #7241 and #7242 being two separate PRs instead of a single one.

We use a `rust-toolchain.toml` file now, so we don't need to explicitly set the Rust version here anymore
GitHub releases are sometimes a bit delayed and need manual work from the release team for patch releases. GitHub tags appear to be more reliable, so let's use those instead.
@Turbo87 Turbo87 added C-internal 🔧 Category: Nonessential work that would make the codebase more consistent or clear A-backend ⚙️ labels Oct 6, 2023
@Turbo87 Turbo87 enabled auto-merge October 6, 2023 08:15
@Turbo87 Turbo87 merged commit 379fcaa into rust-lang:main Oct 6, 2023
@Turbo87 Turbo87 deleted the rust-from-tags branch October 6, 2023 08:20
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-backend ⚙️ C-internal 🔧 Category: Nonessential work that would make the codebase more consistent or clear
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant