Add container image reference to release notes

[aravindtga]

After the image is pushed to GHCR, the workflow now appends the container image reference to the GitHub release notes.

Fixes kptdev/kpt#4478

Changes

• Read the image base path from the function's metadata.yaml and append the version tag to construct the full image reference
• Append a "Container Image" section to the release notes with the image ref

Testing

Verified in a personal fork by creating a draft release and triggering the workflow with a test tag. The image reference was correctly read from metadata.yaml and appended to the release notes.

• https://github.com/aravindtga/krm-functions-catalog/releases/tag/functions%2Fgo%2Fupsert-resource%2Fv0.2.3
• https://github.com/aravindtga/krm-functions-catalog/actions/runs/24574921580/job/71857614157 (Image details gets updated in release body)
• https://github.com/aravindtga/krm-functions-catalog/actions/runs/24574921580/job/71860296655 (Image reference already exists case)

[netlify]

✅ Deploy Preview for krm-function-catalog canceled.

Name	Link
🔨 Latest commit	f008bb2
🔍 Latest deploy log	https://app.netlify.com/projects/krm-function-catalog/deploys/69e26040871a210008320a42

[Copilot]

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Updates the post-tag workflow to read a function’s container image reference from metadata.yaml and append it to the corresponding GitHub Release notes after publishing.

Changes:

• Elevates workflow contents permission to allow editing release notes.
• Extracts image: base from functions/go/<image_name>/metadata.yaml and constructs <base>:<version>.
• Appends a “Container Image” section to the release notes when missing.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[efiacor]

Very cool. Thanks for this