Skip to content

Track upgrade to stable aspect_rules_lint (remove RC dependency) #2516

@dcalavrezo-qorix

Description

@dcalavrezo-qorix

What

We currently rely on aspect_rules_lint >= 2.0.0-rc0 in order to use fail_on_violation (needed e.g. for Clippy in CI).

While this is acceptable short-term, we should explicitly track the switch to the first stable 2.x release once it becomes available, to avoid a long-term dependency on a release candidate.

How

Avoid pinning tooling to an RC longer than necessary

Align with project policy of preferring stable releases

Make the intent and follow-up explicit

Acceptance criteria

Monitor upstream aspect_rules_lint releases

Update dependency to the first stable 2.x.y release supporting fail_on_violation

Remove any references or constraints specific to -rc versions

CI remains failing on lint violations as before

Estimates for realization

it's just a matter of updating the dependency version in MODULE.bazel files

Category

  • Affects Detailed Design

Requirements / Architecture

  • Requirements / Architecture are not affected by this change?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    Status

    Draft

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions