Skip to content
Open
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion action.yml
Original file line number Diff line number Diff line change
Expand Up @@ -30,4 +30,4 @@ outputs:

runs:
using: 'docker'
image: 'docker://ghcr.io/multimediallc/codeowners-plus:latest'
image: 'docker://ghcr.io/multimediallc/codeowners-plus@sha256:8f9b834d270546cfafa9b3e6774722a93e7178fbeb08415c1bc2e655bb7f8637'
4 changes: 2 additions & 2 deletions scripts/prepare-release.sh
Original file line number Diff line number Diff line change
Expand Up @@ -73,11 +73,11 @@ echo "Updating ${ACTIONS_FILE}, ${CLI_TOOL_FILE}, and ${README_FILE} to replace
# For GNU sed (Linux), -i without an argument is fine.
# For BSD sed (macOS), -i requires an argument (even if empty string for no backup).
if sed --version 2>/dev/null | grep -q GNU; then # GNU sed
sed -i "s|codeowners-plus:.*'|codeowners-plus:${VERSION_TAG}'|g" "${ACTIONS_FILE}"
sed -i "s|codeowners-plus[:@].*'|codeowners-plus:${VERSION_TAG}'|g" "${ACTIONS_FILE}"

Choose a reason for hiding this comment

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

🚩 post-release.sh not updated but likely intentional

The scripts/post-release.sh doesn't modify action.yml at all. Previously with :latest, this was fine because Docker would resolve to the newest image. Now with sha256 pinning, after a release cycle the main branch will retain the old sha256 digest in action.yml. This means the sha256 on main could become stale after a new release. However, this appears intentional — the sha256 pinning on main represents a known-good image and would be manually updated (as was done in this PR). The prepare-release.sh correctly handles converting whatever format is in action.yml to a :vX.Y.Z tag for the release branch/tag.

Staging: Open in Devin

Was this helpful? React with 👍 or 👎 to provide feedback.

Debug

Playground

sed -i "s|Version: .*|Version: \"${VERSION_TAG}\",|g" "${CLI_TOOL_FILE}"
sed -i "s|codeowners-plus@.*|codeowners-plus@${VERSION_TAG}|g" "${README_FILE}"
else # BSD sed (macOS)
sed -i '' "s|codeowners-plus:.*'|codeowners-plus:${VERSION_TAG}'|g" "${ACTIONS_FILE}"
sed -i '' "s|codeowners-plus[:@].*'|codeowners-plus:${VERSION_TAG}'|g" "${ACTIONS_FILE}"
sed -i '' "s|Version: .*|Version: \"${VERSION_TAG}\",|g" "${CLI_TOOL_FILE}"
sed -i '' "s|codeowners-plus@.*|codeowners-plus@${VERSION_TAG}|g" "${README_FILE}"
fi
Expand Down