Angular: Fix @angular/forms version to 21 in sandbox#35112
Conversation
There was a problem hiding this comment.
Pull request overview
Pins @angular/forms to an Angular v21 release in the Angular CLI sandbox template to prevent dependency drift (forms jumping to v22) that can break CI sandbox builds.
Changes:
- Update the Angular CLI “Latest” sandbox template to install
@angular/forms@21.2.16instead of@latest. - Add an inline note indicating the pin should be revisited when Angular CLI starts generating Angular v22 projects by default.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughPinned the ChangesAngular Forms Version Pin
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~2 minutes Possibly related PRs
✨ Finishing Touches📝 Generate docstrings
Comment |
…s-version Angular: Fix @angular/forms version to 21 in sandbox
…s-version Angular: Fix @angular/forms version to 21 in sandbox
What I did
Forced
@angular/formsto stay on v21 to match other deps instead of going to v22.Avoids this kind of CI failure.
Might need to be adjusted again in the near future once
ng newstarts releasing Angular 22, time will tell.Checklist for Contributors
ø
Manual testing
🦋 Canary release
This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the
@storybookjs/coreteam here.core team members can create a canary release here or locally with
gh workflow run --repo storybookjs/storybook publish.yml --field pr=<PR_NUMBER>Summary by CodeRabbit