Sourced from stefanzweifel/git-auto-commit-action's releases.
v6.0.1
Fixed
- Disable Check if Repo is in Detached State (#379)
@stefanzweifelv6.0.0
Added
- Throw error early if repository is in a detached state (#357)
Fixed
- Fix PAT instructions with Dependabot (#376)
@DreamsorcererRemoved
- Remove support for
create_branch,skip_checkout,skip_Fetch(#314)
Sourced from stefanzweifel/git-auto-commit-action's changelog.
Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
Unreleased
TBD
v6.0.1 - 2025-06-11
Fixed
- Disable Check if Repo is in Detached State (#379)
@stefanzweifelv6.0.0 - 2025-06-10
Added
- Throw error early if repository is in a detached state (#357)
Fixed
- Fix PAT instructions with Dependabot (#376)
@DreamsorcererRemoved
- Remove support for
create_branch,skip_checkout,skip_Fetch(#314)v5.2.0 - 2025-04-19
Added
- Add
create_git_tag_onlyoption to skip commiting and always create a git-tag. (#364)@zMynxx- Add Test for
create_git_tag_onlyfeature (#367)@stefanzweifelFixed
v5.1.0 - 2025-01-11
Changed
- Include
github.actor_idin defaultcommit_author(#354)@parkerbxyzFixed
... (truncated)
778341a
Merge pull request #379
from stefanzweifel/disable-detached-state-check33b203d
Disable Check if Repo is in Detached Statea82d80a
Update CHANGELOG3cc016c
Merge pull request #375
from stefanzweifel/v6-nextddb7ae4
Merge pull request #376
from Dreamsorcerer/patch-1b001e5f
Apply suggestions from code review6494dc6
Fix PAT instructions with Dependabot7618051
Add deprecated inputs to fix unbound variable issueae11462
Merge pull request #371
from stefanzweifel/dependabot/npm_and_yarn/bats-1.12.03058f91
Bump bats from 1.11.1 to 1.12.0Sourced from @octokit/request's
releases.
v10.0.2
10.0.2 (2025-05-20)
Bug Fixes
v10.0.1
10.0.1 (2025-05-20)
Bug Fixes
v10.0.0
10.0.0 (2025-05-20)
Continuous Integration
BREAKING CHANGES
Drop support for NodeJS v18
build: set minimal node version in build script to v20
ci: stop testing against NodeJS v18
fe8bb4b
fix(deps): update octokit monorepo (major) (#759)a4c1f27
chore(deps): update dependency undici to v7 (#761)8cf6d84
fix(deps): update dependency fast-content-type-parse to v3 (#747)1eefea8
ci: stop testing against NodeJS v18 (#756)b73d921
chore(deps): update dependency undici to v6.21.2 [security] (#758)9820bbe
build(deps): bump vite from 6.2.6 to 6.3.4 (#755)6150627
ci: replace OCTOKITBOT_PROJECT_ACTION_TOKEN and
OCTOKITBOT_PAT with a tok...bcd76d7
build(deps): bump vite from 6.2.5 to 6.2.6 (#754)Sourced from undici's releases.
v7.10.0
What's Changed
- Add "clientLifetime" option to close and remove connections from the pool after a specified time. by
@dhalbrookin nodejs/undici#4175- remove spurious only by
@mcollinain nodejs/undici#4207- add node v24 workflow by
@tsctxin nodejs/undici#4206- Update WPT by
@github-actionsin nodejs/undici#4172- chore: add
pnpm-lock.yamlto.gitignoreby@styflein nodejs/undici#4227- fix: agent memory leak by
@styflein nodejs/undici#4223- Add ability to detect when MemoryCacheStore reaches max size by
@FelixVaughanin nodejs/undici#4224- feat(ProxyAgent): match Curl behavior in HTTP->HTTP Proxy connections by
@caitpin nodejs/undici#4180- docs: correct example in FormData request by
@inyourtimein nodejs/undici#4226New Contributors
@dhalbrookmade their first contribution in nodejs/undici#4175@caitpmade their first contribution in nodejs/undici#4180@inyourtimemade their first contribution in nodejs/undici#4226Full Changelog: https://github.com/nodejs/undici/compare/v7.9.0...v7.10.0
v7.9.0
What's Changed
- build(deps): bump step-security/harden-runner from 2.10.2 to 2.11.1 by
@dependabotin nodejs/undici#4134- Update WPT by
@github-actionsin nodejs/undici#4155- Update WPT by
@github-actionsin nodejs/undici#4170- feat: add new
acceptNonStandardSearchParametersMockAgent option by@dario-piotrowiczin nodejs/undici#4148- fix: cache: treat cache-control request header case-insensitively by
@alxndrsnin nodejs/undici#4131- cache: honour unqualified no-cache response directive by
@alxndrsnin nodejs/undici#4178- build(deps): bump ossf/scorecard-action from 2.4.0 to 2.4.1 by
@dependabotin nodejs/undici#4079- Ensure conflicting flat headers in HTTP/2 are combined correctly by
@pimterryin nodejs/undici#4196- Add stats of client and pool to be accessible through agent by
@tdeekensin nodejs/undici#4157- Fix missing code in diagnostics example by
@islandryuin nodejs/undici#4195- Doc cors spec compliance by
@FelixVaughanin nodejs/undici#4202- Restore cache tests & fix max-age behavior by
@mcollinain nodejs/undici#4198New Contributors
@tdeekensmade their first contribution in nodejs/undici#4157@islandryumade their first contribution in nodejs/undici#4195@FelixVaughanmade their first contribution in nodejs/undici#4202Full Changelog: https://github.com/nodejs/undici/compare/v7.8.0...v7.9.0
5ad8998
Bumped v7.10.0 (#4231)9e0cfcb
docs: correct example in FormData request (#4226)95fd9d3
feat(ProxyAgent): match Curl behavior in HTTP->HTTP Proxy connections
(#4180)a8d280c
Add ability to detect when MemoryCacheStore reaches max size (#4224)59940c8
fix: agent memory leak (#4223)1262f61
Revert "chore: update WPT (#4172)"d6deb77
chore: add pnpm-lock.yaml to .gitignore (#4227)dcf82a7
chore: update WPT (#4172)2ed2a8a
add node v24 workflow (#4206)bf4c199
remove spurious only (#4207)Sourced from @octokit/auth-app's
releases.
v8.0.1
8.0.1 (2025-05-20)
Bug Fixes
v8.0.0
8.0.0 (2025-05-20)
Continuous Integration
BREAKING CHANGES
Drop support for NodeJS v18
build: set minimal node version in build script to v20
ci: stop testing against NodeJS v18
56cded1
fix(deps): update octokit monorepo (major) (#704)a168de5
ci: stop testing against NodeJS v18 (#702)4bee524
build(deps): lock file maintenance (#703)8a9a326
build(deps-dev): bump vite from 6.3.2 to 6.3.5 (#701)b2ad57f
build(deps): lock file maintenance (#697)00bb36c
build(deps): lock file maintenance (#696)0f9ad9c
build(deps-dev): bump vite from 6.2.5 to 6.2.6 (#695)Sourced from dotenv's changelog.
17.2.2 (2025-09-02)
Added
- 🙏 A big thank you to new sponsor Tuple.app - the premier screen sharing app for developers on macOS and Windows. Go check them out. It's wonderful and generous of them to give back to open source by sponsoring dotenv. Give them some love back.
Sourced from esbuild's releases.
v0.25.9
Better support building projects that use Yarn on Windows (#3131, #3663)
With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the
C:drive. The problem was as follows:
- Yarn in Plug'n'Play mode on Windows stores its global module cache on the
C:drive- Some developers put their projects on the
D:drive- Yarn generates relative paths that use
../..to get from the project directory to the cache directory- Windows-style paths don't support directory traversal between drives via
..(soD:\..is justD:)- I didn't have access to a Windows machine for testing this edge case
Yarn works around this edge case by pretending Windows-style paths beginning with
C:\are actually Unix-style paths beginning with/C:/, so the../..path segments are able to navigate across drives inside Yarn's implementation. This was broken for a long time in esbuild but I finally got access to a Windows machine and was able to debug and fix this edge case. So you should now be able to bundle these projects with esbuild.Preserve parentheses around function expressions (#4252)
The V8 JavaScript VM uses parentheses around function expressions as an optimization hint to immediately compile the function. Otherwise the function would be lazily-compiled, which has additional overhead if that function is always called immediately as lazy compilation involves parsing the function twice. You can read V8's blog post about this for more details.
Previously esbuild did not represent parentheses around functions in the AST so they were lost during compilation. With this change, esbuild will now preserve parentheses around function expressions when they are present in the original source code. This means these optimization hints will not be lost when bundling with esbuild. In addition, esbuild will now automatically add this optimization hint to immediately-invoked function expressions. Here's an example:
// Original code const fn0 = () => 0 const fn1 = (() => 1) console.log(fn0, function() { return fn1() }())// Old output
const fn0 = () => 0;
const fn1 = () => 1;
console.log(fn0, function() {
return fn1();
}());// New output
const fn0 = () => 0;
const fn1 = (() => 1);
console.log(fn0, (function() {
return fn1();
})());
Note that you do not want to wrap all function expressions in parentheses. This optimization hint should only be used for functions that are called on initial load. Using this hint for functions that are not called on initial load will unnecessarily delay the initial load. Again, see V8's blog post linked above for details.
Update Go from 1.23.10 to 1.23.12 (#4257, #4258)
This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4674 and CVE-2025-47907) from vulnerability scanners that only detect which version of the Go compiler esbuild uses.
Sourced from esbuild's changelog.
0.25.9
Better support building projects that use Yarn on Windows (#3131, #3663)
With this release, you can now use esbuild to bundle projects that use Yarn Plug'n'Play on Windows on drives other than the
C:drive. The problem was as follows:
- Yarn in Plug'n'Play mode on Windows stores its global module cache on the
C:drive- Some developers put their projects on the
D:drive- Yarn generates relative paths that use
../..to get from the project directory to the cache directory- Windows-style paths don't support directory traversal between drives via
..(soD:\..is justD:)- I didn't have access to a Windows machine for testing this edge case
Yarn works around this edge case by pretending Windows-style paths beginning with
C:\are actually Unix-style paths beginning with/C:/, so the../..path segments are able to navigate across drives inside Yarn's implementation. This was broken for a long time in esbuild but I finally got access to a Windows machine and was able to debug and fix this edge case. So you should now be able to bundle these projects with esbuild.Preserve parentheses around function expressions (#4252)
The V8 JavaScript VM uses parentheses around function expressions as an optimization hint to immediately compile the function. Otherwise the function would be lazily-compiled, which has additional overhead if that function is always called immediately as lazy compilation involves parsing the function twice. You can read V8's blog post about this for more details.
Previously esbuild did not represent parentheses around functions in the AST so they were lost during compilation. With this change, esbuild will now preserve parentheses around function expressions when they are present in the original source code. This means these optimization hints will not be lost when bundling with esbuild. In addition, esbuild will now automatically add this optimization hint to immediately-invoked function expressions. Here's an example:
// Original code const fn0 = () => 0 const fn1 = (() => 1) console.log(fn0, function() { return fn1() }())// Old output
const fn0 = () => 0;
const fn1 = () => 1;
console.log(fn0, function() {
return fn1();
}());// New output
const fn0 = () => 0;
const fn1 = (() => 1);
console.log(fn0, (function() {
return fn1();
})());
Note that you do not want to wrap all function expressions in parentheses. This optimization hint should only be used for functions that are called on initial load. Using this hint for functions that are not called on initial load will unnecessarily delay the initial load. Again, see V8's blog post linked above for details.
Update Go from 1.23.10 to 1.23.12 (#4257, #4258)
This should have no effect on existing code as this version change does not change Go's operating system support. It may remove certain false positive reports (specifically CVE-2025-4674 and CVE-2025-47907) from vulnerability scanners that only detect which version of the Go compiler esbuild uses.
195e05c
publish 0.25.9 to npm3dac33f
fix #3131,
fix #3663:
yarnpnp + windows + D drive0f2c5c8
mock fs now supports multiple volumes on windows100a51e
split out yarnpnp snapshot tests13aace3
remove C: assumption from windows snapshot testsf1f413f
fix #4252:
preserve parentheses around functions1bc8091
fix #4257,
close #4258:
go 1.23.10 => 1.23.12bc52135
move the go compiler version to go.versiona0af5d1
makefile: use ESBUILD_VERSION consistentlySourced from dotenv's changelog.
17.2.3 (2025-09-29)
Changed
- Fixed typescript error definition (#912)
affe113
17.2.3db1ff1f
changelog 🪵7063f16
Merge pull request #913
from motdotla/new-tips0bbe72c
test against expected tips017951b
only run .js tests39eda1f
add space backfcc030e
update tipsb6c7a0d
updated tips - as Dotenvx Radar has been renamed Dotenvx Opsb3c8b16
remove unnecessary call to npxd6e4c17
Merge pull request #912
from adjerbetian/fix/typescript-error-definitionSourced from esbuild's releases.
v0.25.10
Fix a panic in a minification edge case (#4287)
This release fixes a panic due to a null pointer that could happen when esbuild inlines a doubly-nested identity function and the final result is empty. It was fixed by emitting the value
undefinedin this case, which avoids the panic. This case must be rare since it hasn't come up until now. Here is an example of code that previously triggered the panic (which only happened when minifying):function identity(x) { return x } identity({ y: identity(123) })Fix
@supportsnested inside pseudo-element (#4265)When transforming nested CSS to non-nested CSS, esbuild is supposed to filter out pseudo-elements such as
::placeholderfor correctness. The CSS nesting specification says the following:The nesting selector cannot represent pseudo-elements (identical to the behavior of the ':is()' pseudo-class). We’d like to relax this restriction, but need to do so simultaneously for both ':is()' and '&', since they’re intentionally built on the same underlying mechanisms.
However, it seems like this behavior is different for nested at-rules such as
@supports, which do work with pseudo-elements. So this release modifies esbuild's behavior to now take that into account:/* Original code */ ::placeholder { color: red; body & { color: green } @supports (color: blue) { color: blue } }/* Old output (with --supported:nesting=false) */
::placeholder {
color: red;
}
body :is() {
color: green;
}
@supports(color: blue) {
{
color: blue;
}
}/* New output (with --supported:nesting=false) */
::placeholder {
color: red;
}
body :is() {
color: green;
}
@supports(color: blue) {
::placeholder {
color: blue;
}
... (truncated)
Sourced from esbuild's changelog.
0.25.10
Fix a panic in a minification edge case (#4287)
This release fixes a panic due to a null pointer that could happen when esbuild inlines a doubly-nested identity function and the final result is empty. It was fixed by emitting the value
undefinedin this case, which avoids the panic. This case must be rare since it hasn't come up until now. Here is an example of code that previously triggered the panic (which only happened when minifying):function identity(x) { return x } identity({ y: identity(123) })Fix
@supportsnested inside pseudo-element (#4265)When transforming nested CSS to non-nested CSS, esbuild is supposed to filter out pseudo-elements such as
::placeholderfor correctness. The CSS nesting specification says the following:The nesting selector cannot represent pseudo-elements (identical to the behavior of the ':is()' pseudo-class). We’d like to relax this restriction, but need to do so simultaneously for both ':is()' and '&', since they’re intentionally built on the same underlying mechanisms.
However, it seems like this behavior is different for nested at-rules such as
@supports, which do work with pseudo-elements. So this release modifies esbuild's behavior to now take that into account:/* Original code */ ::placeholder { color: red; body & { color: green } @supports (color: blue) { color: blue } }/* Old output (with --supported:nesting=false) */
::placeholder {
color: red;
}
body :is() {
color: green;
}
@supports(color: blue) {
{
color: blue;
}
}/* New output (with --supported:nesting=false) */
::placeholder {
color: red;
}
body :is() {
color: green;
}
@supports(color: blue) {
::placeholder {
color: blue;
... (truncated)
d6b668f
publish 0.25.10 to npm5088c19
refactor: use strings.Builder (#4290)755da31
run make update-compat-tablea1d9c86
fix #4287:
marked the wrong issue as fixed73a0b2a
fix #4286:
minifier panic due to identity function134dadf
fix #4265:
@supports nested inside ::pseudoSourced from js-yaml's changelog.
[3.14.2] - 2025-11-15
Security
- Backported v4.1.1 fix to v3
[4.1.1] - 2025-11-12
Security
- Fix prototype pollution issue in yaml merge (<<) operator.
[4.1.0] - 2021-04-15
Added
- Types are now exported as
yaml.types.XXX.- Every type now has
optionsproperty with original arguments kept as they were (seeyaml.types.int.optionsas an example).Changed
Schema.extend()now keeps old type order in case of conflicts (e.g. Schema.extend([ a, b, c ]).extend([ b, a, d ]) is now ordered asabcdinstead ofcbad).[4.0.0] - 2021-01-03
Changed
- Check migration guide to see details for all breaking changes.
- Breaking: "unsafe" tags
!!js/function,!!js/regexp,!!js/undefinedare moved to js-yaml-js-types package.- Breaking: removed
safe*functions. Useload,loadAll,dumpinstead which are all now safe by default.yaml.DEFAULT_SAFE_SCHEMAandyaml.DEFAULT_FULL_SCHEMAare removed, useyaml.DEFAULT_SCHEMAinstead.yaml.Schema.create(schema, tags)is removed, useschema.extend(tags)instead.!!binarynow always mapped toUint8Arrayon load.- Reduced nesting of
/libfolder.- Parse numbers according to YAML 1.2 instead of YAML 1.1 (
01234is now decimal,0o1234is octal,1:23is parsed as string instead of base60).dump()no longer quotes:,[,],(,)except when necessary, #470, #557.- Line and column in exceptions are now formatted as
(X:Y)instead ofat line X, column Y(also present in compact format), #332.- Code snippet created in exceptions now contains multiple lines with line numbers.
dump()now serializesundefinedasnullin collections and removes keys withundefinedin mappings, #571.dump()withskipInvalid=truenow serializes invalid items in collections as null.- Custom tags starting with
!are now dumped as!taginstead of!<!tag>, #576.- Custom tags starting with
tag:yaml.org,2002:are now shorthanded using!!, #258.Added
... (truncated)
9963d36
3.14.2 released10d3c8e
dist rebuild5278870
fix prototype pollution in merge (<<) (#731)Sourced from actions/setup-node's releases.
v6.0.0
What's Changed
Breaking Changes
- Limit automatic caching to npm, update workflows and documentation by
@priyagupta108in actions/setup-node#1374Dependency Upgrades
- Upgrade ts-jest from 29.1.2 to 29.4.1 and document breaking changes in v5 by
@dependabot[bot] in #1336- Upgrade prettier from 2.8.8 to 3.6.2 by
@dependabot[bot] in #1334- Upgrade actions/publish-action from 0.3.0 to 0.4.0 by
@dependabot[bot] in #1362Full Changelog: https://github.com/actions/setup-node/compare/v5...v6.0.0
v5.0.0
What's Changed
Breaking Changes
- Enhance caching in setup-node with automatic package manager detection by
@priya-kinthaliin actions/setup-node#1348This update, introduces automatic caching when a valid
packageManagerfield is present in yourpackage.json. This aims to improve workflow performance and make dependency management more seamless. To disable this automatic caching, setpackage-manager-cache: falsesteps: - uses: actions/checkout@v5 - uses: actions/setup-node@v5 with: package-manager-cache: false
- Upgrade action to use node24 by
@salmanmkcin actions/setup-node#1325Make sure your runner is on version v2.327.1 or later to ensure compatibility with this release. See Release Notes
Dependency Upgrades
- Upgrade
@octokit/request-errorand@actions/githubby@dependabot[bot] in actions/setup-node#1227- Upgrade uuid from 9.0.1 to 11.1.0 by
@dependabot[bot] in actions/setup-node#1273- Upgrade undici from 5.28.5 to 5.29.0 by
@dependabot[bot] in actions/setup-node#1295- Upgrade form-data to bring in fix for critical vulnerability by
@gowridurgadin actions/setup-node#1332- Upgrade actions/checkout from 4 to 5 by
@dependabot[bot] in actions/setup-node#1345New Contributors
@priya-kinthalimade their first contribution in actions/setup-node#1348@salmanmkcmade their first contribution in actions/setup-node#1325Full Changelog: https://github.com/actions/setup-node/compare/v4...v5.0.0
v4.4.0
... (truncated)
2028fbc
Limit automatic caching to npm, update workflows and documentation (#1374)1342781
Bump actions/publish-action from 0.3.0 to 0.4.0 (#1362)89d709d
Bump prettier from 2.8.8 to 3.6.2 (#1334)cd2651c
Bump ts-jest from 29.1.2 to 29.4.1 (#1336)a0853c2
Bump actions/checkout from 4 to 5 (#1345)b7234cc
Upgrade action to use node24 (#1325)d7a1131
Enhance caching in setup-node with automatic package manager detection
(#1348)5e2628c
Bumps form-data (#1332)65becef
Bump undici from 5.28.5 to 5.29.0 (#1295)7e24a65
Bump uuid from 9.0.1 to 11.1.0 (#1273)Sourced from stefanzweifel/git-auto-commit-action's releases.
v7.0.0
Added
- Restore skip_fetch, skip_checkout, create_branch (#388)
@stefanzweifel- Restore Detached State Detection (#393)
@stefanzweifel- Add Support for Tag Messages (#391)
@EliasBoulhartsChanged
- Run Action on Node 24 (#389)
@stefanzweifelDependency Updates
- Bump actions/checkout from 4 to 5 (#386) [@dependabot[bot]](https://github.com/@[dependabot[bot]](https://github.com/apps/dependabot))
Sourced from stefanzweifel/git-auto-commit-action's changelog.
Changelog
All notable changes to this project will be documented in this file.
The format is based on Keep a Changelog and this project adheres to Semantic Versioning.
Unreleased
TBD
v7.0.0 - 2025-10-12
Added
- Restore skip_fetch, skip_checkout, create_branch (#388)
@stefanzweifel- Restore Detached State Detection (#393)
@stefanzweifel- Add Support for Tag Messages (#391)
@EliasBoulhartsChanged
- Run Action on Node 24 (#389)
@stefanzweifelDependency Updates
- Bump actions/checkout from 4 to 5 (#386) [@dependabot[bot]](https://github.com/@[dependabot[bot]](https://github.com/apps/dependabot))
v6.0.1 - 2025-06-11
Fixed
- Disable Check if Repo is in Detached State (#379)
@stefanzweifelv6.0.0 - 2025-06-10
Added
- Throw error early if repository is in a detached state (#357)
Fixed
- Fix PAT instructions with Dependabot (#376)
@DreamsorcererRemoved
- Remove support for
create_branch,skip_checkout,skip_Fetch(#314)v5.2.0 - 2025-04-19
Added
... (truncated)
28e16e8
Release preparations for v7 (#394)698fd76
Merge pull request #391
from EliasBoulharts/custom-tag-messagec40819a
Update READMEd7ee275
Change internal variable namese8684eb
Fix Tests1949701
Merge branch 'master' into pr/391a88dc49
Merge pull request #388
from stefanzweifel/v7-nexta531dec
Merge pull request #386
from stefanzweifel/dependabot/github_actions/actions/...acbe8b1
Merge pull request #393
from stefanzweifel/v7-warn-detached-headd185485
Enable Detached State CheckSourced from actions/checkout's releases.
v6.0.0
What's Changed
- Update README to include Node.js 24 support details and requirements by
@salmanmkcin actions/checkout#2248- Persist creds to a separate file by
@ericsciplein actions/checkout#2286- v6-beta by
@ericsciplein actions/checkout#2298- update readme/changelog for v6 by
@ericsciplein actions/checkout#2311Full Changelog: https://github.com/actions/checkout/compare/v5.0.0...v6.0.0
v6-beta
What's Changed
Updated persist-credentials to store the credentials under
$RUNNER_TEMPinstead of directly in the local git config.This requires a minimum Actions Runner version of v2.329.0 to access the persisted credentials for Docker container action scenarios.
v5.0.1
What's Changed
- Port v6 cleanup to v5 by
@ericsciplein actions/checkout#2301Full Changelog: https://github.com/actions/checkout/compare/v5...v5.0.1
Sourced from actions/checkout's changelog.
Changelog
V6.0.0
- Persist creds to a separate file by
@ericsciplein actions/checkout#2286- Update README to include Node.js 24 support details and requirements by
@salmanmkcin actions/checkout#2248V5.0.1
- Port v6 cleanup to v5 by
@ericsciplein actions/checkout#2301V5.0.0
- Update actions checkout to use node 24 by
@salmanmkcin actions/checkout#2226V4.3.1
- Port v6 cleanup to v4 by
@ericsciplein actions/checkout#2305V4.3.0
- docs: update README.md by
@motssin actions/checkout#1971- Add internal repos for checking out multiple repositories by
@mouismailin actions/checkout#1977- Documentation update - add recommended permissions to Readme by
@benwellsin actions/checkout#2043- Adjust positioning of user email note and permissions heading by
@joshmgrossin actions/checkout#2044- Update README.md by
@nebuk89in actions/checkout#2194- Update CODEOWNERS for actions by
@TingluoHuangin actions/checkout#2224- Update package dependencies by
@salmanmkcin actions/checkout#2236v4.2.2
url-helper.tsnow leverages well-known environment variables by@jww3in actions/checkout#1941- Expand unit test coverage for
isGhesby@jww3in actions/checkout#1946v4.2.1
- Check out other refs/* by commit if provided, fall back to ref by
@orhantoyin actions/checkout#1924v4.2.0
- Add Ref and Commit outputs by
@lucacomein actions/checkout#1180- Dependency updates by
@dependabot- actions/checkout#1777, actions/checkout#1872v4.1.7
- Bump the minor-npm-dependencies group across 1 directory with 4 updates by
@dependabotin actions/checkout#1739- Bump actions/checkout from 3 to 4 by
@dependabotin actions/checkout#1697- Check out other refs/* by commit by
@orhantoyin actions/checkout#1774- Pin actions/checkout's own workflows to a known, good, stable version. by
@jww3in actions/checkout#1776v4.1.6
- Check platform to set archive extension appropriately by
@cory-millerin actions/checkout#1732v4.1.5
- Update NPM dependencies by
@cory-millerin actions/checkout#1703- Bump github/codeql-action from 2 to 3 by
@dependabotin actions/checkout#1694- Bump actions/setup-node from 1 to 4 by
@dependabotin actions/checkout#1696- Bump actions/upload-artifact from 2 to 4 by
@dependabotin actions/checkout#1695
... (truncated)
Sourced from @octokit/request's
releases.
v10.0.5
10.0.5 (2025-09-29)
Bug Fixes
v10.0.4
10.0.4 (2025-09-29)
Bug Fixes
30f83b6
fix(deps): update octokit deps (#772)b07d593
ci(action): update actions/checkout action to v5 (#770)928c3d7
chore(deps): update dependency prettier to v3.6.2 (#766)a84613e
ci(action): update actions/setup-node action to v5 (#771)ad78b4c
fix(deps): update dependency @octokit/types to v15 (#775)Sourced from @octokit/openapi's
releases.
v20.0.0
20.0.0 (2025-09-16)
chore
Features
- new Projects v2 endpoints, new code scanning dismissal endpoints, many other endpoints (#503) (0b92729)
BREAKING CHANGES
- deps: Remove GHES 3.13
262f87f
chore(deps): update dependency sort-keys to v6 (#500)0b92729
feat: new Projects v2 endpoints, new code scanning dismissal endpoints,
many ...a74dd44
chore(deps): update dependency @octokit/core to v7 (#496)3a7a9ea
build(deps): lock file maintenance (#498)d6be26f
ci(action): update actions/checkout action to v5 (#499)6ae358e
ci(action): update actions/setup-node action to v5 (#502)f02c5e2
ci(action): update gr2m/release-notifier-action action to v2 (#501)56774ef
10.5.01e4e297
bin: Do not expose filenames to shell expansionSourced from p-retry's releases.
v7.0.0
Breaking
- Require Node.js 20 3bdb53a
onFailedAttemptandshouldRetrynow receive acontextobject instead of a decoratederrorbff36bb
- You must now must access the error as
object.errorinstead ofobject.- The use of
.attemptNumberand.retriesLeftdid not change.- Remove the
foreveroption (#79) 6a89827
- Many use-cases can use
{retries: Infinity}instead for infinite retries.Improvements
- Rewrite the package to not depend on the
retrypackage (#79) 6a89827
- This is a full rewrite, so test carefully.
- Add
makeRetriablemethod 1a81c1e
https://github.com/sindresorhus/p-retry/compare/v6.2.1...v7.0.0
v7.0.0-0
Breaking
- Require Node.js 20 3bdb53a
onFailedAttemptandshouldRetrynow receive acontextobject instead of a decoratederrorbff36bb
- You must now must access the error as
object.errorinstead ofobject.- The use of
.attemptNumberand.retriesLeftdid not change.- Remove the
foreveroption (#79) 6a89827
- Many use-cases can use
{retries: Infinity}instead for infinite retries.Improvements
- Rewrite the package to not depend on the
retrypackage (#79) 6a89827
- This is a full rewrite, so test carefully.
- Add
makeRetriablemethod 1a81c1e
https://github.com/sindresorhus/p-retry/compare/v6.2.1...v7.0.0-0
e11ca9c
7.0.081608ce
Minor tweaks9ef6a73
Clarify shouldRetry documentation (#93)e05b101
Fix code example typo (#91)157d06e
7.0.0-0bff36bb
Stop decorating errors1a81c1e
Add makeRetriable method4811051
Document mocking777d98f
Document signal handlingb4e52fc
Add test for async stack traces016958a
fix(deps): update dependency @octokit/types to v16 (#731)6290a83
ci(action): update peter-evans/create-or-update-comment action to v5 (#723)767ba94
ci(action): update actions/setup-node action to v6 (#727)a6b03f2
ci(action): update github/codeql-action action to v4 (#726)f6eb9c8
chore(deps): update dependency node to v24 (#730)f50e21a
ci(action): update actions/setup-node action to v5 (#718)7f24cee
build(deps): lock file maintenance (#719)Sourced from @octokit/request's
releases.
v10.0.7
10.0.7 (2025-11-13)
Bug Fixes
v10.0.6
10.0.6 (2025-10-30)
Bug Fixes
f17c1c1
fix(readme): properly structure the options for custom agent (#786)ea46fa9
ci(action): update github/codeql-action action to v4 (#778)8166d28
chore(deps): update vitest monorepo to v4 (major) (#781)1aeac56
fix(deps): update dependency @octokit/types to v16 (#783)b5b08a2
ci(action): update actions/setup-node action to v6 (#779)9a78123
chore(deps): update dependency @types/node to v24 (#782)