@_linked/cli 1.2.11 → 1.3.2

package/.changeset/README.md

@@ -0,0 +1,20 @@
+# Changesets
+
+This package uses [changesets](https://github.com/changesets/changesets) for version management and publishing.
+
+## Adding a changeset
+
+When making a change that should trigger a new release, run:
+
+```bash
+npx changeset
+```
+
+This generates a markdown file in `.changeset/` describing the change. Commit it with your PR.
+
+On merge to `main`, the publish workflow either:
+
+1. Creates (or updates) a **Release PR** that bumps the version + updates `CHANGELOG.md`, or
+2. If the Release PR is already merged, publishes the new version to npm.
+
+Changes that don't need a release (docs, CI config, tooling) can skip the changeset — the check is a warning, not a block.

package/.changeset/config.json

@@ -0,0 +1,14 @@
+{
+  "$schema": "https://unpkg.com/@changesets/config@3.1.1/schema.json",
+  "changelog": [
+    "@changesets/changelog-github",
+    { "repo": "linked-cm/cli" }
+  ],
+  "commit": false,
+  "fixed": [],
+  "linked": [],
+  "access": "public",
+  "baseBranch": "main",
+  "updateInternalDependencies": "patch",
+  "ignore": []
+}

package/.github/workflows/changeset-check.yml

@@ -0,0 +1,44 @@
+name: Changeset Check
+
+on:
+  pull_request:
+    branches:
+      - main
+
+jobs:
+  changeset-check:
+    name: Check for changeset
+    # Skip the check on the automated Release PR.
+    if: ${{ github.head_ref != 'changeset-release/main' }}
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Check for changeset files
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const { data: files } = await github.rest.pulls.listFiles({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              pull_number: context.issue.number,
+            });
+
+            const hasChangeset = files.some(f =>
+              f.filename.startsWith('.changeset/') &&
+              f.filename.endsWith('.md') &&
+              f.filename !== '.changeset/README.md'
+            );
+
+            if (!hasChangeset) {
+              await github.rest.issues.createComment({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                issue_number: context.issue.number,
+                body: "No changeset found. If this PR should trigger a release, run `npx changeset` and commit the generated file.\n\nIf this change doesn't need a release (docs, CI config, etc.), you can ignore this message."
+              });
+              core.warning('No changeset file found in this PR.');
+            }

package/.github/workflows/ci.yml

@@ -0,0 +1,43 @@
+name: CI
+
+on:
+  pull_request:
+    branches:
+      - main
+
+jobs:
+  build-and-test:
+    name: Build & Test
+    runs-on: ubuntu-latest
+    steps:
+      - name: Detect Release PR
+        id: rpr
+        run: |
+          if [[ "${{ github.event.pull_request.head.ref }}" == "changeset-release/main" ]]; then
+            echo "is_release_pr=true" >> $GITHUB_OUTPUT
+            echo "Release PR from changesets/action detected — skipping build/test (auto-generated version+CHANGELOG only)."
+          else
+            echo "is_release_pr=false" >> $GITHUB_OUTPUT
+          fi
+
+      - name: Checkout
+        if: steps.rpr.outputs.is_release_pr == 'false'
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        if: steps.rpr.outputs.is_release_pr == 'false'
+        uses: actions/setup-node@v4
+        with:
+          node-version: 22.16.0
+
+      - name: Install dependencies
+        if: steps.rpr.outputs.is_release_pr == 'false'
+        run: npm ci --legacy-peer-deps
+
+      - name: Build
+        if: steps.rpr.outputs.is_release_pr == 'false'
+        run: npm run build
+
+      - name: Test
+        if: steps.rpr.outputs.is_release_pr == 'false'
+        run: npm test --if-present

package/.github/workflows/publish.yml

@@ -0,0 +1,42 @@
+name: Publish
+
+on:
+  push:
+    branches:
+      - main
+
+concurrency: ${{ github.workflow }}-${{ github.ref }}
+
+jobs:
+  release:
+    name: Publish Release
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      pull-requests: write
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 22.16.0
+          registry-url: 'https://registry.npmjs.org'
+
+      - name: Install dependencies
+        run: npm ci --legacy-peer-deps
+
+      - name: Build
+        run: npm run build
+
+      - name: Create release Pull Request or Publish
+        uses: changesets/action@v1
+        with:
+          publish: npx changeset publish
+          title: 'chore: release'
+          commit: 'chore: release'
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          NODE_AUTH_TOKEN: ${{ secrets.NPM_AUTH_TOKEN }}
+          NPM_TOKEN: ${{ secrets.NPM_AUTH_TOKEN }}

package/CHANGELOG.md

@@ -1,5 +1,28 @@
 # Changelog
 
+## 1.3.2
+
+### Patch Changes
+
+- [#19](https://github.com/linked-cm/cli/pull/19) [`2111d11`](https://github.com/linked-cm/cli/commit/2111d113039c95304458e72c29dc2a58ca97ba16) Thanks [@flyon](https://github.com/flyon)! - Remove `prepack: yarn build && pinst --disable` and `postpack: pinst --enable` scripts. These were conflicting with the CI publish flow (ENEEDAUTH on the actual `npm publish` call). Build now happens only in the dedicated CI "Build" step. Also remove `postinstall: husky install` (not needed for published installs).
+
+## 1.3.0
+
+### Minor Changes
+
+- [#17](https://github.com/linked-cm/cli/pull/17) [`3c81281`](https://github.com/linked-cm/cli/commit/3c81281ce9ef4b16c08f341923f6920b9b9c7f6b) Thanks [@flyon](https://github.com/flyon)! - Phase 0.3 accumulated changes:
+  - **New `linked setup-publish` command**: scaffolds a changesets-based publish workflow in any package repo. Supports single-branch (default) and `--dual-branch` (main + dev with `@next` prereleases). Patches package.json (publishConfig + changesets devDeps), generates package-lock.json in an isolated tmpdir, writes `.github/workflows/{ci,publish,changeset-check}.yml`, and optionally configures GitHub branch protection via `--configure-github` (uses `gh` CLI).
+  - **`linked build-workspace` now invokes each package's own `yarn build` script** instead of the internal buildPackage pipeline. Lets @\_linked/core use pure tsc, pure-CSS packages use no-ops, and lincd-style packages use `yarn linked build`.
+  - **`linked yarn` (safeYarn) gains `LINKED_YARN_DRY_RUN` env** for testing arg forwarding without executing.
+  - **Import checker is warn-only** (was fatal): emits yellow warnings listing missing `.js` extensions but doesn't abort the build.
+  - **compilePackageESM/CJS** skip gracefully when tsconfig-{esm,cjs}.json is absent (pure-CSS packages).
+  - **Dual-package step** uses `npx tsconfig-to-dual-package` so the binary resolves from nearest node_modules.
+  - **runOnPackagesGroupedByDependencies**: tolerate packages without `dependencies` field.
+  - **Package template modernized**: uses `yarn linked build` pattern (matches foundational packages), Gruntfile removed.
+  - **App template**: adds `mrgit-template.json`, `yarn setup` script, `linkedApp: true` flag, `mrgit` devDep.
+  - **`linkedPackage: true` / `linkedApp: true`** flags added to cli-methods readers (alongside legacy `lincd` / `lincdApp` for transition period).
+  - **Bug fix**: lingering `lincd-server/*` imports in LincdServer.tsx migrated to `@_linked/server/*`.
+
 All notable changes to `@_linked/cli` (formerly `lincd-cli`) are documented here.
 
 This project follows [Keep a Changelog](https://keepachangelog.com/) and [Semantic Versioning](https://semver.org/).
@@ -7,6 +30,7 @@ This project follows [Keep a Changelog](https://keepachangelog.com/) and [Semant
 ## [1.2.11] - 2026-04-22
 
 ### Changed
+
 - **Renamed package**: `lincd-cli` → `@_linked/cli`. Repo moved from `semantu/lincd-cli` → `linked-cm/cli`.
 - **Primary binary** is now `linked` (with `lnk` as a short alias).
 - **Flag in package.json** is now `linkedPackage: true` (packages) / `linkedApp: true` (apps). The legacy flags `lincd: true` / `lincdApp: true` are still read for a transition period.
@@ -14,20 +38,24 @@ This project follows [Keep a Changelog](https://keepachangelog.com/) and [Semant
 - **App template** (`defaults/app-with-backend/`) now includes `mrgit-template.json`, a `yarn setup` script, and `mrgit` as a devDep. Run `yarn setup` after `linked create-app` to optionally clone sibling `@_linked/*` repos for local development.
 
 ### Added
+
 - `linked build-workspace` — builds all linked packages in the current workspace in dependency order. Supports `-u` (updated only) and `--use-git` (git-based change detection). Migrated from `@semantu/cli`.
 - `linked build-package <filepath>` — given a file path, walks up to the nearest `package.json` and rebuilds that package. Designed for editor save hooks. Migrated from `@semantu/cli`.
 - `linked yarn <args>` — safe-yarn wrapper that preserves nested repo yarn.lock files during root-level yarn commands (for mrgit workflows). Migrated from `@semantu/cli`.
 
 ### Deprecated
+
 - The `lincd` binary is retained as a deprecated alias that prints a warning to stderr on invocation. It will be removed in a future major release; migrate scripts to `linked`.
 - `generateGruntConfig` export has been removed; it had no active callers. If you still reference it, migrate your package build to `tsc + tsconfig-to-dual-package` (see the package template).
 
 ### Removed
+
 - Grunt bin entry (`grunt`) removed from package.json bins.
 - Internal `config-grunt.cts` and `getGruntConfig` helper removed.
 - Grunt-related devDependencies (`grunt`, `grunt-cli`, `grunt-*`, `@lodder/grunt-postcss`, `load-grunt-tasks`) removed.
 
 ### Migration notes
+
 - Update `package.json` deps: `lincd-cli` → `@_linked/cli`.
 - Update `package.json` flag: `lincd: true` → `linkedPackage: true` (and `lincdApp: true` → `linkedApp: true` for apps). Legacy flags still read for now.
 - Update scripts: `yarn lincd <cmd>` → `yarn linked <cmd>`. The legacy alias still works but emits a deprecation warning.

package/README.md

@@ -1,24 +1,111 @@
-#LINCD CLI
-Command Line Interface for the [lincd.js](https://www.lincd.org) library
+# @_linked/cli
 
-### Installation
+Command-line tools for the `@_linked/*` packages and apps.
 
+## Install
+
+```bash
+npm install --save-dev @_linked/cli
+# or
+yarn add -D @_linked/cli
 ```
-npm install lincd-cli
+
+## Binaries
+
+Three executables ship in this package:
+
+- `linked` — primary command
+- `lnk` — short alias for `linked`
+- `lincd` — deprecated alias; prints a warning and forwards to `linked`. Will be removed in a future major release.
+
+## Commands
+
+Run `linked --help` for the full list. The commonly used ones:
+
+### App scaffolding
+
+```bash
+linked create-app <name>          # scaffold a new app (interactive)
+linked create-package <name>      # scaffold a new linkedPackage
+linked create-shape <name>        # add a shape file to the current package
+linked create-component <name>    # add a React component file
+```
+
+### Building
+
+```bash
+linked build                      # build the current package (tsc + checks)
+linked build-app                  # build frontend + backend for the current app
+linked build-workspace            # build all linked packages in the workspace in dependency order
+linked build-updated              # incremental: only packages that changed since last build
+linked build-package <file>       # walk up from a file path to find its package and rebuild
+```
+
+### Publishing / release
+
+```bash
+linked setup-publish              # install a changesets-based publish workflow in the current repo
+linked setup-publish --dual-branch          # use main + dev with @next prereleases
+linked setup-publish --configure-github     # also set branch protection via gh CLI
+linked setup-publish --scope community      # use NPM_AUTH_TOKEN_CM instead of NPM_AUTH_TOKEN
 ```
 
-or
+`setup-publish` writes:
+
+- `.github/workflows/ci.yml`, `publish.yml`, `changeset-check.yml`
+- `.changeset/config.json` + `README.md`
+- `.gitignore` entries
+- `publishConfig: {access: public}` + `@changesets/cli` devDeps in `package.json`
+- `package-lock.json` (via isolated tmpdir)
 
+### Dev workflow
+
+```bash
+linked start                      # run the dev server (app)
+linked dev                        # file-watch rebuild (package)
+linked yarn <args>                # safe-yarn: run yarn at root while preserving nested yarn.lock files
 ```
-yarn add lincd-cli
+
+### Registry / dev utilities
+
+```bash
+linked publish                    # publish the current package (for non-CI flows)
+linked register                   # register the package to the linked registry
+linked status                     # show which packages need build/publish
+linked depcheck                   # check for missing/unused deps
 ```
 
-### Usage
+## Package flags
 
-type
+The CLI recognizes two flags in `package.json`:
 
+```json
+{
+  "linkedPackage": true,     // marks a reusable library; build-workspace builds it
+  "linkedApp": true          // marks a deployable app; build-workspace skips it
+}
 ```
-npm exec lincd help
+
+The legacy `lincd: true` and `lincdApp: true` flags are still read for the transition period.
+
+## Development
+
+```bash
+cd packages/cli
+yarn build
 ```
 
-for available commands
+Dual ESM + CJS build via `tsconfig-to-dual-package`. Sources in `src/`, output in `lib/esm/` and `lib/cjs/`.
+
+### Templates
+
+Templates live in `defaults/`:
+
+- `defaults/app-with-backend/` — used by `linked create-app`
+- `defaults/app-static/` — minimal static app
+- `defaults/package/` — used by `linked create-package`
+- `defaults/setup-publish/` — workflow + changeset files written by `linked setup-publish` (single-branch default; `dual-branch/` subdirectory for the `--dual-branch` variant)
+
+## Repository
+
+`linked-cm/cli` on GitHub. License: MPL-2.0.

package/defaults/package/package.json

@@ -17,11 +17,10 @@
   "types": "lib/esm/index.d.ts",
   "license": "ISC",
   "scripts": {
-    "build": "rimraf ./lib && yarn build-esm && yarn build-cjs && yarn dual-package",
-    "build-cjs": "tsc -p tsconfig-cjs.json",
-    "build-esm": "tsc -p tsconfig-esm.json",
-    "dual-package": "tsconfig-to-dual-package ./tsconfig-cjs.json ./tsconfig-esm.json",
-    "dev": "tsc -p tsconfig-esm.json -w"
+    "start": "yarn linked dev",
+    "build": "yarn linked build",
+    "prepublishOnly": "yarn linked build production",
+    "postpublish": "yarn linked register"
   },
   "keywords": [
     "linked",
@@ -59,7 +58,6 @@
   "devDependencies": {
     "@types/node": "^22.13.14",
     "@_linked/cli": "^1.2",
-    "rimraf": "^5.0.7",
     "tsconfig-to-dual-package": "^1.2.0",
     "typescript": "^5.7.3"
   }

package/defaults/setup-publish/changeset/README.md

@@ -0,0 +1,20 @@
+# Changesets
+
+This package uses [changesets](https://github.com/changesets/changesets) for version management and publishing.
+
+## Adding a changeset
+
+When making a change that should trigger a new release, run:
+
+```bash
+npx changeset
+```
+
+This generates a markdown file in `.changeset/` describing the change. Commit it with your PR.
+
+On merge to `main`, the publish workflow either:
+
+1. Creates (or updates) a **Release PR** that bumps the version + updates `CHANGELOG.md`, or
+2. If the Release PR is already merged, publishes the new version to npm.
+
+Changes that don't need a release (docs, CI config, tooling) can skip the changeset — the check is a warning, not a block.

package/defaults/setup-publish/changeset/config.json

@@ -0,0 +1,14 @@
+{
+  "$schema": "https://unpkg.com/@changesets/config@3.1.1/schema.json",
+  "changelog": [
+    "@changesets/changelog-github",
+    { "repo": "{{REPO_SLUG}}" }
+  ],
+  "commit": false,
+  "fixed": [],
+  "linked": [],
+  "access": "public",
+  "baseBranch": "main",
+  "updateInternalDependencies": "patch",
+  "ignore": []
+}

package/defaults/setup-publish/dual-branch/changeset/README.md

@@ -0,0 +1,20 @@
+# Changesets
+
+This package uses [changesets](https://github.com/changesets/changesets) for version management and publishing.
+
+## Adding a changeset
+
+When making a change that should trigger a new release, run:
+
+```bash
+npx changeset
+```
+
+This generates a markdown file in `.changeset/` describing the change. Commit it with your PR.
+
+On merge to `main`, the publish workflow either:
+
+1. Creates (or updates) a **Release PR** that bumps the version + updates `CHANGELOG.md`, or
+2. If the Release PR is already merged, publishes the new version to npm.
+
+Changes that don't need a release (docs, CI config, tooling) can skip the changeset — the check is a warning, not a block.

package/defaults/setup-publish/dual-branch/changeset/config.json

@@ -0,0 +1,14 @@
+{
+  "$schema": "https://unpkg.com/@changesets/config@3.1.1/schema.json",
+  "changelog": [
+    "@changesets/changelog-github",
+    { "repo": "{{REPO_SLUG}}" }
+  ],
+  "commit": false,
+  "fixed": [],
+  "linked": [],
+  "access": "public",
+  "baseBranch": "main",
+  "updateInternalDependencies": "patch",
+  "ignore": []
+}

package/defaults/setup-publish/dual-branch/github/workflows/changeset-check.yml

@@ -0,0 +1,43 @@
+name: Changeset Check
+
+on:
+  pull_request:
+    branches:
+      - main
+      - dev
+
+jobs:
+  changeset-check:
+    name: Check for changeset
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
+
+      - name: Check for changeset files
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const { data: files } = await github.rest.pulls.listFiles({
+              owner: context.repo.owner,
+              repo: context.repo.repo,
+              pull_number: context.issue.number,
+            });
+
+            const hasChangeset = files.some(f =>
+              f.filename.startsWith('.changeset/') &&
+              f.filename.endsWith('.md') &&
+              f.filename !== '.changeset/README.md'
+            );
+
+            if (!hasChangeset) {
+              await github.rest.issues.createComment({
+                owner: context.repo.owner,
+                repo: context.repo.repo,
+                issue_number: context.issue.number,
+                body: '⚠️ **No changeset found.** If this PR should trigger a release, run `npx changeset` and commit the generated file.\n\nIf this change doesn\'t need a release (docs, CI config, etc.), you can ignore this message.'
+              });
+              core.warning('No changeset file found in this PR.');
+            }

package/defaults/setup-publish/dual-branch/github/workflows/ci.yml

@@ -0,0 +1,44 @@
+name: CI
+
+on:
+  pull_request:
+    branches:
+      - main
+      - dev
+
+jobs:
+  build-and-test:
+    name: Build & Test
+    runs-on: ubuntu-latest
+    steps:
+      - name: Detect Release PR
+        id: rpr
+        run: |
+          if [[ "${{ github.event.pull_request.head.ref }}" == "changeset-release/main" ]]; then
+            echo "is_release_pr=true" >> $GITHUB_OUTPUT
+            echo "Release PR from changesets/action detected — skipping build/test (auto-generated version+CHANGELOG only)."
+          else
+            echo "is_release_pr=false" >> $GITHUB_OUTPUT
+          fi
+
+      - name: Checkout
+        if: steps.rpr.outputs.is_release_pr == 'false'
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        if: steps.rpr.outputs.is_release_pr == 'false'
+        uses: actions/setup-node@v4
+        with:
+          node-version: 22.16.0
+
+      - name: Install dependencies
+        if: steps.rpr.outputs.is_release_pr == 'false'
+        run: npm ci --legacy-peer-deps
+
+      - name: Build
+        if: steps.rpr.outputs.is_release_pr == 'false'
+        run: npm run build
+
+      - name: Test
+        if: steps.rpr.outputs.is_release_pr == 'false'
+        run: npm test --if-present

package/defaults/setup-publish/dual-branch/github/workflows/publish.yml

@@ -0,0 +1,122 @@
+name: Publish
+
+on:
+  push:
+    branches:
+      - main
+      - dev
+
+concurrency: ${{ github.workflow }}-${{ github.ref }}
+
+jobs:
+  release:
+    name: Publish Stable Release
+    if: github.ref == 'refs/heads/main'
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      pull-requests: write
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 22.16.0
+          registry-url: "https://registry.npmjs.org"
+
+      - name: Install dependencies
+        run: npm ci --legacy-peer-deps
+
+      - name: Build
+        run: npm run build
+
+      - name: Create release Pull Request or Publish
+        id: changesets
+        uses: changesets/action@v1
+        with:
+          publish: npx changeset publish
+          title: "chore: release"
+          commit: "chore: release"
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          NODE_AUTH_TOKEN: ${{ secrets.{{NPM_SECRET_NAME}} }}
+          NPM_TOKEN: ${{ secrets.{{NPM_SECRET_NAME}} }}
+
+  sync-version-to-dev:
+    name: Sync Version to Dev
+    needs: release
+    if: github.ref == 'refs/heads/main'
+    runs-on: ubuntu-latest
+    permissions:
+      contents: write
+      pull-requests: write
+    steps:
+      - name: Checkout dev
+        uses: actions/checkout@v4
+        with:
+          ref: dev
+          fetch-depth: 0
+
+      - name: Sync package.json version from main via PR
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+        run: |
+          MAIN_VERSION=$(git show origin/main:package.json | node -p "JSON.parse(require('fs').readFileSync(0,'utf8')).version")
+          DEV_VERSION=$(node -p "require('./package.json').version")
+          if [ "$MAIN_VERSION" != "$DEV_VERSION" ]; then
+            BRANCH="chore/sync-version-${MAIN_VERSION}"
+            git config user.name "github-actions[bot]"
+            git config user.email "github-actions[bot]@users.noreply.github.com"
+            git checkout -b "$BRANCH"
+            npm version "$MAIN_VERSION" --no-git-tag-version --allow-same-version
+            git add package.json package-lock.json
+            git commit -m "chore: sync package.json version to $MAIN_VERSION from main"
+            git push origin "$BRANCH"
+            gh pr create \
+              --base dev \
+              --head "$BRANCH" \
+              --title "chore: sync package.json version to $MAIN_VERSION from main" \
+              --body "Automated version sync from main after release."
+          fi
+
+  dev-release:
+    name: Publish Dev Release
+    if: github.ref == 'refs/heads/dev'
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Setup Node.js
+        uses: actions/setup-node@v4
+        with:
+          node-version: 22.16.0
+          registry-url: "https://registry.npmjs.org"
+
+      - name: Install dependencies
+        run: npm ci --legacy-peer-deps
+
+      - name: Build
+        run: npm run build
+
+      - name: Publish next release
+        run: |
+          # Start from main's version so changesets apply on top of the latest stable
+          git fetch origin main --depth=1
+          MAIN_VERSION=$(git show origin/main:package.json | node -p "JSON.parse(require('fs').readFileSync(0,'utf8')).version")
+          npm version "$MAIN_VERSION" --no-git-tag-version --allow-same-version
+          # Apply pending changesets to get the next version
+          npx changeset version
+          NEXT_VERSION=$(node -p "require('./package.json').version")
+          # Append dev prerelease identifier
+          DEV_VERSION="${NEXT_VERSION}-next.$(date +%Y%m%d%H%M%S)"
+          npm version "$DEV_VERSION" --no-git-tag-version
+          npm publish --tag next
+        env:
+          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+          NODE_AUTH_TOKEN: ${{ secrets.{{NPM_SECRET_NAME}} }}
+          NPM_TOKEN: ${{ secrets.{{NPM_SECRET_NAME}} }}