fix(ci): resolve release tag from manifest so CD_production deploys

[jirhiker]

What

Replace the broken tag_name passthrough in release-please.yml with a manifest-derived tag resolver, so the production deploy (and forward-merge) actually receive the release tag.

Why

release-please-action@v5 does not populate a usable tag_name output in this manifest configuration. The action's run log shows it emits exactly two outputs — release_created and an empty tag_name — and no path-scoped (.--tag_name) outputs exist at all.

Consequence: CD_production's job gate

if: ${{ startsWith(inputs.tag_name || github.event.release.tag_name, 'v') }}

receives an empty inputs.tag_name → startsWith('', 'v') = false → the deploy job silently skips. Observed on both v1.1.1 and v1.1.2 (run 28806722930, 28808275126): the release/tag were created, the reusable workflow was invoked (so release_created propagated), but the inner job self-skipped. Both releases had to be shipped by manually re-publishing the GitHub release to fire the release: published path.

The forward-merge job consumes the same tag_name, so it was getting an empty tag too.

Fix

After the release step, resolve the tag from the released version in the branch-appropriate manifest:

tag="$ACTION_TAG"                       # prefer the action output if ever non-empty
if [ -z "$tag" ]; then
  version="$(jq -r '.["."]' "$MANIFEST")"
  tag="v${version}"                     # include-v-in-tag: true in both configs
fi

• MANIFEST follows the same staging/stable switch already used for manifest-file.
• Fails loudly if the version can't be read (no more silent skips).
• Only runs when release_created == 'true'.

Supersedes

PR #756 (already merged) added a .--tag_name fallback based on a path-scoped output key this configuration never emits — so it had no effect. This PR removes that dead fallback and replaces it with the manifest-derived resolver.

Note

This is CI-only. It needs to reach production (and thus future hotfix/* branches cut from release tags) via the normal forward-merge flow to fix auto-deploy on those lines.

🤖 Generated with Claude Code