Thanks to visit codestin.com
Credit goes to github.com

Skip to content

chore(deps): update release-plz/action digest to e879257#171

Merged
renovate[bot] merged 1 commit into
mainfrom
renovate/release-plz-action-digest
Jun 12, 2026
Merged

chore(deps): update release-plz/action digest to e879257#171
renovate[bot] merged 1 commit into
mainfrom
renovate/release-plz-action-digest

Conversation

@renovate

@renovate renovate Bot commented Jun 12, 2026

Copy link
Copy Markdown
Contributor

This PR contains the following updates:

Package Type Update Change
release-plz/action (changelog) action digest 064f4d1e879257

Configuration

📅 Schedule: (in timezone America/Chicago)

  • Branch creation
    • Only on Friday (* * * * 5)
  • Automerge
    • At any time (no schedule defined)

🚦 Automerge: Enabled.

Rebasing: Whenever PR is behind base branch, 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 was generated by Mend Renovate. View the repository job log.

Summary by CodeRabbit

  • Chores
    • Updated CI/CD release automation workflow to use the latest version of release tooling.

@renovate renovate Bot enabled auto-merge (squash) June 12, 2026 06:00
@greptile-apps

greptile-apps Bot commented Jun 12, 2026

Copy link
Copy Markdown

PR author is in the excluded authors list.

@coderabbitai

coderabbitai Bot commented Jun 12, 2026

Copy link
Copy Markdown

Review Change Stack

📝 Walkthrough

Walkthrough

The PR updates the pinned commit SHA for the release-plz/action step in .github/workflows/release-plz.yml to a new revision of the v0.5 action. No workflow structure, triggers, job configuration, or environment variables are modified.

Changes

Release Workflow Maintenance

Layer / File(s) Summary
Release workflow action pin update
.github/workflows/release-plz.yml
The release-plz/action step is pinned to a new commit SHA for the v0.5 action version.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

  • jdx/demand#167: Also updates a pinned commit SHA in .github/workflows/release-plz.yml for release-plz-related actions.

Poem

🐰 A pin so small, yet true and bright,
One commit hash now shines with light,
Release-plz v0.5, fresh and new,
Hopping forward, workflows too!

🚥 Pre-merge checks | ✅ 5
✅ Passed checks (5 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title accurately describes the main change: updating the release-plz/action GitHub Action digest to a specific commit SHA (e879257).
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Comment @coderabbitai help to get the list of available commands and usage tips.

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

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/release-plz.yml:
- Line 20: The workflow uses a pinned commit for release-plz/action
(`release-plz/action@e8792575c7f2366cf6ff3ccc33ead9ace5b691c7`) but the trailing
comment `# v0.5` points to a different commit; fix by updating the pinned SHA to
the commit that the v0.5 tag references (or remove/update the `# v0.5` comment
if you intend to pin a different commit) so the pin and tag annotation are
consistent in the release-plz action invocation; ensure tokens/permissions
(RELEASE_PLZ_TOKEN, CARGO_REGISTRY_TOKEN and contents: write / pull-requests:
write) remain intact.
🪄 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: Pro Plus

Run ID: 95332f2b-ead3-406a-a57b-3cbd13cb0315

📥 Commits

Reviewing files that changed from the base of the PR and between f9ab9b6 and e354c45.

📒 Files selected for processing (1)
  • .github/workflows/release-plz.yml

fetch-depth: 0
- uses: dtolnay/rust-toolchain@29eef336d9b2848a0b548edc03f92a220660cdb8 # stable
- uses: release-plz/action@064f4d1e36c843611ddf013be726beaa4ad804db # v0.5
- uses: release-plz/action@e8792575c7f2366cf6ff3ccc33ead9ace5b691c7 # v0.5

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟠 Major

🧩 Analysis chain

🏁 Script executed:

#!/bin/bash
# Description: Verify the release-plz/action commit SHA corresponds to v0.5

# Fetch the v0.5 tag and verify the commit SHA
echo "Checking if commit e8792575c7f2366cf6ff3ccc33ead9ace5b691c7 exists and matches v0.5..."
gh api repos/release-plz/action/commits/e8792575c7f2366cf6ff3ccc33ead9ace5b691c7 --jq '{sha: .sha, commit_message: .commit.message, author_date: .commit.author.date}'

echo -e "\nFetching v0.5 tag information..."
gh api repos/release-plz/action/git/ref/tags/v0.5 --jq '{ref: .ref, sha: .object.sha}'

echo -e "\nChecking for security advisories..."
gh api graphql -f query='
{
  repository(owner: "release-plz", name: "action") {
    vulnerabilityAlerts(first: 5) {
      nodes {
        securityVulnerability {
          advisory {
            summary
            severity
            publishedAt
          }
        }
      }
    }
  }
}'

Repository: jdx/demand

Length of output: 595


🌐 Web query:

release-plz/action v0.5 changelog or commit e879257

💡 Result:

I can’t reliably identify the changelog entry for commit e879257 in release-plz/action v0.5, because none of the web results I found contain that commit hash (e879257) or map it to a specific release (v0.5.x) / changelog section in the action repository. What I can confirm from authoritative sources: 1) The official repository release feed exists at https://github.com/release-plz/action/releases, and it lists many “What’s Changed” items per tag, but the search results shown here don’t surface an entry for e879257 specifically. 2) release-plz/action’s latest recorded release (as surfaced in the results) is v0.5.128 (2026-03-07), but that still doesn’t connect to e879257. If you can provide either (a) the full commit SHA for e879257 (7 hex is ambiguous), or (b) the specific v0.5.x tag that contains that commit, I can pinpoint the exact changelog lines for that change. As-is, any attempt to attribute “e879257” to a particular v0.5 changelog would be guesswork.

Citations:


Fix release-plz/action pin/tag mismatch (v0.5)

This workflow has contents: write / pull-requests: write and uses RELEASE_PLZ_TOKEN + CARGO_REGISTRY_TOKEN, so the action version pin needs to be consistent. The commit release-plz/action@e8792575c7f2366cf6ff3ccc33ead9ace5b691c7 exists, but the v0.5 tag points to d22c02a7cf6d7870bd163be7c7d9518d331aef34, so the # v0.5 annotation is inconsistent with the pinned SHA.

Update the pinned SHA to the v0.5 tag’s commit (or remove/update the # v0.5 comment if intentionally not using the v0.5 tag).

Security-advisory lookup for release-plz/action requires authenticated GitHub API access (the unauthenticated call fails); run it with proper auth or check the repo’s security advisories before merging.

🤖 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/release-plz.yml at line 20, The workflow uses a pinned
commit for release-plz/action
(`release-plz/action@e8792575c7f2366cf6ff3ccc33ead9ace5b691c7`) but the trailing
comment `# v0.5` points to a different commit; fix by updating the pinned SHA to
the commit that the v0.5 tag references (or remove/update the `# v0.5` comment
if you intend to pin a different commit) so the pin and tag annotation are
consistent in the release-plz action invocation; ensure tokens/permissions
(RELEASE_PLZ_TOKEN, CARGO_REGISTRY_TOKEN and contents: write / pull-requests:
write) remain intact.

@renovate renovate Bot merged commit babe0ed into main Jun 12, 2026
7 of 8 checks passed
@renovate renovate Bot deleted the renovate/release-plz-action-digest branch June 12, 2026 06:07
@jdx jdx mentioned this pull request Jun 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.

0 participants