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
{{ message }}
Repository navigation
Commit e5049ff
Browse filesBrowse the repository at this point in the historyBrowse files
Key NuGet lock versions as the writers do; vendored matches hosted
Second review round on NuGet other-version discovery.
- Discovery keyed lock versions by `normalize_nuget_version` of the
TRIMMED `resolved`, while both writers normalize the raw value: a
padded ` 13.0.3 ` beside `13.0.3` was one version to discovery (and
attested) but another to the writers (which refuse the lock). It is
keyed raw now, so the ref is withheld (`vex_nuget_lock_other_version`).
- A vendored ref was still emitted, attested and unpinned, when the lock
could not be read; hosted emits none. Vendored now matches hosted.
- A vendored ref named `nupkg_leaf(id, lock spelling)` when locked but
the feed's real file otherwise; it always names the feed's file.
- The unusable-version diagnostic named the root lock even when only a
member lock held the entry; it names the locks that do.
- Pre-release labels order by identifier (numeric ones numerically), so
the lock an other-version mark points at follows NuGet precedence.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
| maven | `pom.xml` (+ `.mvn/maven.config`, `.mvn/checksums/checksums.sha256`) | a dependency version `<base>-socket.<hex8>` matching exactly ONE `socket-patch-<uuid>` repository on the patch host | pre-v5 single-POM wiring only: `socket-patch-vendor-<uuid>` repository + exactly one jar under `.socket/vendor/maven/<uuid>/` with a matching `.sha1`. A v5 suffixed pin served from `.socket/vendor/maven2` is no reference here: its ledger entry's wiring check gates it, so without a ledger it is not attested | Trusted Checksums line when enabled; not required (the suffixed version is the pin) |
541
541
| gradle (v5.0) | `.socket/gradle/hosted-index.tsv`, the owned hosted script, and every settings script and lock file the script graph reaches | an index row whose repository URL is on the patch host and names the row's uuid, live only while the owned script is intact, every build's settings file applies it with the current index digest, every lock entry of the GA is the suffixed version, no `settings-gradle.lockfile` names the GA and no build script sets a custom `lockFile` (otherwise `patched_ref_invalid`) | none here: a vendored Gradle entry is gated by its ledger entry's wiring check | the suffixed copies installed in the Gradle cache; required (never the lock basis), because the script lets a higher upstream version resolve |
542
-
| nuget | the first of `nuget.config` / `NuGet.config` / `NuGet.Config`, + `packages.lock.json` | source `socket-patch-<uuid>` + its exclusive exact-id `<packageSourceMapping>`; version from `packages.lock.json` | the same mapping onto `.socket/vendor/nuget/<uuid>`; version from the feed's single nupkg (the patched version), else the lock | `contentHash`, required. Lock versions match under `normalize_nuget_version` of the trimmed `resolved`, as the writers match them (`1.0` and `1.0.0` are one version; an empty one is `patched_ref_invalid`). When the governed locks also lock the mapped id at a version other than the patched one (another target framework or project), which both writers refuse (`redirect_nuget_lock_other_version`, `vendor_nuget_lock_other_version`), the reference is kept but not attested (`vex_nuget_lock_other_version`, naming the other versions and their locks). Vendored, the patched version is the feed's single nupkg: it is the only reference, even when no lock entry is at it, and other locked versions are never references. A hosted url names no version, so each hosted reference is checked against its own version: any two locked versions withhold them all, and a single locked version other than the patch's is gated by the patch record (`record_mismatch`). |
542
+
| nuget | the first of `nuget.config` / `NuGet.config` / `NuGet.Config`, + `packages.lock.json` | source `socket-patch-<uuid>` + its exclusive exact-id `<packageSourceMapping>`; version from `packages.lock.json` | the same mapping onto `.socket/vendor/nuget/<uuid>`; version from the feed's single nupkg (the patched version), else the lock | `contentHash`, required. Lock versions match under `normalize_nuget_version` of the raw `resolved`, as the writers match them (a padded ` 1.0 ` is another version) (`1.0` and `1.0.0` are one version; an empty one is `patched_ref_invalid`). When the governed locks also lock the mapped id at a version other than the patched one (another target framework or project), which both writers refuse (`redirect_nuget_lock_other_version`, `vendor_nuget_lock_other_version`), the reference is kept but not attested (`vex_nuget_lock_other_version`, naming the other versions and their locks). Vendored, the patched version is the feed's single nupkg: it is the only reference, even when no lock entry is at it, and other locked versions are never references. A hosted url names no version, so each hosted reference is checked against its own version: any two locked versions withhold them all, and a single locked version other than the patch's is gated by the patch record (`record_mismatch`). |
543
543
| deno | `deno.lock`'s npm section, only as evidence against an npm-family pin of a `name@version` it also locks, which `vex` then omits (see **Unattested references**, #406); hosted and vendored npm runs warn about such a pin (`redirect_npm_deno_lock` / `vendor_npm_deno_lock`) | — (no hosted mode) | — (no vendored backend) | — |
0 commit comments