Repository navigation
ci: update Patch Release Me to digest-pinned 0.6.7 - #270
Conversation
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Dependency Review✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.Snapshot WarningsEnsure that dependencies are being submitted on PR branches and consider enabling retry-on-snapshot-warnings. See the documentation for more information and troubleshooting advice. Scanned Files
|
There was a problem hiding this comment.
Copilot review overview
Review tier: Lite
Findings: None
What changed in this PR
This PR updates the release workflow to use a digest-pinned container image for Patch Release Me, avoiding an unusable action reference and ensuring the exact bytes executed are immutable.
Changes:
- Switch the “Patch Release Me” step from a repository action ref to
docker://ghcr.io/...:0.6.7@sha256:...(digest-pinned). - Pass the bump mode via the Docker action
argsinput instead of the actionmodeinput. - Add a TODO + link documenting when it’s safe to switch back to the upstream repository action.
| File | Description |
|---|---|
| .github/workflows/release.yml | Updates Patch Release Me invocation to a digest-pinned OCI image and routes bump mode via args. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
The Both runs reported the same database-schema incompatibility while importing existing YAML test fixtures: The failures are in the OpenAPI, Helm, and CloudFormation library tests. This PR changes only |
Summary
argsinput.Why
The 0.6.6 container image was never published. Version 0.6.7 restores the image and fixes mode argument handling.
Using
docker://...:0.6.7@sha256:...also pins the executed container bytes. The repository action is not used yet because its Dockerfile still references a mutable image tag.Validation
git diff --check.docker buildx imagetools inspect.