publish¶

The publish workflow publishes the snap(s) built during the run to the Snap Store, using the canonical/action-publish action. Each *.snap file found in the run artifacts is published.

The target channel is resolved as follows, in increasing precedence order:

by default, the snap is published to <track>/edge;
if the git ref is a tag, the snap is published to <track>/candidate;
if the snap-risk input is set, it takes precedence over both.

All snaps built from the git-ref branch are published to the same track defined by snap-track.

Usage¶

jobs:
  publish:
    needs: [build]
    permissions:
      contents: read
    uses: canonical/robotics-actions-workflows/.github/workflows/publish.yaml@main
    secrets:
      snapstore-login: ${{ secrets.SNAPSTORE_LOGIN }}

Note

This workflow expects the snap artifacts produced by the build workflow to be present in the same run.

Inputs¶

Input	Type	Default	Required	Description
`git-ref`	string	`${{ github.ref }}`	no	The branch that published the artifacts.
`snap-risk`	string	`''`	no	Snap Store channel risk used for publication. Defaults to `edge`, or to `candidate` when the git ref is a tag.
`snap-track`	string	`latest`	no	Snap Store channel track used for publication.

Secrets¶

Secret	Required	Description
`snapstore-login`	yes	Snap Store credential (see `snapcraft export-login`).

Outputs¶

The workflow declares no workflow outputs and uploads no artifacts. Its outcome is the published snap revision(s) on the resolved channel.

Permissions¶

contents: read