Skip to content

chore(release): new release - #292

Merged
alexander-akait merged 1 commit into
mainfrom
changeset-release/main
Nov 13, 2026
Merged

alexander-akait merged 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Nov 13, 2026 •

Copy link
Copy Markdown
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

tapable@2.3.4

Patch Changes

@github-actions
github-actions Bot force-pushed the changeset-release/main branch from adee109 to 8068c21 Compare November 13, 2026 14:44
@alexander-akait
alexander-akait merged commit 10e336b into main Nov 13, 2026
3 checks passed
@alexander-akait
alexander-akait deleted the changeset-release/main branch November 13, 2026 14:46
alexander-akait added a commit that referenced this pull request Nov 13, 2026
#292 versioned 2.3.4, but the Release workflow failed before publishing it.
Restore its changesets, the 2.3.3 version and the changelog, so the fixed
workflow opens the release pull request again once this merges.
alexander-akait added a commit that referenced this pull request Nov 13, 2026
…the unpublished 2.3.4 (#293)

* ci: pin changesets/action back to v1.9.0

v2 only works with Changesets CLI v3, and tapable is on @changesets/cli v2, so
the Release workflow fails before publishing ("Changesets CLI v2 is not
supported; use Changesets action v1 instead") and 2.3.4 never reached npm.

* ci: update to Changesets CLI v3 for changesets/action v2

changesets/action v2 only works with Changesets CLI v3, so the Release
workflow stopped before publishing. Instead of pinning the action back:

- @changesets/cli ^3 and @changesets/get-github-info ^1; the changelog
  generator moves to its getCommitInfo/getPullRequestInfo API, as webpack's did
- the workflow keeps changesets/action v2.1.2 with its renamed inputs
  (github-token, version-script, publish-script, commit-message, pr-title)

* chore: revert the unpublished 2.3.4 release

#292 versioned 2.3.4, but the Release workflow failed before publishing it.
Restore its changesets, the 2.3.3 version and the changelog, so the fixed
workflow opens the release pull request again once this merges.
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.

1 participant