Document manually triggering the conda-forge bots#12083
Merged
jrbourbeau merged 1 commit intodask:mainfrom Sep 24, 2025
Merged
Conversation
Contributor
Unit Test ResultsSee test report for an extended history of previous test failures. This is useful for diagnosing flaky tests. 9 files ±0 9 suites ±0 3h 8m 37s ⏱️ - 4m 4s Results for commit 031c89a. ± Comparison against base commit b804291. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
In the last release it took around 36 hours for the conda-forge bots to pick up the new versions of
daskanddistributedfrom PyPI. @jakirkham advised that I could've opened issues with the title@conda-forge-admin, please update versionon each of the feedstocks to trigger this manually.This feels easier than the manual process for opening the PRs.
This PR updates the docs with instructions on doing this.