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

Rebuild for ucx 1.18 #110

Open
wants to merge 2 commits into
base: 3.x
Choose a base branch
from

Conversation

regro-cf-autotick-bot
Copy link
Contributor

This PR has been triggered in an effort to update ucx118.

Notes and instructions for merging this PR:

  1. Please merge the PR only after the tests have passed.
  2. Feel free to push to the bot's branch to update this PR if needed.

Please note that if you close this PR we presume that the feedstock has been rebuilt, so if you are going to perform the rebuild yourself don't close this PR until the your rebuild has been merged.


If this PR was opened in error or needs to be updated please add the bot-rerun label to this PR. The bot will close this PR and schedule another one. If you do not have permissions to add this label, you can use the phrase @conda-forge-admin, please rerun bot in a PR comment to have the conda-forge-admin add it for you.

This PR was created by the regro-cf-autotick-bot. The regro-cf-autotick-bot is a service to automatically track the dependency graph, migrate packages, and propose package version updates for conda-forge. Feel free to drop us a line if there are any issues! This PR was generated by https://github.com/regro/cf-scripts/actions/runs/12897362290 - please use this URL for debugging.

@conda-forge-admin
Copy link
Contributor

Hi! This is the friendly automated conda-forge-linting service.

I wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found some lint.

Here's what I've got...

For recipe/meta.yaml:

For recipe/meta.yaml:

  • ℹ️ The recipe is not parsable by parser conda-recipe-manager. The recipe can only be automatically migrated to the new v1 format if it is parseable by conda-recipe-manager.

This message was generated by GitHub Actions workflow run https://github.com/conda-forge/conda-forge-webservices/actions/runs/12897875183. Examine the logs at this URL for more detail.

@dalcinl
Copy link
Contributor

dalcinl commented Jan 22, 2025

@minrk I got two PRs with the same title, #109 and next this one #110. I merged the first (everything looked good) without noticing the second. I'm not sure what's the purpose of this one.

@jakirkham
Copy link
Member

The previous one was for main ( #109 ) and this one is for 3.x

Looks like migrations are enabled for both

bot:
abi_migration_branches:
- 3.x

Note: main is always included in the list

@dalcinl
Copy link
Contributor

dalcinl commented Jan 22, 2025

and this one is for 3.x

Oh, I totally forgot 🤦‍♂️. Then this PR may require some added love.

@jakirkham
Copy link
Member

No worries. It's good to check. Sometime the bot does accidentally send multiple PRs to the same branch, which is good to catch and fix

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.

4 participants