Graduate lockfile from experimental to stable#1
Draft
brooke-hamilton wants to merge 10 commits intomainfrom
Draft
Graduate lockfile from experimental to stable#1brooke-hamilton wants to merge 10 commits intomainfrom
brooke-hamilton wants to merge 10 commits intomainfrom
Conversation
Signed-off-by: Brooke Hamilton <45323234+brooke-hamilton@users.noreply.github.com>
Signed-off-by: Brooke Hamilton <45323234+brooke-hamilton@users.noreply.github.com>
Signed-off-by: Brooke Hamilton <45323234+brooke-hamilton@users.noreply.github.com>
Signed-off-by: Brooke Hamilton <45323234+brooke-hamilton@users.noreply.github.com>
Signed-off-by: Brooke Hamilton <45323234+brooke-hamilton@users.noreply.github.com>
Signed-off-by: Brooke Hamilton <45323234+brooke-hamilton@users.noreply.github.com>
…ate-lockfile Bring in the 0.86.1 fix that excludes `--additional-features`-only features from the lockfile, and integrate it with the lockfile graduation work on this branch. Conflict resolution: - src/spec-configuration/containerFeaturesConfiguration.ts: Drop the `initLockfile` argument from the `writeLockfile` call. The graduation work removed `forceInitLockfile` from `writeLockfile` and `initLockfile` from `readLockfile`'s return, so the incoming reference no longer compiles. The remaining `generateLockfile(featuresConfig, config, additionalFeatures)` call from main is preserved inside the `!params.noLockfile` guard. Other reconciliations: - package.json: keep 0.87.0 (graduation release) instead of 0.86.1 so the version reflects the graduation feature set being shipped. - CHANGELOG.md: move the 0.87.0 graduation entry under "May 2026" and nest the 0.86.1 bullet beneath it for historical accuracy. Signed-off-by: Brooke Hamilton <Brooke.Hamilton+microsoft@microsoft.com>
Signed-off-by: Brooke Hamilton <Brooke.Hamilton+microsoft@microsoft.com>
Signed-off-by: Brooke Hamilton <45323234+brooke-hamilton@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This pull request graduates lockfile support from experimental to stable, making lockfile generation the default behavior during
buildandupoperations. It introduces new flags to control lockfile handling, deprecates the old experimental flags, and updates the documentation and codebase to reflect these changes. The CLI now enforces mutual exclusivity between lockfile-related flags and provides clear user warnings for deprecated options.Lockfile feature graduation and CLI changes:
Lockfiles (
.devcontainer-lock.json) are now generated by default onbuildandupfor reproducible builds. The new--no-lockfileflag disables lockfile generation, while--frozen-lockfileensures the lockfile exists and is unchanged. The experimental flags--experimental-lockfileand--experimental-frozen-lockfileare deprecated but still accepted with a warning. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10]The CLI enforces that
--no-lockfilecannot be used together with any of the (deprecated or stable) lockfile-enforcing flags. [1] [2]Deprecated flags now trigger warnings to inform users of the new defaults and recommended options.
Codebase and API updates:
Internal parameters, interfaces, and function signatures are updated to use
noLockfileandfrozenLockfileinstead of the experimental flags, and all related logic is refactored accordingly. [1] [2] [3] [4] [5] [6] [7] [8] [9] [10] [11]The lockfile write and read logic is updated to support the new flags and behavior, and to throw errors or skip writing as appropriate. [1] [2] [3] [4] [5] [6] [7]
Documentation and tooling:
Documentation is updated to describe the new default lockfile behavior, usage of new flags, and deprecation of the old flags. [1] [2] [3]
Adds the Mocha Test Adapter extension to the devcontainer for improved test integration in VS Code.
Bumps package version to
0.87.0to reflect these changes.