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

Switch to version 10.3.0-rc.0 #547

Merged
merged 1 commit into from
Jan 24, 2025
Merged

Conversation

bruno-at-orange
Copy link
Contributor

Prepare release candidate 0 for 10.3.0

  • change only the version number

Copy link
Collaborator

@marcboulle marcboulle left a comment

Choose a reason for hiding this comment

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

LGTM

@bruno-at-orange bruno-at-orange merged commit 2f5b183 into dev-v10 Jan 24, 2025
23 checks passed
@bruno-at-orange bruno-at-orange deleted the prepare-release-10.3.0-rc.0 branch January 24, 2025 08:33
Copy link
Collaborator

@popescu-v popescu-v left a comment

Choose a reason for hiding this comment

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

conda-build moved from 24.11.2 to 25.1.1, which entails that Conda packages now have the .conda extension by default, instead of .tar.bz2.

Compare:

Hence, we need to either:

  1. pin conda-build to the latest 24.x.y which builds into the tar.bz2 format by default.
  2. add the --pkg-format=tar.bz2 option to conda build in
    conda build --output-folder ./build/conda ./packaging/conda
    (see warning in the last successful build using the .tar.bz2 format: https://github.com/KhiopsML/khiops/actions/runs/12690326153/job/35372162667#step:9:11).
  3. update
    rm -f -v ./build/conda/*/kni-transfer*.tar.bz2
    and
    --user "$ANACONDA_CHANNEL" ./build/conda/*/*.tar.bz2
    to change from *.tar.bz2 to *.conda.

I would go for either 2. or 3, with a preference for option 2., because it is the least intrusive IMHO, and keeping the .tar.bz2 format would facilitate local manual debugging by eased unarchiving of the packages.

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