@changesets/action

1.5.2

Patch Changes

75202af Thanks @enisdenjo! - Upstream "Wire up @octokit/plugin-throttling with all GitHub Octokit instances"

75202af Thanks @enisdenjo! - Upstream "Use logging provided by @actions/core"

75202af Thanks @enisdenjo! - Upstream "Add a throttling plugin to the used Octokit instance to retry requests after hitting secondary rate limits"

1.5.1

Patch Changes

b81ec1a Thanks @enisdenjo! - githubReleaseAssets has no default

1.5.0

Minor Changes

3ee9d10 Thanks @enisdenjo! - Merge upstream changesets/action

ebbfc3c Thanks @dotansimha! - Allow to specify createGithubReleases: aggregate, in order to publish a single GitHub Release

1.4.0

Minor Changes

1775681 Thanks @enisdenjo! - Upload assets to GitHub release

1.3.0

Minor Changes

#167 993a0a0 Thanks @dmregister! - Added pullRequestNumber to the action's outputs

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

#144 898d125 Thanks @Andarist! - Updated all Changesets dependencies. This should fix parsing issues for completely empty summaries that has been fixed in @changesets/[email protected].

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

#128 1937303 Thanks @dhruvdutt! - Setup the git user in the local config instead of the global one.

#131 d3db9ec Thanks @jacklesliewise! - Added setupGitUser option to enable or disable setting up a default git user

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.