feat(registry): Auto-create package structure for new packages #689
Conversation
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
When introducing a new package to the registry, craft now automatically creates the required folder/file structure instead of failing with ENOENT. Changes: - Extended RegistryConfig with optional initial manifest fields (name, packageUrl, mainDocsUrl, apiDocsUrl) - Modified getPackageManifest to create directories and generate initial manifest when latest.json doesn't exist - Added InitialManifestData interface for type-safe initial manifest creation - repo_url is auto-derived from the GitHub repo configuration - Added comprehensive tests for the new package initialization flow Fixes #167
Contributor
Semver Impact of This PR🟡 Minor (new features) 📋 Changelog PreviewThis is how your changes will appear in the changelog. New Features ✨
Bug Fixes 🐛
🤖 This preview updates automatically when you update the PR. |
BYK
changed the title
Contributor
|
Config fields (name, packageUrl, mainDocsUrl, apiDocsUrl) now always override existing manifest values when specified. This allows repo maintainers to update package metadata by changing their .craft.yml configuration, rather than only applying these fields for new packages.
MathurAditya724
approved these changes
Dec 30, 2025
This was referenced Dec 31, 2025
7 tasks
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.
When introducing a new package to the registry, craft now automatically creates the required folder/file structure instead of failing with
ENOENT: no such file or directory.Changes
RegistryConfiginterface with optional initial manifest fields (name,packageUrl,mainDocsUrl,apiDocsUrl)getPackageManifestto create directories and generate initial manifest whenlatest.jsondoesn't existInitialManifestDatainterface for type-safe initial manifest creationrepo_urlis auto-derived from the GitHub repo configurationExample Usage
Fixes #167