feat: update plcc-ng to 2.0.0 - #4
Merged
Merged
Conversation
BREAKING CHANGE: plcc-ng 2.0.0 is a new major version (was 1.0.0). Images already published under the previous major tag keep plcc-ng 1.0.0; this release publishes under a new major tag.
There was a problem hiding this comment.
Pull request overview
Updates the repository’s pinned plcc-ng version references to align with the plcc-ng 2.0.0 release and the associated breaking-change release process for the prebuilt devcontainer images.
Changes:
- Pin plcc-ng to
2.0.0in feature test scenarios and assertions. - Pin plcc-ng to
2.0.0in the prebuilt image devcontainer configurations. - Refresh feature metadata proposals and user-facing docs to reference
2.0.0.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| test/plcc-ng/scenarios.json | Updates the test scenario to pin plcc-ng 2.0.0. |
| test/plcc-ng/pinned_version.sh | Updates the expected installed version assertion to 2.0.0. |
| src/plcc-ng/devcontainer-feature.json | Updates feature metadata to propose 2.0.0 and bumps feature patch version for publishing. |
| images/plcc-ng/.devcontainer/devcontainer.json | Pins the local plcc-ng feature option to install 2.0.0 in the standard image. |
| images/plcc-ng-full/.devcontainer/devcontainer.json | Pins the local plcc-ng feature option to install 2.0.0 in the full image. |
| docs/choosing-your-image.md | Updates the docs’ pinned-version example to 2.0.0. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
70
to
+74
| ``` | ||
|
|
||
| The feature's `version` option pins a plcc-ng release from | ||
| [PyPI](https://pypi.org/project/plcc-ng/), e.g. | ||
| `{ "version": "1.0.0" }`; the default is `latest`. | ||
| `{ "version": "2.0.0" }`; the default is `latest`. |
The 2.0.0 release publishes the images under :2 and leaves :1 on plcc-ng 1.x, so every image example that still said :1 would have sent readers to the previous major while the same page documented plcc-ng 2.0.0. The feature reference stays at :1 deliberately — that tag tracks the feature's own version, which is 1.0.1, not plcc-ng's. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Contributor
|
🐳 PR images built (amd64 only):
To test, point a devcontainer.json |
|
🎉 This PR is included in version 2.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
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
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.
Automated update: plcc-ng has a new release (2.0.0).
PyPI release: https://pypi.org/project/plcc-ng/2.0.0/
BREAKING CHANGE: plcc-ng 2.0.0 is a new major version (was 1.0.0). Images
already published under the previous major tag keep plcc-ng 1.0.0; this
release publishes under a new major tag.