fix: update Angular support skill workspace guidance - #55
Merged
osnoser1 merged 4 commits intoJun 13, 2026
Merged
Conversation
Copy link
Copy Markdown
Member
Sorry, something went wrong.
Copy link
Copy Markdown
✅ Deploy Preview for limitless-angular-sanity-example canceled.
|
Sorry, something went wrong.
osnoser1
marked this pull request as ready for review
June 13, 2026 15:51
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.
PR Checklist
Closes #
What is the new behavior?
Updates the angular-version-support skill so adding Angular support defaults to moving workspace Angular package manifests, not only the library peer range and compatibility matrix.
The helper now scans workspace package.json files and updates direct Angular toolchain dependencies in apps/packages, while keeping --library-only available for explicit library-only support. The skill reference now instructs agents to resolve TypeScript and Angular-adjacent adapter compatibility, update the lockfile, and run workspace build/test validation after the deterministic helper step.
Does this PR introduce a breaking change?
Other information
Validation performed:
[Optional] What gif best describes this PR or how it makes you feel?