Skip to content

packages.yaml workflow does not run on a new release. #5137

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
matifali opened this issue Nov 19, 2022 · 3 comments · Fixed by #5173
Closed

packages.yaml workflow does not run on a new release. #5137

matifali opened this issue Nov 19, 2022 · 3 comments · Fixed by #5173

Comments

@matifali
Copy link
Member

matifali commented Nov 19, 2022

packages.yaml was merged in main before 0.12.7 and 0.12.8 releases but it did not run both of the times.

It seems like the trigger,

on:
  release:
    types: [published]

is not working.

There is some context and a similar issue. googleapis/release-please#766

A workaround can be to change the trigger to,

on:
  workflow_run:
    workflows: [release]
    types:
      - completed

This will run the workflow after the release workflow.

Another approach is to create a separate token, as discussed here, https://github.com/orgs/community/discussions/26875

cc @deansheather

@matifali
Copy link
Member Author

matifali commented Nov 19, 2022

A manual run of the workflow also fails,
see the logs here,
https://github.com/matifali/coder/actions/runs/3503152146/jobs/5868221341

@deansheather
Copy link
Member

It's very odd that github isn't triggering it, but we can try this for sure

@matifali
Copy link
Member Author

matifali commented Nov 19, 2022

A manual run of the workflow also fails, see the logs here, https://github.com/matifali/coder/actions/runs/3503152146/jobs/5868221341

Also, a manual trigger is failing. Please check the log when you find the time.

kylecarbs pushed a commit that referenced this issue Nov 27, 2022
This commit is a workaround to run the `packages.yaml` action after the release action
Fixes #5137.
Check #5137 for context.
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 a pull request may close this issue.

2 participants