- #255
f2660aaThanks @ernestognw! - Allow customize PRbranchfield
- #282
eb19e25Thanks @mark-omarov! - Updated a few dependencies to patch the security vulnerabilities that were reported for their older versions.
- #291
db8a109Thanks @varl! - Wire up@octokit/plugin-throttlingwith all GitHub Octokit instances
-
#286
225a1e8Thanks @varl! - This patch implements the@octokit/plugin-throttlingplugin 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/actiongitting spurious secondary rate limits and failing CI jobs, for which the only known workaround is to simply re-run the job.
- #123
b78f480Thanks @Andarist! - Updated@actions/*dependencies to avoid using deprecated features of the runner.
- #228
bff53ccThanks @iansan5653! - Addis:pull-requestto search query when looking for existing PR. This fixes an issue with user-owned PATs.
- #167
993a0a0Thanks @dmregister! - AddedpullRequestNumberto the action's outputs
- #157
521c27bThanks @emmenko! - Automatically adjust GitHub PR message if it exceeds a size limit of 60k characters by omitting some of the changelog information.
- #161
52c9ce7Thanks @bicknellr! - Change directory tocwdbefore running git user setup. This fixes an issue when the action starts its execution not in a git repository.
- #144
898d125Thanks @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
5c0997bThanks @akphi! - AddedcreateGithubReleasesinput option (defaults totrue) to control whether to create Github releases during publish or not.
- #134
1ed9bc2Thanks @dmregister! - Addedcwdinput option that can be used in projects that are not in the root directory.
- #128
1937303Thanks @dhruvdutt! - Setup the git user in the local config instead of the global one.
- #131
d3db9ecThanks @jacklesliewise! - AddedsetupGitUseroption to enable or disable setting up a default git user
- #118
05c863dThanks @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.