Skip to content

fix(ci): remove invalid flags from changeset publish command - #2050

Merged
ArtieReus merged 2 commits into
mainfrom
artie-fix-release-not-knowing-flags
Oct 6, 2026
Merged

ArtieReus merged 2 commits into
mainfrom
artie-fix-release-not-knowing-flags

Conversation

@ArtieReus

Copy link
Copy Markdown
Collaborator

Summary

Fixes the publish workflow failure that occurred after merging the version bump PR. The release script was using invalid command-line flags that don't exist in @changesets/cli@3.0.3, causing the publish action to fail with an "Unknown option '-r'" error.

Changes Made

  • Removed invalid -r and --no-git-checks flags from the release script in package.json
  • Updated to use changeset publish without additional flags
  • The CHANGESETS_OUTPUT environment variable is automatically handled by the changesets CLI when running in GitHub Actions

Related Issues

Screenshots (if applicable)

N/A - CI/CD configuration change only

Testing Instructions

  1. Verify the change locally:
pnpm i
pnpm run release
  1. The command should run without "Unknown option" errors
  2. Merge this PR and verify the next publish workflow runs successfully

Checklist

  • I have performed a self-review of my code.
  • I have commented my code, particularly in hard-to-understand areas.
  • I have added tests that prove my fix is effective or that my feature works.
  • New and existing unit tests pass locally with my changes.
  • I have made corresponding changes to the documentation (if applicable).
  • My changes generate no new warnings or errors.
  • I have created a changeset for my changes.

Note: Tests and changeset are not applicable for this CI configuration fix. The fix itself is minimal (removing invalid flags) and will be validated by the next successful publish workflow run.

PR Manifesto

Review the PR Manifesto for best practises.

Signed-off-by: Arturo Reuschenbach Puncernau <reuschenbach@gmail.com>
Copilot AI balanced review requested due to automatic review settings October 6, 2026 08:50
@ArtieReus
ArtieReus requested a review from a team as a code owner October 6, 2026 08:50
@changeset-bot

changeset-bot Bot commented Oct 6, 2026 •

Copy link
Copy Markdown

⚠️ No Changeset found

Latest commit: 99362f3

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Copilot review overview

🟢 Approval recommended

The focused change matches Changesets CLI usage and the existing release workflow.

Review effort: Balanced
Findings: None

What changed in this PR

Removes unsupported Changesets CLI flags that caused the npm publishing workflow to fail.

Changes:

  • Updates the release script to use the supported changeset publish command.
File Description
package.json Removes invalid publish flags from the release script.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@ArtieReus ArtieReus self-assigned this Oct 6, 2026
@ArtieReus
ArtieReus merged commit c52e12d into main Oct 6, 2026
25 checks passed
@ArtieReus
ArtieReus deleted the artie-fix-release-not-knowing-flags branch October 6, 2026 09:00
@github-actions

github-actions Bot commented Oct 6, 2026

Copy link
Copy Markdown
Contributor
PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-10-06 09:00 UTC

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.

4 participants