aboutsummaryrefslogtreecommitdiffstatshomepage
Commit message (Collapse)AuthorAge
* fix Node warningsv5.0.1Egor Tensin2026-03-14
|
* wait, what the hell? doesn't Dependabot update node_modules as well?Egor Tensin2026-03-14
|
* Merge pull request #8 from egor-tensin/dependabot/npm_and_yarn/undici-6.24.1Egor Tensin2026-03-14
|\ | | | | Bump undici from 6.23.0 to 6.24.1
| * Bump undici from 6.23.0 to 6.24.1dependabot[bot]2026-03-14
|/ | | | | | | | | | | | | | Bumps [undici](https://github.com/nodejs/undici) from 6.23.0 to 6.24.1. - [Release notes](https://github.com/nodejs/undici/releases) - [Commits](https://github.com/nodejs/undici/compare/v6.23.0...v6.24.1) --- updated-dependencies: - dependency-name: undici dependency-version: 6.24.1 dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
* README: updateEgor Tensin2026-03-12
|
* move to Node 24v5.0.0Egor Tensin2026-03-12
|
* workflows/test: remove on: pull_requestEgor Tensin2026-03-01
| | | | Why do I even need this? on: push covers everything I need
* 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
|
* DEVELOPMENT.md: expand on sourcesEgor Tensin2026-02-28
|
* workflows/test: remove Windows 2019Egor Tensin2026-02-28
| | | | Doesn't seem to be supported anymore.
* add DEVELOPMENT.mdEgor Tensin2026-02-28
|
* add dependabot.ymlEgor Tensin2026-01-11
|
* v4.0.2v4.0.2Egor Tensin2025-12-16
|
* bump dependenciesEgor Tensin2025-12-16
|
* bump dependenciesEgor Tensin2025-12-16
|
* workflows/test: upgrade actionsEgor Tensin2025-12-16
|
* workflows/test: update runner imagesEgor Tensin2025-12-16
|
* README: updatev4.0.1Egor Tensin2024-01-28
| | | | | I completely forgot that I'm supposed to bump the version in package.json & the README.
* bump version in package.json, upgrade dependenciesEgor Tensin2024-01-28
|
* workflows/test: upgrade actionsv4.0.0Egor Tensin2024-01-28
|
* Merge pull request #2 from radarhere/masterEgor Tensin2024-01-28
|\ | | | | Updated to Node 20
| * Updated to Node 20Andrew Murray2024-01-27
|/
* v3v3Egor Tensin2022-12-11
|
* upgrade actions/coreEgor Tensin2022-12-11
|
* bump Node versionEgor Tensin2022-12-11
|
* workflows/test: run on new Windows runnersEgor Tensin2022-12-11
|
* workflows/test: upgrade actionsEgor Tensin2022-12-11
|
* make .gitattributes more consistentEgor Tensin2022-12-11
|
* workflows/test: include windows-latestEgor Tensin2021-06-15
|
* README: updateEgor Tensin2021-04-18
|
* README: updateEgor Tensin2021-04-18
|
* README: updateEgor Tensin2021-04-18
|
* README: fix badge linkEgor Tensin2021-04-17
|
* README: updatev2Egor Tensin2021-03-14
|
* add node_modules/Egor Tensin2021-03-14
|
* 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.
* add .gitattributesEgor Tensin2020-12-25
|
* rename the actionv1Egor Tensin2020-12-24
|
* add READMEEgor Tensin2020-12-24
|
* initial commitEgor Tensin2020-12-24