- #282
eb19e25
Thanks @mark-omarov! - Updated a few dependencies to patch the security vulnerabilities that were reported for their older versions.
- #291
db8a109
Thanks @varl! - Wire up@octokit/plugin-throttling
with all GitHub Octokit instances
-
#286
225a1e8
Thanks @varl! - This patch implements the@octokit/plugin-throttling
plugin and wires it up with the internal GitHub Octokit instance.This plugin is recommended by the Octokit docs as it implements all the GitHub best practices for integrators.
This should help with
changesets/action
gitting spurious secondary rate limits and failing CI jobs, for which the only known workaround is to simply re-run the job.
- #123
b78f480
Thanks @Andarist! - Updated@actions/*
dependencies to avoid using deprecated features of the runner.
- #228
bff53cc
Thanks @iansan5653! - Addis:pull-request
to search query when looking for existing PR. This fixes an issue with user-owned PATs.
- #167
993a0a0
Thanks @dmregister! - AddedpullRequestNumber
to the action's outputs
- #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.
- #161
52c9ce7
Thanks @bicknellr! - Change directory tocwd
before running git user setup. This fixes an issue when the action starts its execution not in a git repository.
- #144
898d125
Thanks @Andarist! - Updated all Changesets dependencies. This should fix parsing issues for completely empty summaries that has been fixed in@changesets/parse@0.3.11
.
- #130
5c0997b
Thanks @akphi! - AddedcreateGithubReleases
input option (defaults totrue
) to control whether to create Github releases during publish or not.
- #134
1ed9bc2
Thanks @dmregister! - Addedcwd
input option that can be used in projects that are not in the root directory.
- #128
1937303
Thanks @dhruvdutt! - Setup the git user in the local config instead of the global one.
- #131
d3db9ec
Thanks @jacklesliewise! - AddedsetupGitUser
option to enable or disable setting up a default git user
- #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.