Repository navigation
Release 0.18.6 - #67
Merged
Merged
Conversation
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
1 participant
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.
Prepare the coordinated 0.18.6 patch release for the first-occurrence reconciliation fix in #66. Update both package versions, template version, fallback generated lockfile versions, and root manifest/lockfile together. No dependency or data-model changes.
Validation passed on Node 24.11.1:
npm ci,CI=true npm run validate, both package dry runs,npm audit(zero vulnerabilities), andgit diff --check. A fresh consumer generated with the local unreleased package validated 224 resources with no errors or warnings. Two independent combined code and security reviews found no actionable issues. Changed files contain no private source material or secrets.