I did the releases 2.0.0, 2.0.1, and 2.0.2 using the following command:
gh workflow run release.yml --ref idea-251
Which checked out the idea-251 branch, and then built it (this is in build.yml). Thus, the platform binaries are correct.
In the next step, the release process invoked the Create Release step, which uses the softprops/action-gh-release@v2 action.
However, we didn't pass the branch/commit information to that step, so it tagged the tip-of-tree of the main branch.
That's why, if we navigate to the Releases page (e.g., https://github.com/android-graphics/sherlock-platform/releases/tag/v2.0.2), the commit and tag both point to the wrong place.
I did the releases 2.0.0, 2.0.1, and 2.0.2 using the following command:
Which checked out the
idea-251branch, and then built it (this is inbuild.yml). Thus, the platform binaries are correct.In the next step, the release process invoked the Create Release step, which uses the
softprops/action-gh-release@v2action.However, we didn't pass the branch/commit information to that step, so it tagged the tip-of-tree of the
mainbranch.That's why, if we navigate to the Releases page (e.g., https://github.com/android-graphics/sherlock-platform/releases/tag/v2.0.2), the commit and tag both point to the wrong place.