Uh oh!
There was an error while loading. Please reload this page.
Doc 19: the registry does not know what language a package is - #17
Merged
Conversation
Driving the live registry in a browser surfaces what artifact-level and file:// checks cannot: one publish of a four-language repo leaves five navigable packages and nothing in the API or UI says which language any of them is. package.language/ecosystem stop at the artifact. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Uh oh!
There was an error while loading. Please reload this page.
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 freeto 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.
Records a gap that only browser-driving the live registry could surface — every earlier check ran against artifacts on disk or a
file://registry.One publish of a four-language repository leaves five navigable packages, and nothing in the API or the UI says which language any of them is.
package.language/package.ecosystemare declared in the manifest and enforced by the install guard, but they stop at the artifact — absent fromPackageMetadata,PackageSummary, and the package page. Two consequences:acme-clients-javais indistinguishable from any unrelated package. The-javasuffix is a naming convention the registry does not understand, and a target that overrodenamehas no suffix at all.Paired with zed-pkg/zed-e2e#5, which adds the browser coverage this came out of. That suite asserts what the UI does expose — separate pages per language, distinct
sha256per slice, lockstep versions, and that the polyglot source name deliberately does not resolve. Language identity is the one thing it cannot assert, because there is nothing to assert against.🤖 Generated with Claude Code