chore(ci): mark github releases as pre-release #1152
Merged
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 issue(s)
Resolves #
Description
Summary of changes
This marks the GitHub Release that is produced by Release-Please as a "Pre-release" (see https:/phated/phated/releases for an example).
Noirup and our various guides utilize the "latest" release because GitHub provides a handy redirect: https:/noir-lang/noir/releases/latest and sometimes the docs and demos lag behind. This change allows the previous release to be marked as "latest" until we manually update the GitHub Release to be latest (such as when documentation is done).
Note: In the PR that added this feature on Release-Please, they restricted it to 0.x.x versions, which would not work for our workflow after 1.0; however, I think this decision was arbitrary and I'll work with them to allow this to be applied to any release versions.
Dependency additions / changes
Test additions / changes
Checklist
cargo fmt
with default settings.Documentation needs
Additional context