Skip to content

Commit 49c3e4e

Browse files
fengmk2fengmk2
authored
chore: release v1.19.0 (#141)
Bump `package.json`, the README examples, and the GitLab and Azure template defaults to `v1.19.0`. Changes since `v1.18.0`: - Add the `cache-save` input for restore-only caching. - Update `vite-plus` to `v0.3.0`. - Update `socketdev/sfw-free` to `v1.15.1`. - Update `pnpm` to `v11.25.0`. After merge, create the annotated tag `v1.19.0` on the merge commit. Push the tag.
1 parent 5d3aeab commit 49c3e4e

5 files changed

Lines changed: 44 additions & 44 deletions

File tree

‎README.md‎

Lines changed: 39 additions & 39 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.18.0
21+
- uses: voidzero-dev/setup-vp@v1.19.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@v6
36-
- uses: voidzero-dev/setup-vp@v1.18.0
36+
- uses: voidzero-dev/setup-vp@v1.19.0
3737
```
3838

3939
### With Node.js Version
4040

4141
```yaml
4242
steps:
4343
- uses: actions/checkout@v6
44-
- uses: voidzero-dev/setup-vp@v1.18.0
44+
- uses: voidzero-dev/setup-vp@v1.19.0
4545
with:
4646
node-version: "lts"
4747
```
@@ -51,7 +51,7 @@ steps:
5151
```yaml
5252
steps:
5353
- uses: actions/checkout@v6
54-
- uses: voidzero-dev/setup-vp@v1.18.0
54+
- uses: voidzero-dev/setup-vp@v1.19.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.18.0
71+
- uses: voidzero-dev/setup-vp@v1.19.0
7272
with:
7373
node-manager: false
7474
```
@@ -78,7 +78,7 @@ steps:
7878
```yaml
7979
steps:
8080
- uses: actions/checkout@v6
81-
- uses: voidzero-dev/setup-vp@v1.18.0
81+
- uses: voidzero-dev/setup-vp@v1.19.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@v6
94-
- uses: voidzero-dev/setup-vp@v1.18.0
94+
- uses: voidzero-dev/setup-vp@v1.19.0
9595
with:
9696
node-version: "lts"
9797
cache: true
@@ -103,7 +103,7 @@ steps:
103103
```yaml
104104
steps:
105105
- uses: actions/checkout@v6
106-
- uses: voidzero-dev/setup-vp@v1.18.0
106+
- uses: voidzero-dev/setup-vp@v1.19.0
107107
with:
108108
version: "1.2.3"
109109
node-version: "lts"
@@ -127,7 +127,7 @@ to `latest` only when nothing pins a resolvable version. So a project that pins
127127
```yaml
128128
steps:
129129
- uses: actions/checkout@v6
130-
- uses: voidzero-dev/setup-vp@v1.18.0
130+
- uses: voidzero-dev/setup-vp@v1.19.0
131131
with:
132132
cache: true
133133
```
@@ -140,7 +140,7 @@ worth watching for, since it means the pinned version was not applied:
140140
```yaml
141141
steps:
142142
- uses: actions/checkout@v6
143-
- uses: voidzero-dev/setup-vp@v1.18.0
143+
- uses: voidzero-dev/setup-vp@v1.19.0
144144
with:
145145
version-file: package.json
146146
cache: true
@@ -200,7 +200,7 @@ action warns and falls back to `latest`. (Auto-detection instead resolves a
200200
```yaml
201201
steps:
202202
- uses: actions/checkout@v6
203-
- uses: voidzero-dev/setup-vp@v1.18.0
203+
- uses: voidzero-dev/setup-vp@v1.19.0
204204
with:
205205
node-version: "lts"
206206
cache: true
@@ -225,7 +225,7 @@ minimal:
225225
226226
steps:
227227
- uses: actions/checkout@v6
228-
- uses: voidzero-dev/setup-vp@v1.18.0
228+
- uses: voidzero-dev/setup-vp@v1.19.0
229229
with:
230230
node-version: "lts"
231231
env:
@@ -242,7 +242,7 @@ read the repo `.npmrc` per its own config resolution):
242242
```yaml
243243
steps:
244244
- uses: actions/checkout@v6
245-
- uses: voidzero-dev/setup-vp@v1.18.0
245+
- uses: voidzero-dev/setup-vp@v1.19.0
246246
with:
247247
node-version: "lts"
248248
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
260260
```yaml
261261
steps:
262262
- uses: actions/checkout@v6
263-
- uses: voidzero-dev/setup-vp@v1.18.0
263+
- uses: voidzero-dev/setup-vp@v1.19.0
264264
with:
265265
sfw: true
266266
run-install: true
@@ -281,7 +281,7 @@ steps:
281281
- uses: socketdev/action@<sha>
282282
with:
283283
mode: firewall-free
284-
- uses: voidzero-dev/setup-vp@v1.18.0
284+
- uses: voidzero-dev/setup-vp@v1.19.0
285285
with:
286286
sfw: true
287287
run-install: true
@@ -305,7 +305,7 @@ jobs:
305305
steps:
306306
- run: apk add --no-cache bash curl gcompat libstdc++
307307
- uses: actions/checkout@v6
308-
- uses: voidzero-dev/setup-vp@v1.18.0
308+
- uses: voidzero-dev/setup-vp@v1.19.0
309309
```
310310

311311
### Matrix Testing with Multiple Node.js Versions
@@ -319,7 +319,7 @@ jobs:
319319
runs-on: ubuntu-latest
320320
steps:
321321
- uses: actions/checkout@v6
322-
- uses: voidzero-dev/setup-vp@v1.18.0
322+
- uses: voidzero-dev/setup-vp@v1.19.0
323323
with:
324324
node-version: ${{ matrix.node-version }}
325325
cache: true
@@ -392,7 +392,7 @@ Set `cache-save: false` to restore an existing dependency cache without writing
392392
For example, this workflow restores caches on every run but saves them only from the `main` branch:
393393

394394
```yaml
395-
- uses: voidzero-dev/setup-vp@v1.18.0
395+
- uses: voidzero-dev/setup-vp@v1.19.0
396396
with:
397397
cache: true
398398
cache-save: ${{ github.event_name == 'push' && github.ref == 'refs/heads/main' }}
@@ -414,9 +414,9 @@ Use an exact release tag in the `include:remote` URL, and pin `setup-ref` to the
414414

415415
```yaml
416416
include:
417-
- remote: "https://raw.githubusercontent.com/voidzero-dev/setup-vp/v1.18.0/gitlab/setup-vp.yml"
417+
- remote: "https://raw.githubusercontent.com/voidzero-dev/setup-vp/v1.19.0/gitlab/setup-vp.yml"
418418
inputs:
419-
setup-ref: "v1.18.0"
419+
setup-ref: "v1.19.0"
420420
421421
test:
422422
extends: .setup-vp
@@ -429,9 +429,9 @@ test:
429429

430430
```yaml
431431
include:
432-
- remote: "https://raw.githubusercontent.com/voidzero-dev/setup-vp/v1.18.0/gitlab/setup-vp.yml"
432+
- remote: "https://raw.githubusercontent.com/voidzero-dev/setup-vp/v1.19.0/gitlab/setup-vp.yml"
433433
inputs:
434-
setup-ref: "v1.18.0"
434+
setup-ref: "v1.19.0"
435435
version: "latest"
436436
working-directory: "web"
437437
run-install: "true"
@@ -449,14 +449,14 @@ GitLab replaces array keywords such as `before_script` when a job uses `extends`
449449

450450
```yaml
451451
include:
452-
- remote: "https://raw.githubusercontent.com/voidzero-dev/setup-vp/v1.18.0/gitlab/setup-vp.yml"
452+
- remote: "https://raw.githubusercontent.com/voidzero-dev/setup-vp/v1.19.0/gitlab/setup-vp.yml"
453453
454454
test:
455455
image: node:24
456456
variables:
457457
SETUP_VP_VERSION: "latest"
458458
SETUP_VP_RUN_INSTALL: "true"
459-
SETUP_VP_SETUP_REF: "v1.18.0"
459+
SETUP_VP_SETUP_REF: "v1.19.0"
460460
before_script:
461461
- !reference [.setup-vp-bootstrap, before_script]
462462
- npm config set //registry.example.com/:_authToken "$NODE_AUTH_TOKEN"
@@ -471,9 +471,9 @@ Use the same pattern when the project has `default:before_script`; put the share
471471

472472
```yaml
473473
include:
474-
- remote: "https://raw.githubusercontent.com/voidzero-dev/setup-vp/v1.18.0/gitlab/setup-vp.yml"
474+
- remote: "https://raw.githubusercontent.com/voidzero-dev/setup-vp/v1.19.0/gitlab/setup-vp.yml"
475475
inputs:
476-
setup-ref: "v1.18.0"
476+
setup-ref: "v1.19.0"
477477
run-install: |
478478
- cwd: ./packages/app
479479
args: ['--frozen-lockfile']
@@ -490,9 +490,9 @@ test:
490490

491491
```yaml
492492
include:
493-
- remote: "https://raw.githubusercontent.com/voidzero-dev/setup-vp/v1.18.0/gitlab/setup-vp.yml"
493+
- remote: "https://raw.githubusercontent.com/voidzero-dev/setup-vp/v1.19.0/gitlab/setup-vp.yml"
494494
inputs:
495-
setup-ref: "v1.18.0"
495+
setup-ref: "v1.19.0"
496496
sfw: true
497497
run-install: "true"
498498
@@ -509,9 +509,9 @@ Pass `NODE_AUTH_TOKEN` as a GitLab CI/CD variable and set `registry-url` when th
509509

510510
```yaml
511511
include:
512-
- remote: "https://raw.githubusercontent.com/voidzero-dev/setup-vp/v1.18.0/gitlab/setup-vp.yml"
512+
- remote: "https://raw.githubusercontent.com/voidzero-dev/setup-vp/v1.19.0/gitlab/setup-vp.yml"
513513
inputs:
514-
setup-ref: "v1.18.0"
514+
setup-ref: "v1.19.0"
515515
registry-url: "https://npm.pkg.github.com"
516516
scope: "@myorg"
517517
@@ -535,11 +535,11 @@ test:
535535
| `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) | |
536536
| `registry-url` | Optional registry URL to write to a temporary `.npmrc` | |
537537
| `scope` | Optional scope for authenticating against scoped registries | |
538-
| `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.18.0` |
538+
| `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` |
539539

540540
### GitLab Notes
541541

542-
- Use an exact release tag such as `v1.18.0` in the remote URL. Do not use `main` (mutable) or `v1` (frozen at v1.15.0, no longer updated).
542+
- 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).
543543
- Always pin `setup-ref` to the same tag or commit SHA as the remote URL, so the compiled runtime matches the included template.
544544
- Quote GitLab string inputs such as `run-install: "false"`; unquoted booleans are rejected by GitLab before the setup runtime can parse them.
545545
- GitLab 17.9+ users can add `integrity` to pin the remote file hash.
@@ -565,7 +565,7 @@ resources:
565565
type: github
566566
endpoint: github
567567
name: voidzero-dev/setup-vp
568-
ref: refs/tags/v1.18.0
568+
ref: refs/tags/v1.19.0
569569
570570
pool:
571571
vmImage: ubuntu-latest
@@ -575,7 +575,7 @@ steps:
575575
576576
- template: azure/setup-vp.yml@setupVp
577577
parameters:
578-
setupRef: v1.18.0
578+
setupRef: v1.19.0
579579
nodeVersion: 24.x
580580
cache: true
581581
runInstall: true
@@ -595,7 +595,7 @@ Pin `ref` and `setupRef` to the same exact tag or commit SHA. Do not use the `v1
595595
| `sfw` | `false` | Wrap `vp install` with Socket Firewall Free. |
596596
| `registryUrl` | | Optional registry URL for a temporary `.npmrc`. |
597597
| `scope` | | Optional npm registry scope. |
598-
| `setupRef` | `v1.18.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. |
598+
| `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. |
599599
| `nodeVersion` | `24.x` | Passed to `UseNode@1`; an empty string skips Node setup. |
600600
| `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. |
601601
| `cache` | `false` | Enable Azure `Cache@2` around the package-manager cache directory. |
@@ -634,7 +634,7 @@ jobs:
634634
steps:
635635
- uses: actions/checkout@v6
636636
637-
- uses: voidzero-dev/setup-vp@v1.18.0
637+
- uses: voidzero-dev/setup-vp@v1.19.0
638638
with:
639639
node-version: "lts"
640640
cache: true
@@ -678,7 +678,7 @@ vp install
678678

