docs: clarify urlTemplate usage and repo_url derivation for registry target#766
Merged
docs: clarify urlTemplate usage and repo_url derivation for registry target#766
Conversation
Contributor
|
s1gr1d
approved these changes
Mar 3, 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
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.
Summary
urlTemplateoption description to explain the three Mustache template variables ({{version}},{{file}},{{revision}}), clarifies it's for apps/CDN-hosted assets and not typically needed for SDK packages on public registries, and replacesexample.complaceholder URLs with realisticdownloads.sentry-cdn.comexamples.urlTemplatefrom the SDK entry in the "Creating New Packages" example (SDKs don't need it).### repo_urland### Other metadatasubsections, explaining the two-tier resolution forrepo_url(auto-detection fromorigingit remote, with an explicitgithub:block in.craft.ymlas a fallback for edge cases) and noting it's always overwritten on every publish.