docs: update Docker Compose setup guide to checkout latest
tag
#4695
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.
Type of Change
Description
This PR updates the release stable version workflow with a new step to update the
latest
tag to the newly created SemVer tag, and updates the Docker Compose setup guide to checkout thelatest
tag when cloning the repository.Motivation and Context
This would help prevent failures with starting the app server when running off of the
main
branch, specifically when a new enum variant has been introduced in themain
branch, but is not available in the latest stable release. Checking out the latest stable release when running the Docker Compose setup would ensure that a compatible configuration file would be used, and thus reduce server startup failures.How did you test it?
I've tested out the new step added in the stable release workflow by running the command locally, first by creating the
latest
tag manually to point to an old release, then by running the command to point to the latest stable release.Checklist
cargo +nightly fmt --all
cargo clippy