-
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Rotate release notes as part of the 0.6.4 release
- Loading branch information
1 parent
0c5dd63
commit 22a9252
Showing
2 changed files
with
8 additions
and
8 deletions.
There are no files selected for viewing
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,8 @@ | ||
## Handle release already existing when uploading release notes | ||
|
||
Previously, the uploading of release notes assumed that the release didn't exist yet. If the release already existed, the release notes upload would fail. | ||
|
||
Only working when a release didn't exist made sense for all our ponylang usage. However, for other projects that create assets as part of the build process and store them in GitHub releases rather than Cloudsmith, the release might already exist. | ||
|
||
Now, we will check to see if the release exists. If it does, we update it with our release notes. If it doesn't, we will create the release like we previously did. | ||
|
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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,8 +0,0 @@ | ||
## Handle release already existing when uploading release notes | ||
|
||
Previously, the uploading of release notes assumed that the release didn't exist yet. If the release already existed, the release notes upload would fail. | ||
|
||
Only working when a release didn't exist made sense for all our ponylang usage. However, for other projects that create assets as part of the build process and store them in GitHub releases rather than Cloudsmith, the release might already exist. | ||
|
||
Now, we will check to see if the release exists. If it does, we update it with our release notes. If it doesn't, we will create the release like we previously did. | ||
|
||