Skip to content

Conversation

@CosmicJesterX
Copy link

No description provided.

Copy link
Contributor

@vercel vercel bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Additional Suggestion:

The main package is marked as private, which will prevent the npm-publish-github-packages workflow from successfully publishing to GitHub Packages.

View Details
📝 Patch Details
diff --git a/.github/workflows/npm-publish-github-packages.yml b/.github/workflows/npm-publish-github-packages.yml
deleted file mode 100644
index ea2d329fa0..0000000000
--- a/.github/workflows/npm-publish-github-packages.yml
+++ /dev/null
@@ -1,36 +0,0 @@
-# This workflow will run tests using node and then publish a package to GitHub Packages when a release is created
-# For more information see: https://docs.github.com/en/actions/publishing-packages/publishing-nodejs-packages
-
-name: Node.js Package
-
-on:
-  release:
-    types: [created]
-
-jobs:
-  build:
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
-        with:
-          node-version: 20
-      - run: npm ci
-      - run: npm test
-
-  publish-gpr:
-    needs: build
-    runs-on: ubuntu-latest
-    permissions:
-      contents: read
-      packages: write
-    steps:
-      - uses: actions/checkout@v4
-      - uses: actions/setup-node@v4
-        with:
-          node-version: 20
-          registry-url: https://npm.pkg.github.com/
-      - run: npm ci
-      - run: npm publish
-        env:
-          NODE_AUTH_TOKEN: ${{secrets.GITHUB_TOKEN}}

Analysis

Removed misplaced npm-publish-github-packages workflow

What failed: The npm-publish-github-packages workflow would fail when executed because it attempts to run npm publish on the root package, which has "private": true. Per npm documentation, npm refuses to publish packages marked as private.

Why it was wrong: This workflow was incompatible with the Next.js monorepo structure:

  1. The root package.json is intentionally marked "private": true (line 3) to prevent accidental publication of the monorepo coordinator
  2. Next.js has its own release mechanism via the changesets workflow for publishing individual workspace packages
  3. The workflow cannot be fixed by removing "private": true" - that would break monorepo conventions and safety mechanisms
  4. The workflow cannot be adapted to publish workspace packages because it runs npm publish from the root with no package specification

Fix applied: Removed .github/workflows/npm-publish-github-packages.yml as it was a misconfigured workflow that conflicts with the project's established release process and monorepo structure.

Fix on Vercel

@ztanner ztanner closed this Nov 19, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants