Skip to content

Publishing

Releases are published to GitHub Packages as @subscribed-aps/subscribed-cli. The package is private (access: restricted) and can only be installed by users with a GitHub token that has read:packages access to the subscribed-aps org.

Prerequisites

A GitHub personal access token with the write:packages scope, added to your ~/.npmrc:

@subscribed-aps:registry=https://npm.pkg.github.com
//npm.pkg.github.com/:_authToken=YOUR_GITHUB_TOKEN

Steps

  1. Bump the version in package.json following semver:
  2. patch (0.1.x) — bug fixes
  3. minor (0.x.0) — new commands or features, backwards compatible
  4. major (x.0.0) — breaking changes
npm version patch   # or minor / major
  1. Build to make sure the compiled output is up to date:
npm run build
  1. Publish:
npm publish
  1. Verify the new version appears at: https://github.com/orgs/subscribed-aps/packages?repo_name=tools-package-subscribed-cli

Notes

  • npm version automatically creates a git commit and tag. Push both: git push && git push --tags.
  • Never publish from a feature branch — always publish from main after the PR is merged.
  • The prepare script (npm run build) runs automatically before publish, so the dist/ output is always current.