Skip to content

chore(deps): update oras-project/setup-oras action to v2.0.4 - #695

Merged
mergeraptor[bot] merged 1 commit into
mainfrom
renovate/github-actions-(non-major)
Nov 18, 2026
Merged

mergeraptor[bot] merged 1 commit into
mainfrom
renovate/github-actions-(non-major)

Conversation

@mergeraptor

@mergeraptor mergeraptor Bot commented Nov 18, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
oras-project/setup-oras action patch v2.0.3 → v2.0.4

Release Notes

oras-project/setup-oras

v2.0.4

Compare Source

Highlights
  • Support ORAS CLI version(s): 1.4.0
What's Changed
New Contributors

Full Changelog: oras-project/setup-oras@v2.0.3...v2.0.4


Configuration

📅 Schedule: (UTC)

  • Branch creation
    • At any time (no schedule defined)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


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

This PR has been generated by Mend Renovate CLI.

@mergeraptor
mergeraptor Bot enabled auto-merge November 18, 2026 18:17
@jeefy
jeefy requested review from ahmedadan and daegalus November 18, 2026 18:17
@jeefy

jeefy commented Nov 18, 2026

Copy link
Copy Markdown
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign ahmedadan after the PR has been reviewed.
You can assign the PR to them by writing /assign @ahmedadan in a comment when ready.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@mergeraptor
mergeraptor Bot added this pull request to the merge queue Nov 18, 2026
@hivecommons-hive

hivecommons-hive Bot commented Nov 18, 2026 •

Copy link
Copy Markdown
Contributor

Hive status — updated in place; edits do not notify. Full history is in the Activity Monitor.

ℹ️ Sentinel: informational, author is trusted (allow-listed bot), merge is not blocked. Head 626e92c756d4 matched:

  • sensitive_path: changes 1 sensitive path(s) (.github/workflows/build.yml)

No sentinel-alert label was added. The finding is recorded in the dashboard Security tab and /api/sentinel; set sentinel.trusted_authors_block: true to block trusted authors too.

Review follow-ups: 1 open of 1 (below review.backlog.min_severity: P2)

Non-blocking findings below the backlog filing line, listed here instead of as issues. Tick them off as they are fixed; set review.backlog.min_severity: P3 to file every finding.

  • P3 info docs-currency — Workflow comment about setup-oras release table is out of date (.github/workflows/build.yml:723): build.yml:723 and :818 say 'setup-oras v2.0.1's built-in release table stops at ORAS 1.3.3'. At v2.0.4 the table includes 1.3.6 and 1.4.0. This is already on main; this PR does not touch those lines.…

@hivecommons-hive hivecommons-hive Bot added no-dco A commit is missing Signed-off-by — run `git rebase --signoff` role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) stage/050-review-pending Review swarm requested; awaiting a verdict for the current head labels Nov 18, 2026
Merged via the queue into main with commit ff74aff Nov 18, 2026
54 checks passed

@hivecommons-hive hivecommons-hive Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Summary: This updates a small helper used by the release pipeline to install ORAS, a tool that uploads release files to a container registry, from version 2.0.3 to 2.0.4. The exact ORAS download and its fingerprint stay the same, so releases should behave as before. One difference: the helper now sends the workflow's built-in GitHub login when downloading from GitHub. That is safe here, but worth knowing about. Nothing blocks merging.


Pinned commit ac735097e22fe643015b0d19645f7c9a69942128 checked against upstream tag v2.0.4 (it matches). Both call sites keep the same url and checksum for ORAS 1.3.6 (.github/workflows/build.yml:727-730, :821-824). So the installed binary is the same.

CI at this head: every build/release job shows skipped (only prow ran). The new action version has not run in this repo yet. The risk is low because its inputs did not change.

docs-currency (out-of-scope, was already there before this PR): the comments at .github/workflows/build.yml:723 and :818 say "setup-oras v2.0.1's built-in release table stops at ORAS 1.3.3". At v2.0.4 the table includes 1.3.6 and 1.4.0 (upstream src/lib/data/releases.json), so the comment is out of date. Suggested fix on main:

      # Pin the release the Justfile's oras_image names, by URL and checksum,
      # rather than following setup-oras's built-in default version.

No findings from: correctness, intent-alignment, style.

Confidence: 5/5 (safe)

— hive: agent=reviewer backend=claude model=claude-opus-5-5 effort=medium claude=2.1.326

# the release the Justfile's oras_image names, by URL and checksum.
- name: Set up oras
uses: oras-project/setup-oras@5e2f2482b30b0cb3e14e67f89a80c88c659a7c63 # v2.0.3
uses: oras-project/setup-oras@ac735097e22fe643015b0d19645f7c9a69942128 # v2.0.4

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

FYI (security, info): v2.0.4 adds a token input that defaults to github.token (upstream action.yml). src/setup.ts sends it as auth only when the download host is github.com, and masks it with core.setSecret. This job runs on pull requests (it checks out the PR head at :801-805), but the token is read-only for fork PRs and goes only to github.com. No change needed. If you want the download to send no login at all, add token: '' under with:. The same applies to the release job at line 727.

@jeefy

jeefy commented Nov 18, 2026

Copy link
Copy Markdown
Collaborator

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
To complete the pull request process, please assign ahmedadan after the PR has been reviewed.
You can assign the PR to them by writing /assign @ahmedadan in a comment when ready.

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@mergeraptor
mergeraptor Bot deleted the renovate/github-actions-(non-major) branch November 18, 2026 21:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-dco A commit is missing Signed-off-by — run `git rebase --signoff` role/trusted Author is trusted for unattended merge (trusted-author role or registry/claim tier in require_tiers) stage/050-review-pending Review swarm requested; awaiting a verdict for the current head

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant