Skip to content

Changeset fails on ignore pattern when there's no matches #1794

Closed

Description

@RobertGemmaJr

Prisma now generates their own nested subfolders which includes a package.json file. It's created via a prisma generate which we do on postinstall. Since they're automatically they are gitignored.

The issue is that we need the ignore locally but the changeset bot never runs an install so it never matches the ignore glob. Here's my config:

Config

{
  "$schema": "https://unpkg.com/@changesets/[email protected]/schema.json",
  "changelog": "@changesets/cli/changelog",
  "commit": false,
  "privatePackages": {
    "version": true,
    "tag": true
  },
  "fixed": [],
  "linked": [],
  "access": "restricted",
  "baseBranch": "main",
  "updateInternalDependencies": "patch",
  "ignore": ["prisma-client-*"]
}

Error

Image

Proposed Solution

The path(s) in the ignore config should NOT fail if they do not find a match.

Activity

  1. RobertGemmaJr commented on Dec 2, 2025

    @RobertGemmaJr
    Author

    Perhaps also worth noting that I now have to run my install and postinstall scripts in the release workflow as a workaround to this as well. I cannot use npx @changeset/cli ... anymore for the same issue. When the changeset action fails here the entire workflow fails

    name: 🚀 Changesets Versioning & Release
    
    on:
      push:
        branches:
          - main
    
    jobs:
      release:
        name: 🦋 Changeset Release Action
        runs-on: ubuntu-latest
        permissions:
          contents: write
        steps:
          - name: ⬇️ Checkout repo
            uses: actions/checkout@v4
            with:
              token: ${{ secrets.CJ_PAT }}
          - name: 🔶 Install pnpm
            uses: pnpm/action-setup@v4
    
          - name: ⎔ Setup node
            uses: actions/setup-node@v4
            with:
              node-version-file: .nvmrc
              cache: pnpm
    
          # Make commits and open PRs as CJ
          - name: 🤖 CJ Login
            run: |
              git config user.name ccv-cj
              git config user.email [email protected]
              echo "GITHUB_TOKEN=${{ secrets.CJ_PAT }}" >> $GITHUB_ENV
    
          - name: 📥 Install Dependencies
            run: pnpm install --frozen-lockfile
    
          - name: "🦋 Changesets: Create Pull Request or Publish Release"
            id: changesets
            uses: changesets/action@v1
            with:
              title: "chore: Version Packages"
              commit: "chore(release): Automated version bump from changesets"
              # NOTE @RobertGemmaJr: We login as CJ manually
              setupGitUser: false
              # Create a new tag in GitHub instead of publishing to npm
              # NOTE @RobertGemmaJr: The command still causes the action to create a release on GitHub
              publish: pnpm changeset tag
              createGithubReleases: true
    
        outputs:
          hasChangesets: ${{ steps.changesets.outputs.hasChangesets }}
          published: ${{ steps.changesets.outputs.published }}
          publishedPackages: ${{ steps.changesets.outputs.publishedPackages }}
  2. added a commit that references this issue on Mar 9, 2026
    9e3f7a2
  3. added this to the v3 milestone on Jun 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions