-
-
Notifications
You must be signed in to change notification settings - Fork 402
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Potential breaking change in Repo.head()
for annotated tags
#1443
Comments
I don't think this is a regression, but rather a bug fix. The new behaviour is correct and consistent with C git; symrefs and unpeeled tags are meant to be preserved by a clone rather than be dereferenced. Even before 0.22.2 you were meant to get this behaviour, but that might not have happened in all situations. |
I agree that given that this change makes things consistent across tools, it is the right change. However, even if it is a bug fix this is likely a breaking change from a user's perspective (this is also debatable). I guess it comes down to if you follow semver, if not then downstream users just need to adjust the version expectations and tighten the version constraints. Edit: As the "api" iteself has not changed - it is technically still conformant to semver norms. So ... /shrug! |
Yeah, I agree that it is surprising - if I'd been aware of it before the release I would have added a note in NEWS. However, with certain client implementations (e.g. LocalGitClient) you would already get the behaviour you're seeing with the newer versions. So it's a bit of a grey area. Anyway, glad we've at least cleared up what the issue was here. Just to be clear, the intent is to follow semver. Closing this for now. |
@jelmer following up from python-poetry/poetry#9849 (comment) and python-poetry/poetry#9748 (comment) raising this issue to triage if this is in-fact a dulwich issue or a usage issue on our end.
A simplified reproducer that matches steps we use.
reproducer.py
container-one-line-reproducer.sh
From the output of the above shell command, you can see that the change happened between
0.22.1
and0.22.3
.The text was updated successfully, but these errors were encountered: