Skip to content

Fix release sign target detection when passed as single argument#9199

Open
ShahanaFarooqui wants to merge 1 commit into
ElementsProject:masterfrom
ShahanaFarooqui:fix-ci-release-signing
Open

Fix release sign target detection when passed as single argument#9199
ShahanaFarooqui wants to merge 1 commit into
ElementsProject:masterfrom
ShahanaFarooqui:fix-ci-release-signing

Conversation

@ShahanaFarooqui
Copy link
Copy Markdown
Collaborator

@ShahanaFarooqui ShahanaFarooqui commented Jun 5, 2026

The sign target detection uses pattern matching that requires spaces on both sides of "sign" in the TARGETS variable. When only "sign" is passed as an argument, TARGETS becomes " sign" (leading space only), causing the condition to fail.

Add an additional pattern match to detect "sign" with a leading space but no trailing space, which occurs when "sign" is the only target or the last target in the list.

This regression seems to have been exposed by GitHub Actions runner updates (Ubuntu 22.04 → 24.04), which changed argument passing behavior.

Changelog-None: Fixes the release signing issue only.

Fixes #9198.

… argument

The sign target detection uses pattern matching that requires spaces on
both sides of "sign" in the TARGETS variable. When only "sign" is passed
as an argument, TARGETS becomes " sign" (leading space only), causing
the condition to fail.

Add an additional pattern match to detect "sign" with a leading space
but no trailing space, which occurs when "sign" is the only target or
the last target in the list.

This regression seems to have been exposed by GitHub Actions runner
updates (Ubuntu 22.04 → 24.04), which changed argument passing behavior.

Changelog-None: Fixes the release signing issue in CI only.
@ShahanaFarooqui ShahanaFarooqui linked an issue Jun 5, 2026 that may be closed by this pull request
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.

SHA256SUMS files didn't create with the release actions

1 participant