Aquesta és una versió anterior. La versió actual és la 0.9.7. Nub 0.9.7 · Data de publicació:
Fitxers d’instal·lació 0.7.2
| Arquitectura | Tipus | Àmbit | Mida del fitxer | Baixa | SHA256 |
|---|---|---|---|---|---|
| 64 bits | ZIP → Portable | — | — | github.com | VirusTotal |
| ARM64 | ZIP → Portable | — | — | github.com | VirusTotal |
L’enllaç i l’SHA256 provenen del manifest comunitari del Gestor de paquets del Windows. Convé comparar el hash del fitxer baixat abans d’executar-lo.
Notes de la versió
Supply-chain and workspace resolution fixes, plus per-invocation platform selection for cross-platform installs.
Release-age gate
Running a tool without naming a version resolves the latest tag, which narrowed to that one version — so a minimumReleaseAge window covering it left nothing to fall back to and nubx <tool> failed outright. A blocked latest now resolves to the newest release that clears the window (#682, #681).
$ nubx some-tool
+ some-tool@2.3.0 latest 2.4.0
warn: the latest some-tool release (2.4.0) is younger than minimumReleaseAge; using 2.3.0 instead
help: to take the newest release anyway: `--minimum-release-age=0`, or `--minimum-release-age-exclude=some-tool`
The fallback stops at whatever the publisher currently tags latest, so a higher version they published and then untagged is never selected, and a latest pointing at a prerelease is refused rather than falling back onto a stable release from an older line. The same narrowing also affected the non-strict mode in the opposite direction — the blocked release was the only candidate, so it was re-selected and the window had no effect. It is now enforced there too.
Installs
──────────────────┬──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┬────────────
Area │What changed │Commit
──────────────────┼──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┼────────────
Platform selection│--os, --cpu and --libc select optional dependencies for a target other than the host, per invocation (#683) │af33650
──────────────────┼──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┼────────────
Workspace protocol│A workspace:<path> tail naming a member directory resolves to that member instead of being read as a version range and sent to the registry (#674) │ab7350e
──────────────────┼──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┼────────────
Prewarm │The prewarm graph is host-filtered under the isolated layout, matching the linked tree (#679) │adac3af
──────────────────┼──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┼────────────
Patch application │A failing hunk reports its number and line, counted from 1, with what was searched for and that the patch needs regenerating (#674) │ab7350e
──────────────────┴──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────┴────────────
Diagnostics
The refusal to accept a nodeOptions entry now names NODE_OPTIONS as the constraint doing the refusing (#684, c178118).
Documentation
The package-manager page's layout section is reworked to state the policy as neutral-surface-first, with a dead npmrc example corrected and a duplicated build-approval enumeration removed.
What's Changed
- fix: name NODE_OPTIONS as the constraint refusing a nodeOptions entry by @colinhacks in #684
- fix(install): host-filter the prewarm graph under the isolated layout too by @colinhacks in #679
- feat(install): --os / --cpu / --libc for per-invocation platform selection by @colinhacks in #683
- fix(aube): resolve workspace: specifiers, and say where a patch hunk failed by @colinhacks in #674
- fix(resolver): fall back to the newest mature release when the age gate blocks latest by @colinhacks in #682
