Skip to content

Commit 8891bd4

Browse files
fengmk2Copilot
andauthored
Potential fix for pull request finding
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Signed-off-by: MK (fengmk2) <fengmk2@gmail.com>
1 parent 6875014 commit 8891bd4

1 file changed

Lines changed: 2 additions & 2 deletions

File tree

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -120,12 +120,12 @@ jobs:
120120

121121
### Vite+ Installation Cache
122122

123-
The Vite+ CLI installation (`~/.vite-plus/`) is **always cached** automatically — no configuration needed. On cache hit, the install script is skipped entirely, saving 10–60s depending on network conditions.
123+
The Vite+ CLI installation (`~/.vite-plus/`) is cached automatically on a best-effort basis — no configuration needed. If a cache key can be constructed for the resolved version, it will be saved and reused on subsequent runs. On cache hit, the install script is skipped entirely, saving 10–60s depending on network conditions.
124124

125125
The cache key includes OS, architecture, Vite+ version, and Node.js version:
126126
`setup-vp-{OS}-{arch}-{vp-version}-node{node-version}`
127127

128-
When the `version` input is a dist-tag (e.g. `latest`, `alpha`), it is resolved to a precise semver version via the npm registry before constructing the cache key.
128+
When the `version` input is a dist-tag (e.g. `latest`, `alpha`), it is resolved to a precise semver version via the npm registry before constructing the cache key. If version resolution fails (for example, due to npm registry/network issues or an unresolvable version/tag), no cache key is saved and the Vite+ installation will not be cached for that run.
129129

130130
### Dependency Cache
131131

0 commit comments

Comments
 (0)