Fix Sentry releases - incorrect sha truncation

[bruno-garcia]

https://nugettrends.sentry.io/explore/releases/?project=1266317&statsPeriod=1h

Deployment is using on
NuGetTrends.Web@1.0.0+97dd139f

Live telemetry is sending: NuGetTrends.Web@1.0.0+97dd139f
CLI/deployment is using: NuGetTrends.Web@1.0.0+97dd139faddb03aceea1b32645674ba028ec75ac

So 1 release has commit info and is Finalized. And the other has actual error/transactions etc.

[bruno-garcia]

Root Cause

There's a SHA truncation mismatch between what the running app reports to Sentry and what the deploy workflow registers as a Sentry release.

At build time — both web-workflow.yml and scheduler-workflow.yml:

dotnet build -c Release -p:SourceRevisionId=${GITHUB_SHA::8}

This bakes the 8-character truncated SHA into the assembly's InformationalVersion (e.g., 1.0.0+97dd139f). The Sentry .NET SDK auto-detects this, so the running app tags all events with:
NuGetTrends.Web@1.0.0+97dd139f

At deploy time — deploy.yml in nuget-trends-infra:

version: NuGetTrends.Web@1.0.0+${{ steps.images.outputs.web_full_sha }}

The deploy workflow expands the short SHA back to the full 40-character SHA via the GitHub API and creates the Sentry release as:
NuGetTrends.Web@1.0.0+97dd139faddb03aceea1b32645674ba028ec75ac

Result: Sentry sees two different releases — one with commit info (full SHA, from deploy) but no events, and one receiving all live events (short SHA, from app) but no commit info.

Note: The SPA side is already consistent — it uses git rev-parse HEAD (full SHA) everywhere.

Fix Options

Either direction works — the key is making the SHA length consistent:

Option A: Use full SHA in build workflows (change nuget-trends repo)

• web-workflow.yml:122 and scheduler-workflow.yml:71: change ${GITHUB_SHA::8} → ${GITHUB_SHA}
• Deploy workflow stays as-is

Option B: Use truncated SHA in deploy workflow (change nuget-trends-infra repo)

• Change the three Sentry release steps in deploy.yml to use the short SHA in the version string
• Can also simplify get_image_info by removing the GitHub API call to expand the SHA (no longer needed)
• Build workflows stay as-is

set_commits: auto in the Sentry action associates commits via git history, not by parsing the SHA from the version string, so either approach works for commit association.