fix(ci): create release tags on the pushed commit instead of default branch

[Siumauricio]

softprops/action-gh-release creates the version tag without target_commitish, so the GitHub API places it on the default branch (canary) instead of the commit on main that was actually built. This is why the v0.29.14 tag pointed to a canary commit and its auto-generated notes listed unreleased features. target_commitish: ${{ github.sha }} pins the tag to the exact commit the workflow ran on.

Greptile Summary

Pins newly created release tags to the exact workflow commit rather than the repository’s default branch.

• Adds target_commitish: ${{ github.sha }} to the GitHub release action.
• Keeps release tags aligned with the commit used by the build and release jobs.

Confidence Score: 5/5

The PR appears safe to merge with no blocking or non-blocking issues identified.

The explicitly targeted commit is the same commit used for checkout, version extraction, and image builds, preserving release provenance across supported triggers.

_{Reviews (1): Last reviewed commit: "fix(ci): create release tags on the push..." | Re-trigger Greptile}