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
No support for Python packages versioning (PEP 440) #85
Comments
@gdubicki Thanks for your feedback. I think we could add a new |
I have the same request! Would really appreciate having pep440 support! For now I work with sermver + raw for prereleases, but proper support would be awesome! |
@gdubicki @tillsteinbach You can test the |
Just tested it with a dev release (this was not working with semver) and a regular release and it works like a charm! Awesome thanks! |
@tillsteinbach Great to hear! Is your repository public so I can take a look at your workflow? |
@crazy-max sure: https://github.com/tillsteinbach/WeConnect-mqtt/blob/9bb8d018475d1628289656ac02fb94ef8d3e7940/.github/workflows/python-docker-publish.yml#L72 |
@tillsteinbach This run has been triggered by a push tag event which is
Also as you can see |
Ahrg! Yes, I was unconcentrated :) really nice work! |
Hey @crazy-max , thanks for your work on this! I'll check it out within a few days. |
Unfortunately I cannot make it work, @crazy-max . Probably I am just using GitHub Actions terribly wrong but I am getting:
I tried referring specifically to the latest as of now v3.4.1 in gitlabform/gitlabform@6418192 but this failed with:
Any suggestions? |
This is my fork, use |
🤦♂️ |
Hi!
Thanks for the cool action! It works like a charm ...as long as you are using semver.
Unfortunately in my case I wanted to use it for a Python package, which is versioned according to a pythonic standard - PEP440 - which is not semver-compatible.
I couldn't just use
type=match
as in the case of the pre-release versions we should not add any other tags than the one with just the version itself.Initially I wanted to create a PR to add support for PEP 440 to this project, but I don't really know Typescript, so I ended up with writing it in, well, Python.
I would like to share this solution here for other people with such problem to find it and use this as a workaround and/or for someone to consider rewriting this in Typescript and making that PR. :)
Anyway: happy hacking!
(source: voxpupuli/puppetboard@924bb55 + voxpupuli/puppetboard@94052a0)
The text was updated successfully, but these errors were encountered: