Skip to content

fix(ci): gate Snap publish on SNAPCRAFT_STORE_CREDENTIALS presence#124

Merged
ferhimedamine merged 1 commit into
mainfrom
fix/snap-credentials-gate
Jul 16, 2026
Merged

fix(ci): gate Snap publish on SNAPCRAFT_STORE_CREDENTIALS presence#124
ferhimedamine merged 1 commit into
mainfrom
fix/snap-credentials-gate

Conversation

@ferhimedamine

Copy link
Copy Markdown
Contributor

Problem

Publish Snap fails on every release with login_data is empty because SNAPCRAFT_STORE_CREDENTIALS repo secret is empty. The step has no guard, making the whole release page show red on Snap.

Fix

  1. Add HAS_SNAP_CREDS: ${{ secrets.SNAPCRAFT_STORE_CREDENTIALS != '' }} to job-level env
  2. Gate the publish step with if: env.HAS_SNAP_CREDS == 'true'
  3. Add a skip-notice step that emits a ::warning:: annotation explaining how to enable publishing

Snap build still runs on every release so the snap artifact is validated.

To enable Snap publishing

Founder must run:

snapcraft export-login --snaps dk --channels stable

and paste the output as SNAPCRAFT_STORE_CREDENTIALS secret at https://github.com/dakera-ai/dakera-cli/settings/secrets/actions

Closes DAK-7456.

Without this gate, every release shows Publish Snap as red because
the secret is empty. Now the publish step is skipped (not failed)
when the secret is unset, with a warning in the CI log.

Build still runs so the snap artifact is validated on every release.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
@ferhimedamine ferhimedamine merged commit 6443e65 into main Jul 16, 2026
5 of 6 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