Merged
Conversation
There is a lot of output when syncing files, reduce it by setting progress-frequency
416a63f to
316d493
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates the deployment workflow to publish a latest_version marker file alongside editor UI releases, enabling downstream deployments (e.g. editor-standalone) to discover and use the most recent released build.
Changes:
- Upload a
latest_versionfile to the S3 bucket root during tag-based releases. - Purge Cloudflare cache for the
latest_versionURL. - Make the automated “bump version” PRs open as drafts.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| .github/workflows/deploy.yml | Adds S3 upload of latest_version on tag releases and purges its Cloudflare cache entry. |
| .github/workflows/bump-version.yml | Changes the version-bump workflow to create draft PRs. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
We can use this value in the standalone release script to always use the most recently released editor-ui The biggest risk I could think of with this is that an tag added to an old commit (or even a new, unreleased commit) could cause the latest-version to be updated. To prevent this, the latest_release file is only updated if the tag matches the contents in the package.json file.
It currently only runs tests if you make it as draft and then open it again. If we mark it as draft there is one less step.
316d493 to
b81acdf
Compare
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
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.
Related to: https://github.com/RaspberryPiFoundation/digital-editor-issues/issues/1245
This updates a 'latest_version' file in the bucket when editor ui is released. We'll use this file when editor-standalone is deployed to make sure we're on the latest version.
See commits for more.