This repository has been archived by the owner on Aug 21, 2024. It is now read-only.
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.
What has changed?
How to run a staging release?
When running a staging release the latest branch commit will checked out.
Why don't we run the staging release on PRs?
Staging / production releases require AWS credentials. This would only work on PRs opened from branches within the organization but not on PRs opened from forks. There's also the possibility that forks could contain malicious code that we don't want to deploy into our infrastructure.
How to run a production release?
When running production releases, the latest release tag will be checked out.
How to tag a new release?
The easiest way to create a new release tag is to simply create a new release from the release menu in Github.
Make sure to use the next ascending release version and use the schema MAJOR.MINOR.PATCH
To read more about our release process see the documentation
Closes #683