Repository navigation
DOC: add the conda-forge steps to the release checklist - #111
Merged
Merged
Conversation
Member
Author
|
I'm not sure this extra information is needed. Can be closed or merged. Up to reviewer entirely, |
rok
marked this pull request as ready for review
November 6, 2026 19:10
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
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.
Adds the conda-forge steps to the release checklist: what a feedstock maintainer does with the bot's version update, how to test the install, and what to do if something goes wrong there. Part of #108.
This is a draft because the feedstock doesn't exist yet. The text describes it as if it does, and the
benchx-feedstocklink won't work until conda-forge/staged-recipes#35536 merges and the feedstock is created. Mark this ready after that, and check that the steps match how the first bot update goes.The steps follow conda-forge's guide to updating packages. The strict docs build passes, but the steps themselves haven't been tried, because they need a feedstock.