-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
[WIP; RFC; Pending 1268, Stacked on 1270] Enhancement: git tag sem-ver resolution #1176
Conversation
1b5a463
to
5658786
Compare
882a5c1
to
2b4c095
Compare
99e8cf3
to
adaaa74
Compare
adaaa74
to
6542b32
Compare
tests are failing because test fixtures for a git repo do not support a |
4112dc1
to
25f3d1b
Compare
Splitting this PR out into smaller PRs |
25f3d1b
to
2d11d3a
Compare
d6b310d
to
4cad13f
Compare
4cad13f
to
284a5f1
Compare
284a5f1
to
22dff9c
Compare
8f389da
to
6d87e44
Compare
- add git tags to test fixtures
- boolean check for a sem-ver string - filter and sort a sequence of sem-ver strings - these utils are used to filter and sort a list of git tags
- add utility methods for git tags - use sem_ver_sorted for Git.sem_ver_tags - extract private method for Git._folder_args
- use sem-ver constraints to provide a git package - add tests for git provider using tags - test a tag dependency - test a missing tag dependency - test a sem-ver tag dependency - update README for git sem-ver tags
6d87e44
to
92e2603
Compare
I don't think that's something I am willing to add to Poetry. This is a very specific workflow (even though I understand why you might want it) that does not make sense to add to the Poetry code base. |
Interesting opinion, thanks for the transparency on that, it could save a lot of work. The options then are:
If this is a general feature veto, the options become:
If this is an implementation veto, what are the options that could fly? |
@darrenleeweber The truth is, that's a workflow that I was not aware of until now and npm seems to be the only one to support this. But yes, going the plugin route might be the preferred way to implement this once the plugin system is done (see #1237) |
This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Issue(s)
Split out PRs
Not necessarily stacked, but isolated changes in smaller PRs:
Check List