feat: publish to npm as ai-forms - #6
Merged
Merged
Conversation
The package was installable only via a git URL under a private `@fleet` scope, which made it unusable by anyone outside this fleet and invisible to search. `ai-forms` was free on the registry, so take it. - rename `@fleet/ai-forms` -> `ai-forms` (package, lockfile, README, docs) - add the MIT LICENSE file the package.json already claimed - add a tag-driven publish workflow with provenance, gated on `verify` and on the tag matching package.json (a mismatched tag fails loudly instead of shipping the wrong version) - make the README readable by someone who has never seen this fleet: provider-agnostic `complete` example instead of an internal Groq helper, real install line, badges Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
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.
Why
The package was installable only via a git URL under a private
@fleetscope — unusable by anyone outside the fleet, invisible to registry search. The nameai-formsis free on npm.What
@fleet/ai-forms→ai-forms(package.json, lockfile, README)LICENSEfile thatpackage.jsonalready claimed.github/workflows/publish.yml: tag-driven, npm provenance, gated onnpm run verifyand on the tag matchingpackage.jsonversioncompleteexample (was an internal Groq helper), real install line, badgesVerification
npm run verify— build clean, 14/14 tests passnpm pack --dry-run— 16.2 kB, 21 files,dist/only, nameai-formsOne thing this PR cannot do
Publishing needs an
NPM_TOKENrepo secret. Until it exists the workflow will fail at the final step. Everything before it is green.🤖 Generated with Claude Code