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 a5b7cbe
Browse filesBrowse the repository at this point in the historyBrowse files
fix(features)!: map and refuse legacy Feature ids as the reference does
Legacy and shorthand Feature ids now follow the reference CLI's
getBackwardCompatibleFeatureId, getFeatureIdType and
updateDeprecatedFeaturesIntoOptions in up, build, read-configuration,
upgrade, features resolve-dependencies, features info and outdated:
- Only exact legacy names (node, golang, …) map to
ghcr.io/devcontainers/features/<name>:1, and log TS's
"(!) WARNING: Using the deprecated '<id>' Feature" line.
- A legacy name with a tag (node:18, node:1) and any other id without a
'/' fail with "Legacy feature '<id>' not supported".
- gradle, maven and jupyterlab move into the java/python Feature they
are now an option of, before any Feature is resolved.
- owner/repo/feat is an OCI reference whose registry is "owner", no
longer ghcr.io/owner/repo/feat.
- --skip-feature-auto-mapping is accepted and ignored, as in TS.
- outdated reports what getRef parses as written: legacy ids are left
out, and a Feature without published versions is reported empty.
- The lockfile's integrity is looked up by the mapped id, so an entry
under a legacy id doesn't pin it, as in TS.
A ts-oracle golden pins the three TS functions, and five parity cases
compare the user-visible results with the reference.
BREAKING CHANGE: node:18-style ids, other names without a '/', and
owner/repo/feat ids that relied on an implicit ghcr.io now fail or
resolve as in the official CLI; docs/migration.md says how to write
them.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Copy file name to clipboardExpand all lines: docs/parity/parity-matrix.yaml
+67Lines changed: 67 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -348,6 +348,19 @@ initial_cases:
348
348
current_status: match
349
349
notes: "outdated writes JSON.stringify(outdated, undefined, process.stdout.isTTY ? ' ' : undefined): with stdout not a terminal, as here, the result is one unindented line ({\"features\":{}}, a local Feature having no versions). Go used to indent it always."
notes: "loadVersionInfo calls getRef on each id as written, without the legacy mapping: node, node:18, terraform, my-custom-feature and owner/feat do not parse and are left out, as is the local Feature. localhost:1/ns/feat:1 parses; its tags cannot be listed (connection refused), and it is still reported, with no versions: {\"features\":{\"localhost:1/ns/feat:1\":{}}}. Go used to map the legacy ids to ghcr.io and report them, and to leave out a Feature without versions."
363
+
351
364
- id: outdated.text-without-features-success
352
365
lane: contract
353
366
command: outdated
@@ -856,6 +869,60 @@ initial_cases:
856
869
current_status: match
857
870
notes: "A bare Feature id ('myfeature') is a legacy id TS rejects ('Legacy feature myfeature not supported...'), exit 1 with no result. Go used to drop the Feature error silently and print a configuration without the Feature."
notes: "getBackwardCompatibleFeatureId maps only the exact legacy names: 'node:18' stays as written and getFeatureIdType refuses it ('Legacy feature 'node:18' not supported...'), exit 1. Go used to map it to ghcr.io/devcontainers/features/node:18 and fail fetching it."
notes: "updateDeprecatedFeaturesIntoOptions moves gradle into a ghcr.io/devcontainers/features/java:1 it appends after the other Features and logs '(!) WARNING: Using the deprecated 'gradle' Feature...' before any Feature is resolved, so node:18 is refused before java is requested: no network. Go used to resolve gradle in place, requesting java first."
notes: "An id with a slash and no dot in its first segment is an OCI reference whose registry is that segment (getRef): 'devcontainers/features/node:1' is requested from the host devcontainers, which does not resolve, and the GitHub Releases fallback refuses the id, exit 1. Go used to prefix ghcr.io/ and install ghcr.io/devcontainers/features/node:1. Only the exit code is compared: TS ends with its GitHub Releases fallback, which this CLI does not implement (DIVERGENCES.md). network_required for the DNS lookup."
notes: "TS declares --skip-feature-auto-mapping but generateFeaturesConfig never passes it to processFeatureIdentifier, so 'node' is still mapped to ghcr.io/devcontainers/features/node:1 with its deprecation warning, exit 0. Go used to honor the flag and fail to parse 'node' as a reference."
0 commit comments