Update library terminology from registry to repository#3246
Open
Update library terminology from registry to repository#3246
Conversation
Signed-off-by: s-stumbo <sally.stumbo@chainguard.dev>
✅ Deploy Preview for ornate-narwhal-088216 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Member
|
Just a side note .. there are different names for the essentially same or similar thing
So whatever you choose.. it will be kinda wrong in some other context .. but there is really not much you can do about it.. |
mosabua
reviewed
Apr 14, 2026
|
|
||
| Before configuring your repo manager, consider how you want to handle packages that aren't | ||
| yet available in the Chainguard registry. If you configure a fallback to Maven Central, packages sourced from that registry are not covered by Chainguard's | ||
| yet available in the Chainguard libraries repository. If you configure a fallback to Maven Central, packages sourced from that registry are not covered by Chainguard's |
Member
There was a problem hiding this comment.
Suggested change
| yet available in the Chainguard libraries repository. If you configure a fallback to Maven Central, packages sourced from that registry are not covered by Chainguard's | |
| yet available in the Chainguard Libraries repository. If you configure a fallback to Maven Central, packages sourced from that registry are not covered by Chainguard's |
Member
There was a problem hiding this comment.
and others.. if you want to use the "Chainguard Libraries" product name
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
3 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.
[ ] Check if this is a typo or other quick fix and ignore the rest :)
Type of change
Update references to "registry" to call it the "Chainguard libraries repository"
What should this PR do?
Why are we making this change?
Standardize terminology
What are the acceptance criteria?
The wording updates should appear as expected in the deploy preview
How should this PR be tested?
Review the deploy preview