Outdated command

[chrmarti]

Similar data to yarn's and NPM's outdated command. microsoft/vscode-remote-release#8640

E.g.:

$ devcontainer outdated --workspace-folder ../../smktst --config ../../smktst/.devcontainer/lockfile/devcontainer.json
[3 ms] @devcontainers/cli 0.46.0. Node.js v16.20.1. darwin 22.5.0 arm64.
{
  "features": {
    "ghcr.io/devcontainers/features/git:1.0": {
      "current": "1.0.4",
      "wanted": "1.0.5",
      "latest": "1.1.5"
    }
  }
}

[samruddhikhandale]

left one question, besides that looks good to me!

[joshspicer]

A couple questions:

1. Features in my devcontainer.json without a version are omitted. Should we assume latest in this case and resolve the values accordingly?

vs.

---

2. Features that exist but that you don't have local access to don't fail the entire command. This is probably ok but thought i'd highlight. I feel the most logical thing to do here is mirror what npm/yarn does?

---

3. Features with a sha hash as the version are also ignored.

[chrmarti]

A couple questions:

1. Features in my devcontainer.json without a version are omitted. Should we assume latest in this case and resolve the values accordingly?

Fixed.

2. Features that exist but that you don't have local access to don't fail the entire command. This is probably ok but thought i'd highlight. I feel the most logical thing to do here is mirror what npm/yarn does?

I agree. Not sure actually what npm/yarn do (seems my setup doesn't work with GitHub package repo atm), but having some resilience towards missing credentials makes sense.

3. Features with a sha hash as the version are also ignored.

Fixed.

Also adding an --output-format option with text being the default (following along the features info command).