chore(deps): update go-junit-report from tag to SHA #32
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Updates the
go-junit-report
dependency from tag-based reference (@v0.9.1
) to SHA-based reference (@cc1f095d5cc5eca2844f5c5ea7bb37f6b9bf6cac
) in the GitHub Actions unit test workflow.Changes
.github/actions/unit-tests/action.yml
to use the specific commit SHA instead of the version tag forgo-junit-report
Why This Change
This change moves from relying on a mutable Git tag to a specific immutable commit SHA, providing better dependency stability and reproducibility in our CI/CD pipeline.
Testing
Human Review Checklist
cc1f095d5cc5eca2844f5c5ea7bb37f6b9bf6cac
is the correct commit forgo-junit-report
v0.9.1go-junit-report@v0.9.1
in the repositoryRequirements
Related issues
go-junit-report
across 13 LaunchDarkly Go repositoriesAdditional context