chore(deps): bump googleapis/release-please-action from 4 to 5#2
Conversation
|
@dependabot rebase |
Bumps [googleapis/release-please-action](https://github.com/googleapis/release-please-action) from 4 to 5. - [Release notes](https://github.com/googleapis/release-please-action/releases) - [Changelog](https://github.com/googleapis/release-please-action/blob/main/CHANGELOG.md) - [Commits](googleapis/release-please-action@v4...v5) --- updated-dependencies: - dependency-name: googleapis/release-please-action dependency-version: '5' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
a3ad460 to
d9ec374
Compare
WalkthroughWalkthroughBoth GitHub Actions workflow files ( Changesrelease-please-action Version Bump
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Pre-merge checks | ✅ 4✅ Passed checks (4 passed)
Tip: You can configure your own custom pre-merge checks in the settings. Finishing TouchesGenerate unit tests (beta)
Simplify code
Comment |
There was a problem hiding this comment.
Nitpick comments (1)
.github/workflows/publish.yml (1)
18-18: ⚡ Quick winConsider pinning actions to commit hashes for supply chain security.
Both workflow files reference
googleapis/release-please-action@v5using a tag. Pinning to a commit hash (e.g.,@abc123...) instead of a mutable tag prevents potential supply chain attacks where an attacker compromises the v5 tag to point to malicious code.
.github/workflows/publish.yml#L18-L18: Pingoogleapis/release-please-action@v5to its release commit hash..github/workflows/release.yml#L22-L22: Pingoogleapis/release-please-action@v5to its release commit hash.Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/publish.yml at line 18, Both `.github/workflows/publish.yml` (line 18-18) and `.github/workflows/release.yml` (line 22-22) use a mutable tag reference for the googleapis/release-please-action action. To improve supply chain security, replace the `@v5` tag reference with a pinned commit hash at both locations. Find the current release commit hash for v5 of the googleapis/release-please-action repository and update both uses of `googleapis/release-please-action@v5` to `googleapis/release-please-action@<commit-hash>` to prevent potential tag manipulation attacks.Source: Linters/SAST tools
Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In @.github/workflows/publish.yml:
- Line 18: Both `.github/workflows/publish.yml` (line 18-18) and
`.github/workflows/release.yml` (line 22-22) use a mutable tag reference for the
googleapis/release-please-action action. To improve supply chain security,
replace the `@v5` tag reference with a pinned commit hash at both locations.
Find the current release commit hash for v5 of the
googleapis/release-please-action repository and update both uses of
`googleapis/release-please-action@v5` to
`googleapis/release-please-action@<commit-hash>` to prevent potential tag
manipulation attacks.
Review info
Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro Plus
Run ID: 3540c5c6-e71f-4670-a350-58605c985443
Files selected for processing (2)
.github/workflows/publish.yml.github/workflows/release.yml
Bumps googleapis/release-please-action from 4 to 5.
Release notes
Sourced from googleapis/release-please-action's releases.
... (truncated)
Changelog
Sourced from googleapis/release-please-action's changelog.
... (truncated)
Commits
45996edchore(main): release 5.0.0 (#1200)a8121b9chore: build dist (#1201)f533c26fix: bump release-please from 17.3.0 to 17.6.0 (#1199)46dfc01feat!: upgrade to node24 (#1188)Summary by CodeRabbit