-
Notifications
You must be signed in to change notification settings - Fork 67
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
version take 2 #1635
version take 2 #1635
Conversation
There are dueling changes between this and #1634. This PR covers some of the changes suggested there, but not all. They should be reconciled after this is merged. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The metadata rewrite on line 106 is horrifying, but it didn't come in on this PR and will be treated in #1634
Getting an error in testing:
I don't know that this is attributable to this PR yet. added: False alarm. That error came from a docker mismatch on my build. These are a mite too common as we make infrastructure changes prior to release. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I've manually tested the version system in:
- nominal configuration
- missing .git repo
- shallow .git repo.
I will merge when CI completes.
CI tests are weird. Thoughts? |
It is symptomatic of shallow clones breaking For example, pypa/setuptools-scm#414 but we've also seen it before. |
I merged develop in. Hopefully checks will pass now. |
No description provided.