You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Changeset fails on ignore pattern when there's no matches #1794
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:
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 & Releaseon:
push:
branches:
- mainjobs:
release:
name: 🦋 Changeset Release Actionruns-on: ubuntu-latestpermissions:
contents: writesteps:
- name: ⬇️ Checkout repouses: actions/checkout@v4with:
token: ${{ secrets.CJ_PAT }}
- name: 🔶 Install pnpmuses: pnpm/action-setup@v4
- name: ⎔ Setup nodeuses: actions/setup-node@v4with:
node-version-file: .nvmrccache: pnpm# Make commits and open PRs as CJ
- name: 🤖 CJ Loginrun: | git config user.name ccv-cj git config user.email [email protected] echo "GITHUB_TOKEN=${{ secrets.CJ_PAT }}" >> $GITHUB_ENV
- name: 📥 Install Dependenciesrun: pnpm install --frozen-lockfile
- name: "🦋 Changesets: Create Pull Request or Publish Release"id: changesetsuses: changesets/action@v1with:
title: "chore: Version Packages"commit: "chore(release): Automated version bump from changesets"# NOTE @RobertGemmaJr: We login as CJ manuallysetupGitUser: 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 GitHubpublish: pnpm changeset tagcreateGithubReleases: trueoutputs:
hasChangesets: ${{ steps.changesets.outputs.hasChangesets }}published: ${{ steps.changesets.outputs.published }}publishedPackages: ${{ steps.changesets.outputs.publishedPackages }}
Activity
RobertGemmaJr commentedon Dec 2, 2025
Perhaps also worth noting that I now have to run my install and postinstall scripts in the
releaseworkflow as a workaround to this as well. I cannot usenpx @changeset/cli ...anymore for the same issue. When the changeset action fails here the entire workflow failsfix(config): do not error on unmatched ignore patterns