Improve releasing instructions post v0.4.0#4741
Merged
Merged
Conversation
After going through the Engine + CLI v0.4.0 release, as well as all SDKs & docs, these improvements made sense: - last updated badge - new high-level diagram - convert 👉 action items to [x] checklist items - optimise for top to bottom consumption The only contentious item might be the removal of post-release checks, i.e. #4461 . The manual checks are so simple - checking the `dagger version` output - that if we messed that up in our release process, we should add checks that would prevent a release from going through if that was to happen. Let's discuss this further in the PR. Signed-off-by: Gerhard Lazu <gerhard@dagger.io>
gerhard
requested review from
d3rp3tt3,
helderco,
mircubed,
sipsma,
slumbering and
vikram-dagger
Contributor
Author
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
2 participants
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.
After going through the Engine + CLI v0.4.0 release, as well as all SDKs & docs, these improvements made sense:
The only contentious item might be the removal of post-release checks, i.e. #4461 . The manual checks are so simple - checking the
dagger versionoutput - that if we messed that up in our release process, we should add checks that would prevent a release from going through if that was to happen. Let's discuss this further in the PR.