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
Bump the version to v1.17.0 in package.json, the README examples, and
the setup-ref / setupRef defaults in the GitLab and Azure templates.
Changes since v1.16.1:
- feat: support disabling Vite+'s Node.js management with node-manager:
false (#115)
- fix: retry sfw vp install when sfw misreports vp as not found on
Windows (#120)
- chore(deps): update vite-plus to v0.2.8 (#119)
- ci: re-run bundle rebuild when Renovate pushes to a labeled PR (#122)
- chore: align Renovate release age for the whole vite-plus group (#121)
After merge, tag the merge commit as v1.17.0 and push the tag.
Copy file name to clipboardExpand all lines: README.md
+38-38Lines changed: 38 additions & 38 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -18,7 +18,7 @@ GitHub Action, GitLab CI/CD remote template, and Azure Pipelines step template t
18
18
Reference this action with an exact release tag, or a commit SHA:
19
19
20
20
```yaml
21
-
- uses: voidzero-dev/setup-vp@v1.16.1
21
+
- uses: voidzero-dev/setup-vp@v1.17.0
22
22
```
23
23
24
24
Releases are listed on the [tags page](https://github.com/voidzero-dev/setup-vp/tags). [Renovate](https://docs.renovatebot.com/) and Dependabot can keep a pinned tag up to date.
@@ -33,15 +33,15 @@ Releases are listed on the [tags page](https://github.com/voidzero-dev/setup-vp/
33
33
```yaml
34
34
steps:
35
35
- uses: actions/checkout@v6
36
-
- uses: voidzero-dev/setup-vp@v1.16.1
36
+
- uses: voidzero-dev/setup-vp@v1.17.0
37
37
```
38
38
39
39
### With Node.js Version
40
40
41
41
```yaml
42
42
steps:
43
43
- uses: actions/checkout@v6
44
-
- uses: voidzero-dev/setup-vp@v1.16.1
44
+
- uses: voidzero-dev/setup-vp@v1.17.0
45
45
with:
46
46
node-version: "lts"
47
47
```
@@ -51,7 +51,7 @@ steps:
51
51
```yaml
52
52
steps:
53
53
- uses: actions/checkout@v6
54
-
- uses: voidzero-dev/setup-vp@v1.16.1
54
+
- uses: voidzero-dev/setup-vp@v1.17.0
55
55
with:
56
56
node-version-file: ".node-version"
57
57
```
@@ -68,7 +68,7 @@ steps:
68
68
- uses: actions/setup-node@v5
69
69
with:
70
70
node-version: 24
71
-
- uses: voidzero-dev/setup-vp@v1.16.1
71
+
- uses: voidzero-dev/setup-vp@v1.17.0
72
72
with:
73
73
node-manager: false
74
74
```
@@ -78,7 +78,7 @@ steps:
78
78
```yaml
79
79
steps:
80
80
- uses: actions/checkout@v6
81
-
- uses: voidzero-dev/setup-vp@v1.16.1
81
+
- uses: voidzero-dev/setup-vp@v1.17.0
82
82
with:
83
83
working-directory: web
84
84
node-version-file: ".nvmrc"
@@ -91,7 +91,7 @@ steps:
91
91
```yaml
92
92
steps:
93
93
- uses: actions/checkout@v6
94
-
- uses: voidzero-dev/setup-vp@v1.16.1
94
+
- uses: voidzero-dev/setup-vp@v1.17.0
95
95
with:
96
96
node-version: "lts"
97
97
cache: true
@@ -103,7 +103,7 @@ steps:
103
103
```yaml
104
104
steps:
105
105
- uses: actions/checkout@v6
106
-
- uses: voidzero-dev/setup-vp@v1.16.1
106
+
- uses: voidzero-dev/setup-vp@v1.17.0
107
107
with:
108
108
version: "1.2.3"
109
109
node-version: "lts"
@@ -127,7 +127,7 @@ to `latest` only when nothing pins a resolvable version. So a project that pins
127
127
```yaml
128
128
steps:
129
129
- uses: actions/checkout@v6
130
-
- uses: voidzero-dev/setup-vp@v1.16.1
130
+
- uses: voidzero-dev/setup-vp@v1.17.0
131
131
with:
132
132
cache: true
133
133
```
@@ -140,7 +140,7 @@ worth watching for, since it means the pinned version was not applied:
140
140
```yaml
141
141
steps:
142
142
- uses: actions/checkout@v6
143
-
- uses: voidzero-dev/setup-vp@v1.16.1
143
+
- uses: voidzero-dev/setup-vp@v1.17.0
144
144
with:
145
145
version-file: package.json
146
146
cache: true
@@ -200,7 +200,7 @@ action warns and falls back to `latest`. (Auto-detection instead resolves a
200
200
```yaml
201
201
steps:
202
202
- uses: actions/checkout@v6
203
-
- uses: voidzero-dev/setup-vp@v1.16.1
203
+
- uses: voidzero-dev/setup-vp@v1.17.0
204
204
with:
205
205
node-version: "lts"
206
206
cache: true
@@ -225,7 +225,7 @@ minimal:
225
225
226
226
steps:
227
227
- uses: actions/checkout@v6
228
-
- uses: voidzero-dev/setup-vp@v1.16.1
228
+
- uses: voidzero-dev/setup-vp@v1.17.0
229
229
with:
230
230
node-version: "lts"
231
231
env:
@@ -242,7 +242,7 @@ read the repo `.npmrc` per its own config resolution):
242
242
```yaml
243
243
steps:
244
244
- uses: actions/checkout@v6
245
-
- uses: voidzero-dev/setup-vp@v1.16.1
245
+
- uses: voidzero-dev/setup-vp@v1.17.0
246
246
with:
247
247
node-version: "lts"
248
248
registry-url: "https://npm.pkg.github.com"
@@ -260,7 +260,7 @@ Set `sfw: true` to wrap `vp install` with [Socket Firewall Free](https://docs.so
| `node-manager` | String input: `"false"`keeps the runner image's Node.js (skips shims and runs `vp env off`); `"true"` force-enables the managed Node.js; empty lets the installer decide (enabled on CI) | |
508
508
| `registry-url` | Optional registry URL to write to a temporary `.npmrc` | |
509
509
| `scope` | Optional scope for authenticating against scoped registries | |
510
-
| `setup-ref` | setup-vp ref used to download the GitLab bootstrap and compiled runtime. Always set it to the same tag as the remote URL; the default is the latest release when the template was published | `v1.16.1` |
510
+
| `setup-ref` | setup-vp ref used to download the GitLab bootstrap and compiled runtime. Always set it to the same tag as the remote URL; the default is the latest release when the template was published | `v1.17.0` |
511
511
512
512
### GitLab Notes
513
513
514
-
- Use an exact release tag such as `v1.16.1` in the remote URL. Do not use `main` (mutable) or `v1` (frozen at v1.15.0, no longer updated).
514
+
- Use an exact release tag such as `v1.17.0` in the remote URL. Do not use `main` (mutable) or `v1` (frozen at v1.15.0, no longer updated).
515
515
- Always pin `setup-ref` to the same tag or commit SHA as the remote URL, so the compiled runtime matches the included template.
516
516
- Quote GitLab string inputs such as `run-install: "false"`; unquoted booleans are rejected by GitLab before the setup runtime can parse them.
517
517
- GitLab 17.9+ users can add `integrity` to pin the remote file hash.
@@ -537,7 +537,7 @@ resources:
537
537
type: github
538
538
endpoint: github
539
539
name: voidzero-dev/setup-vp
540
-
ref: refs/tags/v1.16.1
540
+
ref: refs/tags/v1.17.0
541
541
542
542
pool:
543
543
vmImage: ubuntu-latest
@@ -547,7 +547,7 @@ steps:
547
547
548
548
- template: azure/setup-vp.yml@setupVp
549
549
parameters:
550
-
setupRef: v1.16.1
550
+
setupRef: v1.17.0
551
551
nodeVersion: 24.x
552
552
cache: true
553
553
runInstall: true
@@ -567,7 +567,7 @@ Pin `ref` and `setupRef` to the same exact tag or commit SHA. Do not use the `v1
| `registryUrl` | | Optional registry URL for a temporary `.npmrc`. |
569
569
| `scope` | | Optional npm registry scope. |
570
-
| `setupRef` | `v1.16.1` | Ref used to download bootstrap scripts and `dist/azure/index.mjs`. Always set it to the same tag as `ref`; the default is the latest release when the template was published. |
570
+
| `setupRef` | `v1.17.0` | Ref used to download bootstrap scripts and `dist/azure/index.mjs`. Always set it to the same tag as `ref`; the default is the latest release when the template was published. |
571
571
| `nodeVersion` | `24.x` | Passed to `UseNode@1`; an empty string skips Node setup. |
572
572
| `nodeManager` | | Control Vite+'s Node.js manager: `false`keeps the agent's Node.js (e.g. from `UseNode@1`); `true` force-enables the managed one; empty lets the installer decide. |
573
573
| `cache` | `false` | Enable Azure `Cache@2` around the package-manager cache directory. |
@@ -606,7 +606,7 @@ jobs:
606
606
steps:
607
607
- uses: actions/checkout@v6
608
608
609
-
- uses: voidzero-dev/setup-vp@v1.16.1
609
+
- uses: voidzero-dev/setup-vp@v1.17.0
610
610
with:
611
611
node-version: "lts"
612
612
cache: true
@@ -650,7 +650,7 @@ vp install
650
650
651
651
### Releasing
652
652
653
-
Releases are published as git tags; there is no npm package, but the `package.json` version tracks the latest release. Consumers pin an exact version tag such as `voidzero-dev/setup-vp@v1.16.1` or a commit SHA. The `v1` major tag is frozen at v1.15.0 and is never moved (an org-level ruleset rejects tag force-pushes).
653
+
Releases are published as git tags; there is no npm package, but the `package.json` version tracks the latest release. Consumers pin an exact version tag such as `voidzero-dev/setup-vp@v1.17.0` or a commit SHA. The `v1` major tag is frozen at v1.15.0 and is never moved (an org-level ruleset rejects tag force-pushes).
654
654
655
655
To cut a release:
656
656
@@ -667,8 +667,8 @@ To cut a release:
667
667
3. Create the new annotated version tag and push it. For example:
Copy file name to clipboardExpand all lines: gitlab/setup-vp.yml
+2-2Lines changed: 2 additions & 2 deletions
Original file line number
Diff line number
Diff line change
@@ -24,7 +24,7 @@ spec:
24
24
default: ""
25
25
setup-ref:
26
26
description: "setup-vp ref used to download the GitLab bootstrap and compiled runtime. Pin this to the same tag or commit as the remote template; the default is the latest release when this template was published."
0 commit comments