summaryrefslogtreecommitdiffstatshomepage
path: root/package.json (follow)
Commit message (Collapse)AuthorAge
* v5.0.4HEADv5.0.4v5.0v5masterEgor Tensin10 days
|
* v5.0.3Egor Tensin2026-10-11
|
* update my emailEgor Tensin2026-04-07
|
* forgot to update the version in package.jsonEgor Tensin2026-04-07
| | | | Solid release practices, amirite
* fix Node warningsv5.0.1Egor Tensin2026-03-14
|
* upgrade actions/core to version 3v4.0.3v4Egor Tensin2026-02-28
| | | | | | | | The relevant changes are in clean.js/restore.js. I'm very, very far away from the entire Javascript infrastructure, and absolutely don't understand why this changes were necessary. Thanks, ChatGPT! Supposedly, this has something to do with the actions/core's transition to ESM or whatever.
* upgrade actions/core to version 2Egor Tensin2026-02-28
|
* v4.0.2v4.0.2Egor Tensin2025-12-16
|
* bump dependenciesEgor Tensin2025-12-16
|
* bump version in package.json, upgrade dependenciesEgor Tensin2024-01-28
|
* v3v3Egor Tensin2022-12-11
|
* upgrade actions/coreEgor Tensin2022-12-11
|
* make it into a JavaScript actionEgor Tensin2021-03-14
This is a huge step back IMO, but I needed to be able to restore the original PATH back as a "post" step. Currently, composite actions don't support post-actions, but JavaScript ones do. I needed this due to a bug: actions/cache wouldn't find Git's tar on windows-2016 (the one in System32 would get used on windows-2019) if the PATH was cleaned up.