Repository navigation
Latest release (1.33.0) is an orphaned git tag #847
Description
Activity
Hi Luca Boccassi (@bluca) , thanks for bringing this to our attention. Now fixed by recreating a branch
release-1.33.0based on that tag1.33.0.I am not entirely sure why this happened, but if I am going to make a wild guess, I believe the root cause was this repo recently changed its merge policy into allowing only "squash-and-merge" (and "rebase-and-merge"). After squash-and-merge, the merged commit will not have the same hash as the real commit being shipped; and then, after deleting the release branch, the release tag becomes an orphan.
The unreliable solution seems to be either:
- Never delete release branch even after release
- Alter our org's github policy to allow
Create a merge commitagain, and then the release operator shall always choose that option to keep the release commit as-is. CC: Bogdan Gavril (@bgavrilMS)
Hi,
The latest release is not on any branch:
https://github.com/AzureAD/microsoft-authentication-library-for-python/tree/1.33.0
This means it's generally ignored by tools as it could be from a fork, so it cannot be used. Git fetch refuses to fetch it, for example.
Please fix this by pushing a release branch at the same tag or so.