Repository navigation
Fix fused ops conda CI - #5
Merged
Merged
Conversation
- Pin rattler-build to v0.77.0 in the fused ops workflow: the rattler-build-action default (v0.44.0) does not support --variant. - Skip the fireants publish workflow for fused-ops-v* releases, which it cannot version (prepare.py needs a v<version> tag). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
5 tasks done
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.
Follow-up to #4. Both publish runs for the
fused-ops-v1.2.0release failed; nothing was uploaded.push_conda_fused_ops.yml: pinrattler-build-version: v0.77.0. The action's default rattler-build (v0.44.0) does not support--variant, so every job failed withunexpected argument '--variant' found.push_conda.yml(fireants): skipfused-ops-v*releases. Thefused-ops-v1.2.0release triggered this workflow too. It failed inprepare.pybefore building anything, since the tag doesn't start withv.Once this PR's build passes and it's merged, publish 1.2.0 with a manual run of
Publish fused ops Conda packageon main withupload: true. The recipe already says 1.2.0, and re-running the release run would use the old workflow file from the tag.The
fused-ops-v1.2.0release had also been marked Latest;v1.4.0.post1has been set back to Latest.🤖 Generated with Claude Code