Skip to content
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

ci(release.yml): only recreate canary once all artifacts are ready to upload #85

Merged
merged 1 commit into from
Sep 14, 2023

Conversation

vdice
Copy link
Member

@vdice vdice commented Sep 14, 2023

… upload

Signed-off-by: Vaughn Dice <vaughn.dice@fermyon.com>
tag: canary
allowUpdates: true
prerelease: true
artifacts: "cloud*.tar.gz,cloud.json,checksums-canary.txt"
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think the downloaded artifacts are nested in a folder. so it would have to be cloud.json/cloud.json and such.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yea, I thought so as well at first, but I emulated what fermyon/spin does; appears to work on my fork: https://github.com/vdice/cloud-plugin/actions/runs/6190247031

@vdice vdice merged commit 78c325a into fermyon:main Sep 14, 2023
8 checks passed
@vdice vdice deleted the ci/fix-canary branch September 14, 2023 21:25
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.

CI: delete/recreate canary only when all artifacts are ready
2 participants