Skip to content

Update GitHub Actions dependencies (major)#85

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/major-github-actions-dependencies
Open

Update GitHub Actions dependencies (major)#85
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/major-github-actions-dependencies

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented May 1, 2026

This PR contains the following updates:

Package Type Update Change
SonarSource/gh-action_release action major v67.0.0
actions/checkout action major v5.0.1v6.0.2
actions/checkout action major v4v6
jdx/mise-action action major v3.6.3v4.0.1

Release Notes

SonarSource/gh-action_release (SonarSource/gh-action_release)

v7.0.0

Compare Source

What's Changed

The v7 generation complies with release and tag immutability.

Improvements

Breaking Change

Full Changelog: SonarSource/gh-action_release@6.8.1...7.0.0

actions/checkout (actions/checkout)

v6.0.2

Compare Source

v6.0.1

Compare Source

v6.0.0

Compare Source

v6

Compare Source

jdx/mise-action (jdx/mise-action)

v4.0.1: : Documentation and Internal Cleanup

Compare Source

A small maintenance release that updates the README documentation to reflect v4 and cleans up internal code. There are no functional changes to the action itself.

Changed
  • Updated all README examples to reference jdx/mise-action@v4, actions/checkout@v6, and current tool versions by @​deining in #​407 and #​408
  • Extracted getCwd() helper to deduplicate working directory resolution logic (internal refactor, no behavior change) by @​altendky in #​403
New Contributors

Full Changelog: jdx/mise-action@v4.0.0...v4.0.1

v4.0.0

Compare Source

What's Changed
New Contributors

Full Changelog: jdx/mise-action@v3...v4.0.0

v4

Compare Source


Configuration

📅 Schedule: (in timezone Europe/Berlin)

  • Branch creation
    • "before 6am on Monday"
  • Automerge
    • At any time (no schedule defined)

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

Rebasing: Never, or you tick the rebase/retry checkbox.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.


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

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot added the dependencies label May 1, 2026
@renovate renovate Bot requested a review from a team May 1, 2026 09:21
@hashicorp-vault-sonar-prod
Copy link
Copy Markdown

hashicorp-vault-sonar-prod Bot commented May 1, 2026

Renovate Jira issue ID: SONARJAVA-6324

@sonar-review-alpha
Copy link
Copy Markdown

sonar-review-alpha Bot commented May 1, 2026

Summary

⚠️ The PR description exceeded the analysis limit and was truncated. The review may not reflect all context.

This PR updates GitHub Actions to major versions across four workflows:

  • actions/checkout: v5.0.1 & v4 → v6.0.2 & v6 (updated in build.yml, unified-dogfooding.yml, and PrepareNextIteration.yml)
  • jdx/mise-action: v3.6.3 → v4.0.1 (updated in build.yml and unified-dogfooding.yml)
  • SonarSource/gh-action_release: v6 → 7.0.0 (updated in release.yml with breaking changes)

All references use pinned commit SHAs with version tags for reproducibility.

What reviewers should know

Critical review point: SonarSource/gh-action_release v7.0.0 introduces breaking changes:

  • version input is now required — verify it's being provided in release.yml
  • Action ownership of GitHub release publication changes — must not be triggered by the release published event; verify the trigger configuration is correct

Routine checks:

  • actions/checkout v6 changes tag handling (preserves annotations, explicit fetch-tags) — no breaking concerns for this repo
  • jdx/mise-action v4.0.1 is a maintenance release with no functional changes
  • All version updates are consistently applied across workflows

  • Generate Walkthrough
  • Generate Diagram

🗣️ Give feedback

@sonarqube-next
Copy link
Copy Markdown

sonarqube-next Bot commented May 1, 2026

Copy link
Copy Markdown

@sonar-review-alpha sonar-review-alpha Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The bump to gh-action_release v7.0.0 introduces two breaking changes that haven't been addressed — the release workflow will fail at runtime as-is. The other three action upgrades (checkout v6, mise-action v4) are clean and consistent.

🗣️ Give feedback

id-token: write
contents: write
uses: SonarSource/gh-action_release/.github/workflows/main.yaml@v6
uses: SonarSource/gh-action_release/.github/workflows/main.yaml@d9c158044abff69356475ff82b1f99b78dbd9d93 # 7.0.0
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

gh-action_release v7.0.0 requires the version input — it is now mandatory and missing from the with: block below. Without it the workflow will error immediately on invocation.

Additionally, v7.0.0's breaking change states the action must not be triggered by the release: published event — the action now owns GitHub release publication itself (reusing an existing draft). The trigger at the top of this file needs to change from release: published to workflow_dispatch. See the v6→v7 migration guide: https://github.com/SonarSource/gh-action_release/tree/7.0.0#migrating-from-v6-to-v7-draft-first-workflow_dispatch

  • Mark as noise


- name: Checkout Sources
uses: actions/checkout@v4
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

SHA comment says # v6 but build.yml and unified-dogfooding.yml annotate the same SHA (de0fac2e) as # v6.0.2. Update the comment to match so the pinned version is unambiguous at a glance.

Suggested change
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6
uses: actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd # v6.0.2
  • Mark as noise

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants