You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+2-2Lines changed: 2 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -14,7 +14,7 @@ GitHub Actions workflows may query the GitHub API and consume rate limits, but t
14
14
## Quick Start
15
15
16
16
```yaml
17
-
- uses: hesreallyhim/github-api-usage-monitor@v1
17
+
- uses: hesreallyhim/github-api-usage-monitor@v2
18
18
```
19
19
20
20
That's it. Insert that anywhere in your workflow job. The action uses the pre/post hook lifecycle — it starts monitoring automatically before your first step and reports after your last step. No `start`/`stop` steps needed.
@@ -53,7 +53,7 @@ jobs:
53
53
usage-tracker:
54
54
runs-on: ubuntu-latest
55
55
steps:
56
-
- uses: hesreallyhim/github-api-usage-monitor@v1
56
+
- uses: hesreallyhim/github-api-usage-monitor@v2
57
57
with:
58
58
diagnostics: true
59
59
# ... The rest of your workflow - calls to GitHub API
Copy file name to clipboardExpand all lines: docs/VERSIONING.md
+16-15Lines changed: 16 additions & 15 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -7,21 +7,22 @@ This document defines the supported runtime contract, dependency constraints, an
7
7
8
8
## 1. Node.js support contract
9
9
10
-
- Supported Node.js versions: **>= 20**
11
-
- Action runtime: `runs.using: node20`
12
-
- Development and CI target: **Node 20.x**
10
+
- Supported Node.js versions: **>= 24**
11
+
- Action runtime: `runs.using: node24`
12
+
- Development and CI target: **Node 24.x**
13
13
14
14
**Rationale**
15
-
- GitHub-hosted runners execute `node20`, which floats across the 20.x line.
15
+
- GitHub-hosted runners execute `node24`, which floats across the 24.x line.
16
16
- We support a major version contract, not a specific patch.
17
+
- A JavaScript action runtime major bump (for example `node20` to `node24`) is treated as a breaking change for release purposes because older GHES or self-hosted environments may not support the newer runtime.
17
18
- Patch-level guarantees are neither tested nor enforced and are therefore not claimed.
18
19
19
20
**Configuration**
20
21
```json
21
22
// package.json
22
23
{
23
24
"engines": {
24
-
"node": ">=20"
25
+
"node": ">=24"
25
26
}
26
27
}
27
28
```
@@ -33,21 +34,21 @@ This document defines the supported runtime contract, dependency constraints, an
33
34
This repository includes both `.nvmrc` and `.node-version` to support multiple Node version managers and tooling ecosystems.
34
35
35
36
- Canonical source: `.nvmrc`
36
-
- Accepted value: major only (e.g. `20`)
37
+
- Accepted value: major only (e.g. `24`)
37
38
- Policy: both files must match exactly
38
39
39
40
```
40
41
.nvmrc
41
-
20
42
+
24
42
43
43
44
.node-version
44
-
20
45
+
24
45
46
```
46
47
47
48
**Rationale**
48
49
-`nvm` consumes `.nvmrc`.
49
50
- Other tooling (asdf, mise, editors, some CI systems) consumes `.node-version`.
50
-
- Using the major only aligns with the project’s Node support contract (`>=20` / `20.x`).
51
+
- Using the major only aligns with the project’s Node support contract (`>=24` / `24.x`).
51
52
- Keeping both files synchronized prevents environment drift across tools.
0 commit comments