Repository navigation
fix: resolve artifactory/prefix/quetz publish targets to https channels - #2907
Merged
Merged
Conversation
`rattler-build publish --to artifactory://...` prepends the target channel
to the solver channels, but only `cloudsmith://` was rewritten to a URL the
repodata gateway can read, so solving failed with
"'artifactory' is not a supported scheme". The same applied to `prefix://`
and `quetz://`.
Also replace `Url::set_scheme("https")` (which always fails when switching
from a non-special scheme) with a string-based rewrite, matching pixi, and
keep Artifactory context paths (e.g. /artifactory/) in the upload base URL.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01K2qg4BnzsQk3K8bu4dBcMz
6 tasks done
This was referenced Oct 28, 2026
Merged
This was referenced Oct 31, 2026
This was referenced Nov 11, 2026
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.
Problem
A user reported that
rattler-build publish recipe.yaml --to artifactory://files.example.com/conda-internalfails before the build starts:publishadds the--totarget as the first channel for solving.resolve_channel_for_repodatarewrote onlycloudsmith://, so the other upload-only schemes went to rattler's repodata gateway unchanged, and the gateway rightly rejects them. This also affectedprefix://andquetz://.s3://,file://andhttp(s)://can already be read by the gateway.A second bug was waiting behind the first: the Quetz and Artifactory uploads called
Url::set_scheme("https"). That call always fails when switching from a non-special scheme, so these uploads would have failed even after the solve worked.Changes
resolve_channel_for_repodatanow rewrites:artifactory://host/path/repo→https://host/path/repoprefix://host/channel→https://host/channelquetz://host/channel→https://host/get/channelrewrite_scheme_to_https, a string-based scheme rewrite matching the helper pixi already has. Quetz, Artifactory and Prefix uploads now use it./artifactory/) in the base URL. Before, the whole path was stripped, soartifactory://host/artifactory/repouploaded tohttps://host/repo/....Notes
publishdoesn't hit the solve error because it solves against the workspace channels. The same Artifactory context-path fix for pixi is in fix(publish): keep Artifactory context path when uploading pixi#7388. The helper could later move intorattler_uploadso both tools share it.User prompt
🤖 Generated with Claude Code
https://claude.ai/code/session_01K2qg4BnzsQk3K8bu4dBcMz