Repository navigation
chore: publish as @flamai/finesse on npm (Apache-2.0) - #2
Merged
Merged
Conversation
npm only allows publishing under an org's own scope, and the org is flamai, so the package is renamed from @flam/finesse. The private flag is removed and publishConfig sets public access. A tag-triggered release workflow publishes with npm Trusted Publishing (GitHub OIDC), so no npm token is stored; it checks the tag against package.json and runs typecheck, lint, tests and build first. README installs from npm.
UNLICENSED means no one may use the published package. Apache-2.0 is permissive for commercial use and adds an explicit patent grant and a trademark clause.
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
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.
Prepares the SDK for its first public npm release as
@flamai/finesse0.1.1. Nothing is published by merging this; a release happens only when av*tag is pushed.Changes
@flam/finesse→@flamai/finesse. npm only allows publishing under an org's own scope, and the org isflamai."private": trueremoved;publishConfig.access: public;repositoryandhomepageadded.LICENSE,licensefield inpackage.json). It wasUNLICENSED, which on npm means no one may use the package..github/workflows/release.yml): on av*tag, it checks the tag againstpackage.json, runs typecheck, lint, tests and build, then runsnpm publishthrough npm Trusted Publishing (GitHub OIDC). No npm token is stored.Verified
pnpm typecheck,pnpm lint,pnpm test(156 passed, 9 live tests skipped) andpnpm build.npm pack --dry-run:@flamai/finesse@0.1.1, 10 files (dist, README, CHANGELOG, LICENSE, package.json), 139 kB. No keys or internal hosts.Before the first release
npm publish --access publicmanually (with 2FA), as a member of theflamaiorg.@flamai/finesse: GitHub, repositoryhomingos/finesse-node, workflowrelease.yml.version, update the CHANGELOG, push tagvX.Y.Z.Provenance attestations need a public repository. This repo is private, so releases publish without the provenance badge until it is made public.