The GH release creates the tag before triggering the action, so the tag is pointed out to the code before the bump-version.sh changes which is OK for Cocoapods since the code is uploaded after the changes, but not ok for SPM since SPM depends on the tag.
This commit updates the tag after the bump-version.sh is executed.
The side effect was that someone using 3.0.0-alpha.3 would be reported as $lib_version=3.0.0-alpha.2.
#skip-changelog
:green_heart: How did you test it?
Locally.
:pencil: Checklist
[X] I reviewed the submitted code.
[ ] I added tests to verify the changes.
[ ] I updated the docs if needed.
[X] No breaking change or entry added to the changelog.
:bulb: Motivation and Context
The GH release creates the tag before triggering the action, so the tag is pointed out to the code before the
bump-version.shchanges which is OK for Cocoapods since the code is uploaded after the changes, but not ok for SPM since SPM depends on the tag. This commit updates the tag after thebump-version.shis executed.The side effect was that someone using
3.0.0-alpha.3would be reported as$lib_version=3.0.0-alpha.2.#skip-changelog
:green_heart: How did you test it?
Locally.
:pencil: Checklist