Skip to content

release: ensure dependencies are updated in release branches #2363

@anmazzotti

Description

@anmazzotti

This issue is about implementing dependencies bump automation for release branches.

Acceptance Criteria:

  • Automation should only target branches for releases that are maintained and supported.
  • Automation should only bump patch releases, no minor/major bumps.
  • Changes should be tested by all available e2e coverage (ex. run e2e tests on release branches)
  • Bumps should include:
    • go version
    • go.mod dependencies
    • CAPI providers (including Core)
    • rancher/kuberlr-kubectl image

Metadata

Metadata

Assignees

No fields configured for Feature.

Projects

Status
In Progress (8 max)

Relationships

None yet

Development

No branches or pull requests

Issue actions