Skip to content

Latest commit

 

History

History
118 lines (60 loc) · 7.57 KB

CHANGELOG.md

File metadata and controls

118 lines (60 loc) · 7.57 KB

@changesets/action

1.4.9

Patch Changes

  • #415 57ab80c Thanks @benmccann! - Improve error message when attempting to publish without publish script defined

1.4.8

Patch Changes

  • #393 48ab0d2 Thanks @s0! - Ensure the PR remains open when updated

  • #393 48ab0d2 Thanks @s0! - Switch to cheaper API for querying existing PRs

1.4.7

Patch Changes

1.4.6

Patch Changes

1.4.5

Patch Changes

  • #282 eb19e25 Thanks @mark-omarov! - Updated a few dependencies to patch the security vulnerabilities that were reported for their older versions.

1.4.4

Patch Changes

1.4.3

Patch Changes

1.4.2

Patch Changes

1.4.1

Patch Changes

  • #123 b78f480 Thanks @Andarist! - Updated @actions/* dependencies to avoid using deprecated features of the runner.

1.4.0

Minor Changes

Patch Changes

  • #228 bff53cc Thanks @iansan5653! - Add is:pull-request to search query when looking for existing PR. This fixes an issue with user-owned PATs.

1.3.0

Minor Changes

Patch Changes

  • #157 521c27b Thanks @emmenko! - Automatically adjust GitHub PR message if it exceeds a size limit of 60k characters by omitting some of the changelog information.

1.2.2

Patch Changes

  • #161 52c9ce7 Thanks @bicknellr! - Change directory to cwd before running git user setup. This fixes an issue when the action starts its execution not in a git repository.

1.2.1

Patch Changes

1.2.0

Minor Changes

  • #130 5c0997b Thanks @akphi! - Added createGithubReleases input option (defaults to true) to control whether to create Github releases during publish or not.
  • #134 1ed9bc2 Thanks @dmregister! - Added cwd input option that can be used in projects that are not in the root directory.

1.1.0

Minor Changes

1.0.0

Major Changes

  • #118 05c863d Thanks @Andarist! - From now on this action will be released using the Changesets-based workflow (using itself). Thanks to that we'll have a good release history. The users will be able to find specific versions of the action and will be able to track changes over time. It also improves the security as the build artifact will always get built in the CI environment, using a frozen lockfile.