Skip to content

Conversation

@marcoesters
Copy link
Contributor

✂️ ✂️ ✂️ Snip, snip, release! ✂️ ✂️ ✂️

@github-project-automation github-project-automation bot moved this to 🆕 New in 🔎 Review Dec 1, 2025
@conda-bot conda-bot added the cla-signed [bot] added once the contributor has signed the CLA label Dec 1, 2025
@marcoesters marcoesters marked this pull request as ready for review December 1, 2025 22:07
@marcoesters marcoesters requested a review from a team as a code owner December 1, 2025 22:07
CHANGELOG.md Outdated
## 2025-12-01 3.13.2:
### Enhancements

* **Breaking change**: Replace custom Python script with `conda-standalone` calls.
Copy link
Contributor

@jaimergp jaimergp Dec 2, 2025

Choose a reason for hiding this comment

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

If this is a breaking change, should we at least bump to 3.14? If we should not, is it really a breaking change?

Copy link
Member

Choose a reason for hiding this comment

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

Agreed, breaking changes are usually leading to a bump in the MAJOR version though, not in a MINOR, or even PATCH version.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The reason why I added this to the news file is that under some circumstances (like using mamba version 2), Python is not added to the installer anymore unless requested in the constructor.yaml file. I think this is a breaking change.

Copy link
Contributor

Choose a reason for hiding this comment

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

I don't think it's breaking in the sense of requiring v4, imo. It's a change in how the installer is bootstrapped, but not in a way that would impact users. If the installer implicitly required python but it was not added as an explicit dependency, it's really unlikely none of the other packages mentioned would have brought it in.

In that sense I'm inclined to call this release 3.14, not 4.0.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

That sounds fair to me. Adding Python implicitly was never really a feature, more of a necessary nuisance. It was never really transparent to the user why Python was always added. I removed the breaking change language from the change log.

Copy link
Member

@jezdez jezdez left a comment

Choose a reason for hiding this comment

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

Needs version bump to 4.0

@github-project-automation github-project-automation bot moved this from 🆕 New to 🏗️ In Progress in 🔎 Review Dec 2, 2025
@jaimergp jaimergp changed the title Prepare 3.13.2 Prepare 4.0 Dec 2, 2025
@jaimergp jaimergp changed the title Prepare 4.0 Prepare 3.14 Dec 2, 2025
@github-project-automation github-project-automation bot moved this from 🏗️ In Progress to ✅ Approved in 🔎 Review Dec 3, 2025
@jaimergp jaimergp merged commit 96d5ea9 into conda:main Dec 3, 2025
3 checks passed
@github-project-automation github-project-automation bot moved this from ✅ Approved to 🏁 Done in 🔎 Review Dec 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

cla-signed [bot] added once the contributor has signed the CLA

Projects

Archived in project

Development

Successfully merging this pull request may close these issues.

4 participants