Skip to content

Map the release key into the reusable release workflows - #4

Merged
pjhartlieb merged 1 commit into
devfrom
fix/release-key-mapping
Oct 29, 2026
Merged

pjhartlieb merged 1 commit into
devfrom
fix/release-key-mapping

Conversation

@pjhartlieb

Copy link
Copy Markdown
Contributor

The first release run (40890779963) stopped at credentials: the release App key reached release-check.yml empty. Nothing was published or tagged.

A reusable workflow's environment: job gets an environment secret only when the caller passes it, by secrets: inherit or by a same-name mapping. Declaring it under workflow_call alone isn't enough. Checked in a sandbox with a dummy secret, controls included.

  • release.yml maps BLS_RELEASE_PRIVATE_KEY into both release-check.yml and publish.yml. A mapping rather than inherit, so only the key is passed.
  • The secret's description in both workflows, and the README, tell callers to map it.

The version stays 1.0.0; no v1.0.0 tag exists yet.

A reusable workflow's environment job gets an environment secret only when the caller passes it,
by secrets: inherit or by a same-name mapping. Declaring it under workflow_call alone leaves it
empty, which stopped the first release at the credentials job.
@pjhartlieb
pjhartlieb requested a review from a team as a code owner October 29, 2026 16:45
@pjhartlieb
pjhartlieb merged commit fcbdc77 into dev Oct 29, 2026
14 checks passed
@pjhartlieb pjhartlieb mentioned this pull request Oct 29, 2026
@pjhartlieb pjhartlieb mentioned this pull request Oct 29, 2026
@pjhartlieb
pjhartlieb deleted the fix/release-key-mapping branch October 30, 2026 19:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants