Skip to content

Requiring version number to match upstream Rust version is unnecessary #6683

@Mark-Simulacrum

Description

@Mark-Simulacrum

#6499 proposed locking the version number of clippy-the-cargo project to the version number of Rust. In practice, this causes some work for the release team during release week, and I'm not sure why it matters - to my knowledge, clippy isn't depended on by any projects outside the monorepo at rust-lang/rust and this repository, so the version number shouldn't meaningfully affect anyone. Can we remove the tests, at least? Cargo for example does not bump the version number in lockstep with the monorepo, for example, so it doesn't seem like this is all that necessary.

If there's some purpose to the version number then we can work on documenting the process to update in https://forge.rust-lang.org/release/process.html#bump-the-stable-version-number-t-6-days-friday-the-week-before, but it would be great to avoid that - we're hoping to eventually automate the release process pretty much start to finish, and the fewer files need to be edited (particularly relatively complex ones like Cargo.toml) the easier that will be.

Metadata

Metadata

Assignees

No one assigned

    Labels

    A-infraArea: CI issues and issues that require full access for GitHub/CI

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions