devcontainers / devcontainers/cli

`up --frozen-lockfile` doesn't fail when lockfile is outdated

Open
#1,273 1 comment 0 reactions 1 assignee Claimed by @v-Kaniska244 View on GitHub
Dominant language
TypeScript
Stars
3k
Forks
457
Avg merge
13h 17m
Merged PRs (30d)
6

Description

`npx @devcontainers/cli up --help` says:
```
--frozen-lockfile Ensure lockfile exists and remains unchanged;
fail otherwise. [boolean] [default: false]
```

I just ran `up --frozen-lockfile` twice, changing `devcontainer.json` (Really simple - image and feature. Changed feature from one to another.) in between without updating the lockfile. Got success and the same container id both times.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.