Skip to content

fix: version bump with alpha (a1/a2...)#2042

Open
wolfv wants to merge 1 commit intoconda:mainfrom
wolfv:fix-bump-with-alpha
Open

fix: version bump with alpha (a1/a2...)#2042
wolfv wants to merge 1 commit intoconda:mainfrom
wolfv:fix-bump-with-alpha

Conversation

@wolfv
Copy link
Contributor

@wolfv wolfv commented Feb 10, 2026

Not sure how we should bump in practice. Do we expect 60a1 -> 60a2 or 61a1?

Fixes #2041

Comment on lines +237 to +240
for c in segment_components[last_num_idx + 1..].iter_mut() {
if let Some(id) = c.as_iden_mut() {
*id = "a".into();
}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should we not also only reset this for a, alpha, beta, b, rc`?

.next_back();
// Find the position of the last numeral so we only
// reset idens that appear after it.
let last_num_idx = segment_components
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we keep the name last_numeral_component? We also have segments and I find this more confusin.

/// appears before the bumped numeral.
#[rstest]
#[case("0.60b1", VersionBumpType::Last, "0.60b2")]
#[case("0.60b1", VersionBumpType::Segment(1), "0.60b2")]
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This one surprised me, but makes sense I guess!

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.

pixi upgrade botches >=0.60b1

2 participants