Bump dependabot/fetch-metadata from 2 to 3#43
Conversation
Bumps [dependabot/fetch-metadata](https://github.com/dependabot/fetch-metadata) from 2 to 3. - [Release notes](https://github.com/dependabot/fetch-metadata/releases) - [Commits](dependabot/fetch-metadata@v2...v3) --- updated-dependencies: - dependency-name: dependabot/fetch-metadata dependency-version: '3' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
dependabot
Bot
added
dependencies
Summary by CodeRabbit
WalkthroughThe Dependabot auto-merge GitHub Actions workflow's fetch-metadata action is updated from version 2 to version 3. No other workflow logic, conditions, or steps were modified. ChangesDependabot Auto-Merge Action Version Upgrade
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~1 minute 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: dependabot[bot] The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
openshift-ci
Bot
added
the
needs-ok-to-test
|
Hi @dependabot[bot]. Thanks for your PR. I'm waiting for a openshift-online member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 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.
Inline comments:
In @.github/workflows/dependabot-auto-merge.yml:
- Line 24: Replace the mutable tag in the GitHub Actions step that currently
reads "uses: dependabot/fetch-metadata@v3" with a full immutable commit SHA for
dependabot/fetch-metadata; locate the "uses: dependabot/fetch-metadata@v3" entry
in the workflow and swap the "@v3" suffix for the repository commit hash (e.g.,
@<full-commit-sha>) so the action is pinned to a specific commit.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: CHILL
Plan: Enterprise
Run ID: 2c3832dd-45b1-4128-ad82-8f737da423d8
📒 Files selected for processing (1)
.github/workflows/dependabot-auto-merge.yml
| - name: Fetch Dependabot Metadata | ||
| id: metadata | ||
| uses: dependabot/fetch-metadata@v2 | ||
| uses: dependabot/fetch-metadata@v3 |
There was a problem hiding this comment.
🧩 Analysis chain
🏁 Script executed:
#!/bin/bash
set -euo pipefail
REPO="dependabot/fetch-metadata"
TAG="v3"
echo "Latest release tag:"
LATEST_TAG=$(gh api "repos/${REPO}/releases/latest" --jq '.tag_name')
echo "$LATEST_TAG"
echo "Commit SHA for ${TAG} (dereferenced if annotated):"
SHA=$(git ls-remote "https://github.com/${REPO}.git" "refs/tags/${TAG}^{}" | awk '{print $1}')
if [[ -z "${SHA}" ]]; then
SHA=$(git ls-remote "https://github.com/${REPO}.git" "refs/tags/${TAG}" | awk '{print $1}')
fi
echo "${SHA}"Repository: openshift-online/rosa-e2e
Length of output: 184
Pin dependabot/fetch-metadata to a full commit SHA instead of a mutable tag.
Using @v3 keeps this workflow vulnerable to tag retargeting. Pinning to an immutable SHA materially improves supply-chain safety with minimal maintenance cost.
🔒 Suggested change
- uses: dependabot/fetch-metadata@v3
+ uses: dependabot/fetch-metadata@25dd0e34f4fe68f24cc83900b1fe3fe149efef98 # v3.1.0📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| uses: dependabot/fetch-metadata@v3 | |
| uses: dependabot/fetch-metadata@25dd0e34f4fe68f24cc83900b1fe3fe149efef98 # v3.1.0 |
🤖 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/dependabot-auto-merge.yml at line 24, Replace the mutable
tag in the GitHub Actions step that currently reads "uses:
dependabot/fetch-metadata@v3" with a full immutable commit SHA for
dependabot/fetch-metadata; locate the "uses: dependabot/fetch-metadata@v3" entry
in the workflow and swap the "@v3" suffix for the repository commit hash (e.g.,
@<full-commit-sha>) so the action is pinned to a specific commit.
|
/ok-to-test |
openshift-ci
Bot
added
ok-to-test
1 participant
Bumps dependabot/fetch-metadata from 2 to 3.
Release notes
Sourced from dependabot/fetch-metadata's releases.
... (truncated)
Commits
25dd0e3v3.1.0 (#692)e073f50Merge pull request #705 from dependabot/dependabot/npm_and_yarn/hono-4.12.140670e16build(deps-dev): bump hono from 4.12.12 to 4.12.147a7fe10Merge pull request #702 from dependabot/dependabot/npm_and_yarn/dependencies-...5168191Updating dist build23882e1build(deps): bump@actions/githubin the dependencies group1072469Merge pull request #701 from dependabot/dependabot/github_actions/actions/cre...43f8a00build(deps): bump actions/create-github-app-token from 3.0.0 to 3.1.1b4d904aMerge pull request #703 from dependabot/dependabot/npm_and_yarn/globals-17.5.0c8046bbbuild(deps-dev): bump globals from 17.4.0 to 17.5.0Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR:
@dependabot rebasewill rebase this PR@dependabot recreatewill recreate this PR, overwriting any edits that have been made to it@dependabot show <dependency name> ignore conditionswill show all of the ignore conditions of the specified dependency@dependabot ignore this major versionwill close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this minor versionwill close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)@dependabot ignore this dependencywill close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)