Skip to content

Release v1.1.1.0#26

Merged
Bodigrim merged 1 commit intomasterfrom
release-1.1.1.0
Mar 7, 2026
Merged

Release v1.1.1.0#26
Bodigrim merged 1 commit intomasterfrom
release-1.1.1.0

Conversation

@Bodigrim
Copy link
Contributor

No description provided.

@Bodigrim Bodigrim requested a review from andreasabel March 6, 2026 21:30
Copy link
Member

@andreasabel andreasabel left a comment

Choose a reason for hiding this comment

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

Thanks!

Consider releasing this as 1.2.0.0 instead, since there is a behavioral change. It is a bugfix, but you never know if folks rely on the current behavior.

Proceed at your own discretion.

@Bodigrim
Copy link
Contributor Author

Bodigrim commented Mar 7, 2026

Thanks. I see the point, but I feel that imposing on users a bounds bumping exercise (there are 42 package with old-time < 1.2) is more churn than the bug fix is worth, so I'd rather go ahead with 1.1.1.0.

@Bodigrim Bodigrim merged commit 1205f9b into master Mar 7, 2026
14 checks passed
@Bodigrim Bodigrim deleted the release-1.1.1.0 branch March 7, 2026 10:22
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.

2 participants