Bump to 1.0.2-pre and pin feature recommendation to :1#42
Merged
Conversation
Open the post-1.0.1 development cycle. The 1.0.1 release stream from the SSL_CERT_DIR fix used 1.0.1-pre while in flight; mirror that pattern for 1.0.2.
The devcontainer CLI's :latest resolution can lag behind the actual most-recent release (currently resolves to 1.0.0 even with 1.0.1 published), so users following the README guidance miss bug fixes. Pin all README examples to the major-version tag :1, which moves forward with each 1.x release. Also update the example in the feature manifest description (shown in the feature catalog) for consistency.
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
2 participants
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.
Summary
package-lock.jsonto1.0.2-pre.descriptionshown in the catalog) to pin the feature to:1instead of:latest(or unpinned, which behaves the same).Why
The devcontainer CLI's
:latestresolution can lag behind the actual most-recent published release — users following the previous README guidance ended up pinned to1.0.0even after1.0.1shipped. Pinning the major-version tag:1moves forward with every 1.x release without exposing users to breaking changes from a future major.Test plan
node test/validate-feature.mjs— all checks pass with the bumped version.1.0.2and updates the:1floating tag.https://claude.ai/code/session_018AmRDWxPGu5bHLKYfunWMj
Generated by Claude Code