679679
### Releasing
680680

681-
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.18.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).
681+
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).
682682

683683
To cut a release:
684684

@@ -697,8 +697,8 @@ To cut a release:
697697
4. Create the new annotated version tag and push it. For example:
698698

699699
```bash
700-
git tag -a v1.18.0 -m "v1.18.0"
701-
git push origin v1.18.0
700+
git tag -a v1.19.0 -m "v1.19.0"
701+
git push origin v1.19.0
702702
```
703703

704704
## 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.18.0
22+
default: v1.19.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
@@ -24,7 +24,7 @@ spec:
2424
default: ""
2525
setup-ref:
2626
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."
27-
default: "v1.18.0"
27+
default: "v1.19.0"
2828
---
2929
.setup-vp-bootstrap:
3030
before_script:
@@ -52,7 +52,7 @@ spec:
5252
export SETUP_VP_NODE_MANAGER="${SETUP_VP_NODE_MANAGER:-}"
5353
export SETUP_VP_REGISTRY_URL="${SETUP_VP_REGISTRY_URL:-}"
5454
export SETUP_VP_SCOPE="${SETUP_VP_SCOPE:-}"
55-
export SETUP_VP_SETUP_REF="${SETUP_VP_SETUP_REF:-v1.18.0}"
55+
export SETUP_VP_SETUP_REF="${SETUP_VP_SETUP_REF:-v1.19.0}"
5656
5757
setup_vp_bootstrap_tmp="$(mktemp "${TMPDIR:-/tmp}/setup-vp-gitlab-bootstrap.XXXXXX")"
5858
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.18.0",
3+
"version": "1.19.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.18.0" });
25+
expect(byName.setupRef).toMatchObject({ type: "string", default: "v1.19.0" });
2626
expect(byName.nodeVersion).toMatchObject({ type: "string", default: "24.x" });
2727
expect(byName.nodeManager).toMatchObject({ type: "string", default: "" });
2828
expect(byName.cache).toMatchObject({ type: "boolean", default: false });

0 commit comments

Comments
 (0)