ci: deploy website after the release pipeline publishes - #3123
Merged
Conversation
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Since the release-please migration, the draft release is published via
gh apiwithGITHUB_TOKEN, and GitHub suppresses workflow triggers for token-driven events, so therelease: publishedtrigger onwebsite.ymlnever fires. gitify.io has been stuck onv7.1.0whilev7.1.1andv7.2.0shipped.website.ymlnow acceptsworkflow_call, andrelease.ymlchains it as aneeds: publishjob so the Netlify build hook fires once every platform has uploaded and the draft is published. Therelease: publishedtrigger stays as a fallback for drafts published by hand through the UI.The build hook
curlalso gained--fail, so a 5xx from Netlify now fails the job instead of exiting 0 silently, and the secret moved intoenv:rather than being interpolated into the shell line.gitify.io still needs a one-offDone ✅gh workflow run website.ymlto catch up tov7.2.0; this change only takes effect from the next release.