fix: update READMEs to use actual package.json names#47
Merged
pyramation merged 1 commit intomainfrom Mar 15, 2026
Merged
Conversation
- metaschema-modules: replace @pgpm/db-meta-modules with @pgpm/metaschema-modules - metaschema-schema: replace @pgpm/db-meta-schema with @pgpm/metaschema-schema - inflection: update cross-reference from @pgpm/db-meta-schema to @pgpm/metaschema-schema - Fix npm badge URLs to point to correct package directory paths
🤖 Devin AI EngineerI'll be helping with this pull request! Here's what you should know: ✅ I will automatically:
Note: I can only respond to comments from users who have write access to this repository. ⚙️ Control Options:
|
![devin-ai-integration[bot]](https://avatars.githubusercontent.com/in/811515?s=60&v=4){kind=small}
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
1 participant
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
The
metaschema-modulesandmetaschema-schemapackages had READMEs still referencing their old names (@pgpm/db-meta-modulesand@pgpm/db-meta-schema). This meant install instructions, badge URLs, overview text, and dependency references were all pointing users to packages that don't exist under those names.Affected files (3):
packages/metaschema-modules/README.md— all@pgpm/db-meta-modules→@pgpm/metaschema-modules; dependency ref@pgpm/db-meta-schema→@pgpm/metaschema-schema; badge URL path fixedpackages/metaschema-schema/README.md— all@pgpm/db-meta-schema→@pgpm/metaschema-schema; badge URL path fixedpackages/inflection/README.md— cross-reference section header@pgpm/db-meta-schema→@pgpm/metaschema-schemaAll other 18 packages were audited and their READMEs already match their
package.jsonnames. Theservicespackage has no README.Review & Testing Checklist for Human
@pgpm/db-meta-modulesor@pgpm/db-meta-schema— this PR only auditedREADME.mdfiles insidepackages/@pgpm/metaschema-modulesand@pgpm/metaschema-schemaso the badge/install links will resolve correctlyNotes
filename=params were also stale (pointing topackages%2Fdb-meta-modules%2F...andpackages%2Fdb-meta-schema%2F...which don't exist as directory names) — these are now corrected to match the actual directory namesLink to Devin session: https://app.devin.ai/sessions/0a557981b0ac4798ac223d3f93896b75
Requested by: @pyramation