Prepare v0.6.4 release #5486
Merged
Prepare v0.6.4 release #5486
Conversation
This file contains 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
These happen on every merge commit, they are not nightlies (even though GoReleaser calls them that). Signed-off-by: Gerhard Lazu <gerhard@dagger.io>
gerhard
commented
Jul 19, 2023
gerhard
force-pushed
the
prepare-0.6.4-release
branch
3 times, most recently
from
ba802f0
to
746e151
Compare
|
Do you need to run |
changie batch patch Signed-off-by: Gerhard Lazu <gerhard@dagger.io>
Replace anything that GoReleaser generates with our changie generated release notes. Signed-off-by: Gerhard Lazu <gerhard@dagger.io>
Signed-off-by: Gerhard Lazu <gerhard@dagger.io>
Signed-off-by: Gerhard Lazu <gerhard@dagger.io>
This will be automated, the first step is to document. Signed-off-by: Gerhard Lazu <gerhard@dagger.io>
gerhard
force-pushed
the
prepare-0.6.4-release
branch
from
746e151
to
b50f18b
Compare
No, the SDK release notes are created after the Engine & CLI get bumped. So after the Engine & CLI are released, the release notes for the SDKs start. |
|
I just checked on my fork that this works as expected: https://github.com/gerhard/dagger/releases/tag/v0.6.4 
Converting this PR to ready for review so that we can finally merge & produce the Engine & CLI releases. |
helderco
approved these changes
Jul 19, 2023
sipsma
pushed a commit
to sipsma/dagger
that referenced
this pull request
Jul 29, 2023
* Clarify that nightly release is actually dev release
These happen on every merge commit, they are not nightlies (even though
GoReleaser calls them that).
Signed-off-by: Gerhard Lazu <gerhard@dagger.io>
* Generate Engine & CLI release notes for the upcoming version
changie batch patch
Signed-off-by: Gerhard Lazu <gerhard@dagger.io>
* Use changie generated changelog for the release notes
Replace anything that GoReleaser generates with our changie generated
release notes.
Signed-off-by: Gerhard Lazu <gerhard@dagger.io>
* Bump GoReleaser to latest stable
Signed-off-by: Gerhard Lazu <gerhard@dagger.io>
* Replace deprecated --rm-dist in GoRelease with --clean
Signed-off-by: Gerhard Lazu <gerhard@dagger.io>
* Add release notes PR to RELEASING
This will be automated, the first step is to document.
Signed-off-by: Gerhard Lazu <gerhard@dagger.io>
---------
Signed-off-by: Gerhard Lazu <gerhard@dagger.io>
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.
The primary difference as of this release is that we generate release notes with
changiebefore releasing, and we use this file in GoReleaser. For now this is manual, but it will be automated as soon as we are confident that this is the right approach.Opening as a draft PR, want to double-check in my fork that releasing works as expected (wouldn't want to have to fix issues half-way through releasing).