Skip to content

Fix unsupported Feature mount metadata blocking release - #3

Merged
temeteke merged 2 commits into
mainfrom
fix/feature-mount-metadata
Oct 17, 2026
Merged

temeteke merged 2 commits into
mainfrom
fix/feature-mount-metadata

Conversation

@temeteke

@temeteke temeteke commented Oct 17, 2026 •

Copy link
Copy Markdown
Owner

Problem

The recently added tmux and Vim Feature manifests contain an unsupported readonly field in their mounts metadata. The existing devcontainers/action@v1 publishing workflow already validates Feature metadata during release.

The precise deploy job failure message has not been independently retrieved, so this is a confirmed schema defect rather than a proven root cause of the reported failure.

Changes

  • Remove the unsupported readonly properties from the two Feature manifests.
  • Update documentation to clearly state that these host config mounts are read-write; processes in the container may modify host files.
  • Remove the separate PR-only validate workflow to keep CI minimal. Rely on the existing Release Dev Container Features workflow's built-in Feature packaging and metadata validation after merging.

Verification

  • The modified manifests passed devcontainer features package ./src in the previous PR branch run, before the redundant workflow was removed.
  • The release workflow must be checked after merging this PR.
  • test/validate.sh remains available for manual JSON/Bash syntax checks.

@temeteke
temeteke merged commit 0bbafcf into main Oct 17, 2026
@temeteke
temeteke deleted the fix/feature-mount-metadata branch October 17, 2026 06:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant