Skip to content

Conversation

@MridulS
Copy link
Member

@MridulS MridulS commented Feb 11, 2025

Let's see if this works. This should bump the last tag from 25.2.0 to 25.2.1.dev0

@MridulS MridulS enabled auto-merge (squash) February 11, 2025 17:02
@jl-wynen
Copy link
Member

Why do we need to bump the patch version?

@MridulS
Copy link
Member Author

MridulS commented Feb 12, 2025

The pip resolver will put 25.2.0 (from pypi) over 25.2.0.dev0 (from pypi.anaconda.org) as it merges both index and picks the latest. pip-compile will always end up with the stable release without the bump.

@jl-wynen
Copy link
Member

Do we actually need a version number based on the latest release (and can we) or can we just set it to 100.0.0.dev0?

If we use, e.g., 25.02.1.dev0, then when we release scipp, the nightly packages become, e.g., 25.03.1.dev0. But downstream, the dependencies where locked to 25.02.1.dev0 and so will continue to (try to) install the old wheel. So it seems to me that picking a fixed version number that can never appear naturally works better.

@MridulS
Copy link
Member Author

MridulS commented Feb 12, 2025

Do we actually need a version number based on the latest release (and can we) or can we just set it to 100.0.0.dev0?

100.0.0.dev0 should be fine too! I just wanted to make it look close to the last release.

@MridulS MridulS requested a review from jl-wynen February 12, 2025 10:24
@MridulS MridulS merged commit a577ef1 into main Feb 12, 2025
4 checks passed
@MridulS MridulS deleted the bump_patch_vers branch February 12, 2025 12:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants