Skip to content

fix(ci): use literal environment name/url in release.yml - #122

Merged
Bre77 merged 1 commit into
mainfrom
fm/tfa-release-workflow-env-fix
Aug 13, 2026
Merged

fix(ci): use literal environment name/url in release.yml#122
Bre77 merged 1 commit into
mainfrom
fm/tfa-release-workflow-env-fix

Conversation

@Bre77

@Bre77 Bre77 commented Aug 13, 2026

Copy link
Copy Markdown
Member

Fixes the release workflow so tag pushes actually run: the publish-to-pypi job's environment: key interpolated ${{ env.ENVIRONMENT_NAME }} / ${{ env.PYPI_PROJECT_URL }}, but GitHub Actions cannot evaluate the env context in a job-level environment: key. This caused every tag push (including v1.9.0) to schedule 0 jobs and fail immediately, before any check run was even created.

Replaces both with literal values (name: pypi, the literal PyPI project URL) — no other changes.

Once this merges, v1.9.0's publish will be re-triggered (re-push the tag at the new merge commit) to actually gate CI and publish to PyPI.

The env context cannot be evaluated in a job-level environment key,
so tag pushes scheduled 0 jobs and the release workflow never ran.
@Bre77 Bre77 added the fm Opened by a Firstmate crewmate label Aug 13, 2026
@Bre77
Bre77 merged commit 83ce38e into main Aug 13, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

fm Opened by a Firstmate crewmate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant