npm / tegami
tegami
What changed in tegami 1, from its official release notes, upgrade guides and advisories. Sources checked 2026-10-19.
1 new APIs and options4 behavior and defaults4 fixes and other
See which of these apply to your code, ranked, in your agent:
npx @unstale/cli inittegami 19 changes
New APIs and options 1
Configure extra npm package names to publish from the package directory; aliases share the package version, changelog, git tag, and dist-tag, and existing registry names are skipped.
Behavior and default changes 4
Configure trusted publishing for package aliases as well as the original package name.
Registry lookups read .npmrc credentials, sending _authToken as a bearer token and _auth as a basic token; environment variables are expanded and host credentials cover paths below that host.
Registry selection follows npm precedence: publishConfig.registry, then @scope:registry, then registry, then https://registry.npmjs.org.
The draft condition matches any move from a prerelease version to a non-prerelease version, including major and minor bumps.
Fixes and other changes 4
Published-version checks use GET /{name} instead of GET /{name}/{version}, allowing checks to work with registries such as GitHub Packages that reject the version route.
Lists packages published to another registry as skipped instead of trying to configure them, since npm trust only exists on registry.npmjs.org.
Scoped package names are percent-encoded in registry URLs so publish status lookups succeed with registries that reject unescaped path segments.
Disposing an already-applied Draft no longer throws because Symbol.asyncDispose calls apply() only when the draft can still be applied.