fix(registry): point angular and strapi at their real npm packages - #164
Merged
Merged
Conversation
npm/angular asked npm about `angular`, which is AngularJS (latest 1.8.3), against min_version 17.0.0, and npm/strapi asked about `strapi` (latest 3.6.11) against min_version 5.0.0. Neither has ever discovered a version, so both definitions silently published nothing. Reported by @JayOfTheKeyboard on #126. They now live at npm/@angular/core and npm/@strapi/strapi. Angular starts at 20.3.0 because its older minors are tagged without the "v" prefix (e.g. 18.2.14); every minor from 20.3 on uses "v{version}". Built locally with test-registry: @angular/core 22.2.0 1956 sections / 692,359 tokens @angular/core 20.3.32 1493 sections / 524,116 tokens @strapi/strapi 5.55.1 456 sections / 122,366 tokens Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UX3uvgjRrv9uYuZxKjNF4o
|
strapi/strapi's docs/ folder is contributor documentation (code of conduct, contributing and coding guides); the user docs live in strapi/documentation under docusaurus/docs/cms. That repo's tags are site versions rather than Strapi releases, so the definition is unversioned, like npm/cypress and npm/express. Built locally: 1392 sections / 568,358 tokens. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01UX3uvgjRrv9uYuZxKjNF4o
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.
Requested by Moshe · project thread
Before: the Angular and Strapi definitions have never published any docs.
npm/angularasks npm aboutangular, which is AngularJS (latest 1.8.3), againstmin_version: 17.0.0.npm/strapiasks aboutstrapi(latest 3.6.11) againstmin_version: 5.0.0. Discovery finds nothing and exits 0.After: both definitions point at the packages people actually install,
@angular/coreand@strapi/strapi, and publish real user docs.vprefix (for example18.2.14and20.2.4), and every minor from 20.3 on usesv{version}. That covers Angular's currently supported releases, 20.3, 21.x and 22.x.strapi/documentation(docusaurus/docs/cms). Thedocs/folder instrapi/strapiis contributor documentation. The documentation repo's tags are site versions rather than Strapi releases, so this definition is unversioned, likenpm/cypressandnpm/express.How: I moved the files to
registry/npm/@angular/core.yamlandregistry/npm/@strapi/strapi.yamland updatednameto match. Built locally withtest-registry:There's no changeset because this only touches registry YAML and
@neuledge/registryis private. Reported by @JayOfTheKeyboard on #126.🤖 Generated with Claude Code
https://claude.ai/code/session_01UX3uvgjRrv9uYuZxKjNF4o