Skip to content

The snapcraft stable release doesn't trigger #14498

@bep

Description

@bep

Web hook events during a release:

  1. refs/tags/v0.155.1 HTTP 200, but body says that “The push event is not for the default branch”
  2. refs/heads/master HTTP 401 Unauthorised
  3. refs/heads/stable HTTP 200, but body says that “The push event is not for the default branch”

So, in the above,

  1. Is in the release branch (e.g. release-0.155.1)
  2. Merges the release branch to master (the last commit here is not the release tag).
  3. Is the force push of the release tag to the stable branch.

See

if grep -q 'Suffix:\s*""' common/hugo/version_current.go; then
for the "trigger logic".

Back when @anthonyfok managed this setup, he asked me to create the stable branch to trigger releases. That obviously does not work any more, and even if we fixed the HTTP 401 Unauthorised above, that commit is not the release commit.

I have tried what I can think of on the Snapcraft side of it, including removing and recreating the Snapcraft app/hook.

I have tried to get into the Snapcraft forum for a while, I'm still waiting on approval. This needs some input from ther Canonical/Snapcraft side.

Metadata

Metadata

Assignees

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions