Skip to content

JACOCO-117 Update GitHub Action to use version 7 for release workflow#196

Open
rombirli wants to merge 1 commit intomasterfrom
rombirli/gh-action-release-v7
Open

JACOCO-117 Update GitHub Action to use version 7 for release workflow#196
rombirli wants to merge 1 commit intomasterfrom
rombirli/gh-action-release-v7

Conversation

@rombirli
Copy link
Copy Markdown
Contributor

@rombirli rombirli commented May 5, 2026

No description provided.

@hashicorp-vault-sonar-prod hashicorp-vault-sonar-prod Bot changed the title Update GitHub Action to use version 7 for release workflow JACOCO-117 Update GitHub Action to use version 7 for release workflow May 5, 2026
@sonar-review-alpha
Copy link
Copy Markdown

sonar-review-alpha Bot commented May 5, 2026

Summary

Updates the gh-action_release workflow action from v6 to v7 in the release pipeline. This is a straightforward version bump to the SonarSource release automation action that handles publishing to Maven Central and other distribution channels.

What reviewers should know

What to check:

  • Review the gh-action_release v7 release notes for breaking changes or new requirements
  • Verify the v7 action still supports the same input parameters (publishToBinaries, mavenCentralSync) used in this workflow
  • Confirm this upgrade doesn't affect how artifacts are built, signed, or published

File modified: .github/workflows/release.yml (line 29 only)

This is a low-risk change unless v7 introduced incompatible parameter changes or new prerequisites.


  • Generate Walkthrough
  • Generate Diagram

🗣️ Give feedback

@hashicorp-vault-sonar-prod
Copy link
Copy Markdown

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

JACOCO-117

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.

LGTM! ✅

Clean, minimal change. The single-line bump from @v6 to @v7 in release.yml is the only modification, and no other workflow references gh-action_release — so there's no consistency gap elsewhere. The automated-release.yml workflow uses a different action (release-github-actions) and is unaffected.

The existing inputs (publishToBinaries, mavenCentralSync, slackChannel, version, releaseId, dryRun) and permissions (id-token: write, contents: write) are all carried over unchanged. Tag-based pinning (@v7 rather than a commit SHA) is consistent with how other SonarSource shared actions are referenced in this repo (e.g., release-github-actions@v1).

🗣️ Give feedback

@sonarqube-next
Copy link
Copy Markdown

sonarqube-next Bot commented May 5, 2026

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant