aptlylabs-ui

Private registry (GitHub Packages)

@voxxup/aptlylabs-ui is published to GitHub Packages. The npm scope (@voxxup) must match the GitHub user or organization that owns this repository (github.com/voxxup/aptlylabs-ui), or GitHub will reject the publish.

One-time: authentication

CI: The publish workflow uses GITHUB_TOKEN automatically.

Your machine (publish or install private packages):

  1. Create a GitHub personal access token with read:packages (install) and write:packages + repo (publish from local, if needed).

  2. Either export before npm install / npm publish:

    export NODE_AUTH_TOKEN=ghp_your_token

    Or add to ~/.npmrc (do not commit):

    //npm.pkg.github.com/:_authToken=ghp_your_token

Install in another project

In that project’s root .npmrc:

@voxxup:registry=https://npm.pkg.github.com
//npm.pkg.github.com/:_authToken=${NODE_AUTH_TOKEN}

Then:

npm install @voxxup/aptlylabs-ui

Use a version range that matches your releases, e.g. "@voxxup/aptlylabs-ui": "^0.0.1".

Publish a new version

  1. Bump version in packages/ui/package.json (and changelog if you keep one).

  2. Option A — GitHub Actions: Create a GitHub Release whose tag matches the version (e.g. tag v0.1.0 for version 0.1.0). The workflow publishes @voxxup/aptlylabs-ui from packages/ui.

  3. Option B — Local: From repo root, with NODE_AUTH_TOKEN set:

    npm publish -w @voxxup/aptlylabs-ui

Using npmjs.com instead of GitHub

If your org uses npm private scope instead, change: