Skip to content

Commit 9fd26ff

Browse files
fengmk2fengmk2
authored
chore: release v1.20.0 (#151)
Set `package.json` to `1.20.0`. Update the README examples and the GitLab and Azure template defaults to `v1.20.0`. This release adds `package-manager` for GitHub and GitLab, and `packageManager` for Azure. These inputs control package managers separately from Node.js. The `node-manager: false` setting preserves package-manager management on Vite+ `0.3.1` and later.
1 parent a28dce9 commit 9fd26ff

5 files changed

Lines changed: 46 additions & 46 deletions

File tree

‎README.md‎

Lines changed: 41 additions & 41 deletions
Original file line numberDiff line numberDiff line change
@@ -18,7 +18,7 @@ GitHub Action, GitLab CI/CD remote template, and Azure Pipelines step template t
1818
Reference this action with an exact release tag, or a commit SHA:
1919

2020
```yaml
21-
- uses: voidzero-dev/setup-vp@v1.19.0
21+
- uses: voidzero-dev/setup-vp@v1.20.0
2222
```
2323
2424
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/
3333
```yaml
3434
steps:
3535
- uses: actions/checkout@v7
36-
- uses: voidzero-dev/setup-vp@v1.19.0
36+
- uses: voidzero-dev/setup-vp@v1.20.0
3737
```
3838

3939
### With Node.js Version
4040

4141
```yaml
4242
steps:
4343
- uses: actions/checkout@v7
44-
- uses: voidzero-dev/setup-vp@v1.19.0
44+
- uses: voidzero-dev/setup-vp@v1.20.0
4545
with:
4646
node-version: "lts"
4747
```
@@ -51,7 +51,7 @@ steps:
5151
```yaml
5252
steps:
5353
- uses: actions/checkout@v7
54-
- uses: voidzero-dev/setup-vp@v1.19.0
54+
- uses: voidzero-dev/setup-vp@v1.20.0
5555
with:
5656
node-version-file: ".node-version"
5757
```
@@ -68,7 +68,7 @@ steps:
6868
- uses: actions/setup-node@v5
6969
with:
7070
node-version: 24
71-
- uses: voidzero-dev/setup-vp@v1.19.0
71+
- uses: voidzero-dev/setup-vp@v1.20.0
7272
with:
7373
node-manager: false
7474
```
@@ -78,7 +78,7 @@ steps:
7878
```yaml
7979
steps:
8080
- uses: actions/checkout@v7
81-
- uses: voidzero-dev/setup-vp@v1.19.0
81+
- uses: voidzero-dev/setup-vp@v1.20.0
8282
with:
8383
working-directory: web
8484
node-version-file: ".nvmrc"
@@ -91,7 +91,7 @@ steps:
9191
```yaml
9292
steps:
9393
- uses: actions/checkout@v7
94-
- uses: voidzero-dev/setup-vp@v1.19.0
94+
- uses: voidzero-dev/setup-vp@v1.20.0
9595
with:
9696
node-version: "lts"
9797
cache: true
@@ -103,7 +103,7 @@ steps:
103103
```yaml
104104
steps:
105105
- uses: actions/checkout@v7
106-
- uses: voidzero-dev/setup-vp@v1.19.0
106+
- uses: voidzero-dev/setup-vp@v1.20.0
107107
with:
108108
version: "1.2.3"
109109
node-version: "lts"
@@ -119,7 +119,7 @@ If your project uses an older Vite+ version, upgrade Vite+ to v0.3.1 or later.
119119
```yaml
120120
steps:
121121
- uses: actions/checkout@v7
122-
- uses: voidzero-dev/setup-vp@v1.19.0
122+
- uses: voidzero-dev/setup-vp@v1.20.0
123123
- run: pnpm --version
124124
```
125125

@@ -140,7 +140,7 @@ to `latest` only when nothing pins a resolvable version. So a project that pins
140140
```yaml
141141
steps:
142142
- uses: actions/checkout@v7
143-
- uses: voidzero-dev/setup-vp@v1.19.0
143+
- uses: voidzero-dev/setup-vp@v1.20.0
144144
with:
145145
cache: true
146146
```
@@ -153,7 +153,7 @@ worth watching for, since it means the pinned version was not applied:
153153
```yaml
154154
steps:
155155
- uses: actions/checkout@v7
156-
- uses: voidzero-dev/setup-vp@v1.19.0
156+
- uses: voidzero-dev/setup-vp@v1.20.0
157157
with:
158158
version-file: package.json
159159
cache: true
@@ -213,7 +213,7 @@ action warns and falls back to `latest`. (Auto-detection instead resolves a
213213
```yaml
214214
steps:
215215
- uses: actions/checkout@v7
216-
- uses: voidzero-dev/setup-vp@v1.19.0
216+
- uses: voidzero-dev/setup-vp@v1.20.0
217217
with:
218218
node-version: "lts"
219219
cache: true
@@ -238,7 +238,7 @@ minimal:
238238
239239
steps:
240240
- uses: actions/checkout@v7
241-
- uses: voidzero-dev/setup-vp@v1.19.0
241+
- uses: voidzero-dev/setup-vp@v1.20.0
242242
with:
243243
node-version: "lts"
244244
env:
@@ -255,7 +255,7 @@ read the repo `.npmrc` per its own config resolution):
255255
```yaml
256256
steps:
257257
- uses: actions/checkout@v7
258-
- uses: voidzero-dev/setup-vp@v1.19.0
258+
- uses: voidzero-dev/setup-vp@v1.20.0
259259
with:
260260
node-version: "lts"
261261
registry-url: "https://npm.pkg.github.com"
@@ -273,7 +273,7 @@ Set `sfw: true` to wrap `vp install` with [Socket Firewall Free](https://docs.so
273273
```yaml
274274
steps:
275275
- uses: actions/checkout@v7
276-
- uses: voidzero-dev/setup-vp@v1.19.0
276+
- uses: voidzero-dev/setup-vp@v1.20.0
277277
with:
278278
sfw: true
279279
run-install: true
@@ -294,7 +294,7 @@ steps:
294294
- uses: socketdev/action@<sha>
295295
with:
296296
mode: firewall-free
297-
- uses: voidzero-dev/setup-vp@v1.19.0
297+
- uses: voidzero-dev/setup-vp@v1.20.0
298298
with:
299299
sfw: true
300300
run-install: true
@@ -318,7 +318,7 @@ jobs:
318318
steps:
319319
- run: apk add --no-cache bash curl gcompat libstdc++
320320
- uses: actions/checkout@v7
321-
- uses: voidzero-dev/setup-vp@v1.19.0
321+
- uses: voidzero-dev/setup-vp@v1.20.0
322322
```
323323

324324
### Matrix Testing with Multiple Node.js Versions
@@ -332,7 +332,7 @@ jobs:
332332
runs-on: ubuntu-latest
333333
steps:
334334
- uses: actions/checkout@v7
335-
- uses: voidzero-dev/setup-vp@v1.19.0
335+
- uses: voidzero-dev/setup-vp@v1.20.0
336336
with:
337337
node-version: ${{ matrix.node-version }}
338338
cache: true
@@ -369,7 +369,7 @@ Omitting both `node-version` and `node-version-file` leaves the session without
369369
`package-manager` controls Vite+'s package-manager management independently of `node-manager`. When omitted, it leaves the installer default unchanged (enabled on CI) and runs no environment-mode commands. Set it to `false` to run `vp env off pm` and prefer system package managers, or provide a mapping:
370370

371371
```yaml
372-
- uses: voidzero-dev/setup-vp@v1.19.0
372+
- uses: voidzero-dev/setup-vp@v1.20.0
373373
with:
374374
node-manager: false
375375
package-manager: |
@@ -421,7 +421,7 @@ Set `cache-save: false` to restore an existing dependency cache without writing
421421
For example, this workflow restores caches on every run but saves them only from the `main` branch:
422422

423423
```yaml
424-
- uses: voidzero-dev/setup-vp@v1.19.0
424+
- uses: voidzero-dev/setup-vp@v1.20.0
425425
with:
426426
cache: true
427427
cache-save: ${{ github.event_name == 'push' && github.ref == 'refs/heads/main' }}
@@ -443,9 +443,9 @@ Use an exact release tag in the `include:remote` URL, and pin `setup-ref` to the
443443

444444
```yaml
445445
include:
446-
- remote: "https://raw.githubusercontent.com/voidzero-dev/setup-vp/v1.19.0/gitlab/setup-vp.yml"
446+
- remote: "https://raw.githubusercontent.com/voidzero-dev/setup-vp/v1.20.0/gitlab/setup-vp.yml"
447447
inputs:
448-
setup-ref: "v1.19.0"
448+
setup-ref: "v1.20.0"
449449
450450
test:
451451
extends: .setup-vp
@@ -458,9 +458,9 @@ test:
458458

459459
```yaml
460460
include:
461-
- remote: "https://raw.githubusercontent.com/voidzero-dev/setup-vp/v1.19.0/gitlab/setup-vp.yml"
461+
- remote: "https://raw.githubusercontent.com/voidzero-dev/setup-vp/v1.20.0/gitlab/setup-vp.yml"
462462
inputs:
463-
setup-ref: "v1.19.0"
463+
setup-ref: "v1.20.0"
464464
version: "latest"
465465
working-directory: "web"
466466
run-install: "true"
@@ -478,14 +478,14 @@ GitLab replaces array keywords such as `before_script` when a job uses `extends`
478478

479479
```yaml
480480
include:
481-
- remote: "https://raw.githubusercontent.com/voidzero-dev/setup-vp/v1.19.0/gitlab/setup-vp.yml"
481+
- remote: "https://raw.githubusercontent.com/voidzero-dev/setup-vp/v1.20.0/gitlab/setup-vp.yml"
482482
483483
test:
484484
image: node:24
485485
variables:
486486
SETUP_VP_VERSION: "latest"
487487
SETUP_VP_RUN_INSTALL: "true"
488-
SETUP_VP_SETUP_REF: "v1.19.0"
488+
SETUP_VP_SETUP_REF: "v1.20.0"
489489
before_script:
490490
- !reference [.setup-vp-bootstrap, before_script]
491491
- npm config set //registry.example.com/:_authToken "$NODE_AUTH_TOKEN"
@@ -500,9 +500,9 @@ Use the same pattern when the project has `default:before_script`; put the share
500500

501501
```yaml
502502
include:
503-
- remote: "https://raw.githubusercontent.com/voidzero-dev/setup-vp/v1.19.0/gitlab/setup-vp.yml"
503+
- remote: "https://raw.githubusercontent.com/voidzero-dev/setup-vp/v1.20.0/gitlab/setup-vp.yml"
504504
inputs:
505-
setup-ref: "v1.19.0"
505+
setup-ref: "v1.20.0"
506506
run-install: |
507507
- cwd: ./packages/app
508508
args: ['--frozen-lockfile']
@@ -519,9 +519,9 @@ test:
519519

520520
```yaml
521521
include:
522-
- remote: "https://raw.githubusercontent.com/voidzero-dev/setup-vp/v1.19.0/gitlab/setup-vp.yml"
522+
- remote: "https://raw.githubusercontent.com/voidzero-dev/setup-vp/v1.20.0/gitlab/setup-vp.yml"
523523
inputs:
524-
setup-ref: "v1.19.0"
524+
setup-ref: "v1.20.0"
525525
sfw: true
526526
run-install: "true"
527527
@@ -538,9 +538,9 @@ Pass `NODE_AUTH_TOKEN` as a GitLab CI/CD variable and set `registry-url` when th
538538

539539
```yaml
540540
include:
541-
- remote: "https://raw.githubusercontent.com/voidzero-dev/setup-vp/v1.19.0/gitlab/setup-vp.yml"
541+
- remote: "https://raw.githubusercontent.com/voidzero-dev/setup-vp/v1.20.0/gitlab/setup-vp.yml"
542542
inputs:
543-
setup-ref: "v1.19.0"
543+
setup-ref: "v1.20.0"
544544
registry-url: "https://npm.pkg.github.com"
545545
scope: "@myorg"
546546
@@ -565,11 +565,11 @@ test:
565565
| `package-manager` | String input: `"true"`, `"false"`, or a YAML mapping of npm, pnpm, yarn, and bun to booleans (Vite+ 0.3.1+) | Unset (enabled on CI) |
566566
| `registry-url` | Optional registry URL to write to a temporary `.npmrc` | |
567567
| `scope` | Optional scope for authenticating against scoped registries | |
568-
| `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.19.0` |
568+
| `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.20.0` |
569569

570570
### GitLab Notes
571571

572-
- Use an exact release tag such as `v1.19.0` in the remote URL. Do not use `main` (mutable) or `v1` (frozen at v1.15.0, no longer updated).
572+
- Use an exact release tag such as `v1.20.0` in the remote URL. Do not use `main` (mutable) or `v1` (frozen at v1.15.0, no longer updated).
573573
- Always pin `setup-ref` to the same tag or commit SHA as the remote URL, so the compiled runtime matches the included template.
574574
- Quote GitLab string inputs such as `run-install: "false"`; unquoted booleans are rejected by GitLab before the setup runtime can parse them.
575575
- GitLab 17.9+ users can add `integrity` to pin the remote file hash.
@@ -595,7 +595,7 @@ resources:
595595
type: github
596596
endpoint: github
597597
name: voidzero-dev/setup-vp
598-
ref: refs/tags/v1.19.0
598+
ref: refs/tags/v1.20.0
599599
600600
pool:
601601
vmImage: ubuntu-latest
@@ -605,7 +605,7 @@ steps:
605605
606606
- template: azure/setup-vp.yml@setupVp
607607
parameters:
608-
setupRef: v1.19.0
608+
setupRef: v1.20.0
609609
nodeVersion: 24.x
610610
cache: true
611611
runInstall: true
@@ -625,7 +625,7 @@ Pin `ref` and `setupRef` to the same exact tag or commit SHA. Do not use the `v1
625625
| `sfw` | `false` | Wrap `vp install` with Socket Firewall Free. |
626626
| `registryUrl` | | Optional registry URL for a temporary `.npmrc`. |
627627
| `scope` | | Optional npm registry scope. |
628-
| `setupRef` | `v1.19.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. |
628+
| `setupRef` | `v1.20.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. |
629629
| `nodeVersion` | `24.x` | Passed to `UseNode@1`; an empty string skips Node setup. |
630630
| `nodeManager` | | Control Vite+'s Node.js manager: `false` keeps the agent's Node.js (e.g. from `UseNode@1`); `true` leaves the installer default unchanged; empty lets the installer decide. |
631631
| `packageManager` | Unset (enabled on CI) | Boolean or object mapping npm, pnpm, yarn, and bun to booleans (Vite+ 0.3.1+). Only false entries change modes. |
@@ -665,7 +665,7 @@ jobs:
665665
steps:
666666
- uses: actions/checkout@v7
667667
668-
- uses: voidzero-dev/setup-vp@v1.19.0
668+
- uses: voidzero-dev/setup-vp@v1.20.0
669669
with:
670670
node-version: "lts"
671671
cache: true
@@ -715,7 +715,7 @@ For new commits, review the changes and remove and re-add `run-e2e`. Results and
715715

716716
### Releasing
717717

718-
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.19.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).
718+
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.20.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).
719719

720720
To cut a release:
721721

@@ -734,8 +734,8 @@ To cut a release:
734734
4. Create the new annotated version tag and push it. For example:
735735

736736
```bash
737-
git tag -a v1.19.0 -m "v1.19.0"
738-
git push origin v1.19.0
737+
git tag -a v1.20.0 -m "v1.20.0"
738+
git push origin v1.20.0
739739
```
740740

741741
## Feedback

‎azure/setup-vp.yml‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ parameters:
1919
default: ""
2020
- name: setupRef
2121
type: string
22-
default: v1.19.0
22+
default: v1.20.0
2323
- name: nodeVersion
2424
type: string
2525
default: 24.x

‎gitlab/setup-vp.yml‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -27,7 +27,7 @@ spec:
2727
default: ""
2828
setup-ref:
2929
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."
30-
default: "v1.19.0"
30+
default: "v1.20.0"
3131
---
3232
.setup-vp-bootstrap:
3333
before_script:
@@ -56,7 +56,7 @@ spec:
5656
export SETUP_VP_NODE_MANAGER="${SETUP_VP_NODE_MANAGER:-}"
5757
export SETUP_VP_REGISTRY_URL="${SETUP_VP_REGISTRY_URL:-}"
5858
export SETUP_VP_SCOPE="${SETUP_VP_SCOPE:-}"
59-
export SETUP_VP_SETUP_REF="${SETUP_VP_SETUP_REF:-v1.19.0}"
59+
export SETUP_VP_SETUP_REF="${SETUP_VP_SETUP_REF:-v1.20.0}"
6060
6161
setup_vp_bootstrap_tmp="$(mktemp "${TMPDIR:-/tmp}/setup-vp-gitlab-bootstrap.XXXXXX")"
6262
setup_vp_env_tmp="$(mktemp "${TMPDIR:-/tmp}/setup-vp-gitlab-env.XXXXXX")"

‎package.json‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
{
22
"name": "setup-vp",
3-
"version": "1.19.0",
3+
"version": "1.20.0",
44
"private": true,
55
"type": "module",
66
"scripts": {

‎src/azure/template.test.ts‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,7 @@ describe("azure/setup-vp.yml", () => {
2222
expect(byName.sfw).toMatchObject({ type: "boolean", default: false });
2323
expect(byName.registryUrl).toMatchObject({ type: "string", default: "" });
2424
expect(byName.scope).toMatchObject({ type: "string", default: "" });
25-
expect(byName.setupRef).toMatchObject({ type: "string", default: "v1.19.0" });
25+
expect(byName.setupRef).toMatchObject({ type: "string", default: "v1.20.0" });
2626
expect(byName.nodeVersion).toMatchObject({ type: "string", default: "24.x" });
2727
expect(byName.packageManager).toMatchObject({ type: "object", default: "" });
2828
expect(byName.nodeManager).toMatchObject({ type: "string", default: "" });

0 commit comments

Comments
 (0)