Skip to content

fix(ci): pass runtime publish credentials via step env - #165

Merged
santimattius merged 1 commit into
mainfrom
fix/publish-runtime-credentials-export
Nov 1, 2026
Merged

santimattius merged 1 commit into
mainfrom
fix/publish-runtime-credentials-export

Conversation

@santimattius

Copy link
Copy Markdown
Owner

Problem

The runtime-v0.1.0-ALPHA01 publish failed before Gradle ran:

line 6: export: `***': not a valid identifier

In publish-runtime.yml, export NAME=\ followed by an indented "$VAR" line joins into export NAME= "$VAR": the variable is set to empty and the secret becomes a separate argument. Failure happened at the export step, so nothing was uploaded to Maven Central.

Fix

Map the secrets directly to ORG_GRADLE_PROJECT_* in the step env: and run Gradle, the same approach publish.yml uses. No shell export needed.

Verification

  • Workflow YAML parses.
  • Not runnable locally; validated by re-running the release after merge.

@santimattius
santimattius changed the base branch from feat/coroutines-toolkit-runtime to main November 1, 2026 16:43
Line-continued export statements joined into 'export NAME=' followed by a
separate word, which failed with 'not a valid identifier' before Gradle
ran. Map the secrets directly to ORG_GRADLE_PROJECT_* env vars instead.
@santimattius
santimattius force-pushed the fix/publish-runtime-credentials-export branch from 7275e11 to 66b6d94 Compare November 1, 2026 16:44
@santimattius
santimattius merged commit 339e9ea into main Nov 1, 2026
2 of 3 checks passed
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.

1 participant