fix(ci): fetch previous tag from git instead of API #1127
Merged
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
Previously the release info script would query the GitHub HTTP API and retrieve the latest "Release" (git tag) published. The latest "Release" could (likely) be for a different `release-*` branch or even `master` rather than the previous tag on the same branch as the new tag. This resulted in "Release" changelogs containing commits that dont exist in the tags history. By instead querying git itself we can fetch the previous tag in history and then generate an accurate changelog, eg: between `v1.7.4` and `v1.7.3` rather than potentially `v1.7.4` and `v1.10.0`. Run script through `shellcheck` and `shfmt`.
dbyron-sf
approved these changes
Apr 27, 2022
|
@Mergifyio backport release-1.27.x release-1.28.x |
mergify bot
pushed a commit
that referenced
this pull request
Apr 27, 2022
Previously the release info script would query the GitHub HTTP API and retrieve the latest "Release" (git tag) published. The latest "Release" could (likely) be for a different `release-*` branch or even `master` rather than the previous tag on the same branch as the new tag. This resulted in "Release" changelogs containing commits that dont exist in the tags history. By instead querying git itself we can fetch the previous tag in history and then generate an accurate changelog, eg: between `v1.7.4` and `v1.7.3` rather than potentially `v1.7.4` and `v1.10.0`. Run script through `shellcheck` and `shfmt`. (cherry picked from commit 8eac542)
mergify bot
pushed a commit
that referenced
this pull request
Apr 27, 2022
Previously the release info script would query the GitHub HTTP API and retrieve the latest "Release" (git tag) published. The latest "Release" could (likely) be for a different `release-*` branch or even `master` rather than the previous tag on the same branch as the new tag. This resulted in "Release" changelogs containing commits that dont exist in the tags history. By instead querying git itself we can fetch the previous tag in history and then generate an accurate changelog, eg: between `v1.7.4` and `v1.7.3` rather than potentially `v1.7.4` and `v1.10.0`. Run script through `shellcheck` and `shfmt`. (cherry picked from commit 8eac542)
✅ Backports have been created
|
mergify bot
added a commit
that referenced
this pull request
Apr 27, 2022
Previously the release info script would query the GitHub HTTP API and retrieve the latest "Release" (git tag) published. The latest "Release" could (likely) be for a different `release-*` branch or even `master` rather than the previous tag on the same branch as the new tag. This resulted in "Release" changelogs containing commits that dont exist in the tags history. By instead querying git itself we can fetch the previous tag in history and then generate an accurate changelog, eg: between `v1.7.4` and `v1.7.3` rather than potentially `v1.7.4` and `v1.10.0`. Run script through `shellcheck` and `shfmt`. (cherry picked from commit 8eac542) Co-authored-by: kskewes-sf <96093759+kskewes-sf@users.noreply.github.com>
mergify bot
added a commit
that referenced
this pull request
Apr 27, 2022
Previously the release info script would query the GitHub HTTP API and retrieve the latest "Release" (git tag) published. The latest "Release" could (likely) be for a different `release-*` branch or even `master` rather than the previous tag on the same branch as the new tag. This resulted in "Release" changelogs containing commits that dont exist in the tags history. By instead querying git itself we can fetch the previous tag in history and then generate an accurate changelog, eg: between `v1.7.4` and `v1.7.3` rather than potentially `v1.7.4` and `v1.10.0`. Run script through `shellcheck` and `shfmt`. (cherry picked from commit 8eac542) Co-authored-by: kskewes-sf <96093759+kskewes-sf@users.noreply.github.com>
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.
Previously the release info script would query the GitHub HTTP API and retrieve
the latest "Release" (git tag) published.
The latest "Release" could (likely) be for a different
release-*branch oreven
masterrather than the previous tag on the same branch as the newtag.
This resulted in "Release" changelogs containing commits that dont
exist in the tags history.
By instead querying git itself we can fetch the previous tag in history
and then generate an accurate changelog, eg: between
v1.7.4andv1.7.3rather than potentiallyv1.7.4andv1.10.0.Run script through
shellcheckandshfmt.