Skip to content
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

Can we publish to PyPI from different branches? #2040

Closed
tcompa opened this issue Nov 13, 2024 · 3 comments
Closed

Can we publish to PyPI from different branches? #2040

tcompa opened this issue Nov 13, 2024 · 3 comments
Labels
flexibility Support more workflow-execution use cases

Comments

@tcompa
Copy link
Collaborator

tcompa commented Nov 13, 2024

#2015 did work, but it partly breaks the history of versions and it would be suboptimal for a more complex bugfix.

Let's check whether the GHA that publishes to PyPI can be modified so that it can run on-demand on any given branch. If so, we'd have a way to avoid installing from GitHub.

@tcompa
Copy link
Collaborator Author

tcompa commented Jan 9, 2025

This will be most likely necessary, starting from #2168

@tcompa tcompa added the flexibility Support more workflow-execution use cases label Jan 9, 2025
@tcompa
Copy link
Collaborator Author

tcompa commented Jan 14, 2025

We could not do this with the original bumpver version (2022.x), but recent versions support the --ignore-vcs-tag flag.
With this flag on, we can do something like

  • From main: bumpver update --set-version 4.0.0 --tag-commit --commit
  • From dev: bumpver update --set-version 4.1.a0 --tag-commit --commit
  • From main: bumpver update --set-version 4.0.2 --tag-commit --commit --ignore-vcs-tag

@tcompa tcompa mentioned this issue Jan 14, 2025
3 tasks
@tcompa tcompa closed this as completed Jan 20, 2025
@tcompa
Copy link
Collaborator Author

tcompa commented Jan 21, 2025

Here is an example:

  1. We released a bunch of 2.11.0 prereleases from dev-2.11
  2. We released 2.10.6 from main
  3. We merged main into dev-2.11 (47593f8)

Image

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
flexibility Support more workflow-execution use cases
Projects
Development

No branches or pull requests

1 participant