Npm dist-tag precedence & repository settings updates#421
Open
grainne-cloudsmith wants to merge 11 commits into
Open
Npm dist-tag precedence & repository settings updates#421grainne-cloudsmith wants to merge 11 commits into
grainne-cloudsmith wants to merge 11 commits into
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
grainne-cloudsmith
changed the title
Contributor
There was a problem hiding this comment.
Pull request overview
Updates Cloudsmith documentation to reflect current repository settings behavior and clarifies npm dist-tag handling (including upstream precedence) for users configuring npm repositories.
Changes:
- Reworks the Repository Settings doc with updated screenshots, renamed sections, and expanded setting descriptions (including “NPM upstream tags take precedence”).
- Updates the npm Registry doc for improved accuracy/wording around distribution tags and adds a new “Upstream Tag Precedence” section.
Reviewed changes
Copilot reviewed 2 out of 14 changed files in this pull request and generated 6 comments.
| File | Description |
|---|---|
| src/content/repositories/repository-settings.mdx | Refreshes repository settings documentation, screenshots, and adds/clarifies settings including npm upstream dist-tag precedence. |
| src/content/formats/npm-registry.mdx | Improves wording/accuracy and adds guidance on upstream dist-tag precedence behavior for npm. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| **Use Debian repository labels** | ||
|
|
||
| If checked, a `Label` field will be present in Debian-based repositories. It will contain a string that identifies the entitlement token used to authenticate the repository, in the form of `source=t-`, or `source=none` if no token was used. You can use this to help with pinning. |
Contributor
Author
There was a problem hiding this comment.
For reviewer input - I'd updated this to align with the latest UI copy. Worth reverting?
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.
Updates to the npm format doc:
Updates to the Repository Settings doc:
Note: 'NPM' still present in a few places where we're directly referencing the UI copy with the same capitalisation.