Describe your problem
When a function is released, the CI pipeline builds and pushes a container image to GHCR, but the release notes contain no reference to it. As seen in #1226, the documentation now links to the latest release page, but the release itself has no mention of the published image.
A direct link to a specific image version on GHCR cannot be constructed from the version tag alone, the URL requires a unique numeric identifier (e.g./pkgs/container/.../<id>?tag=v0.1.5) that can only be obtained via the GitHub Packages API.
The expectation is to query the GHCR registry or the GitHub Packages API during the release workflow to resolve the image URL, and append it to the release notes automatically. This would give consumers a direct link to the published image alongside the release.
Describe your problem
When a function is released, the CI pipeline builds and pushes a container image to GHCR, but the release notes contain no reference to it. As seen in #1226, the documentation now links to the latest release page, but the release itself has no mention of the published image.
A direct link to a specific image version on GHCR cannot be constructed from the version tag alone, the URL requires a unique numeric identifier (e.g.
/pkgs/container/.../<id>?tag=v0.1.5) that can only be obtained via the GitHub Packages API.The expectation is to query the GHCR registry or the GitHub Packages API during the release workflow to resolve the image URL, and append it to the release notes automatically. This would give consumers a direct link to the published image alongside the release.