feat: Add automated frontend dependency updates #22304
Conversation
|
This would need some changes to use vaadin-bot or whatever should be used @manolo. Not sure how to test it either - the script itself works but the action is unclear |
- Add script that updates dependencies based on branch (patch for non-main, latest for main) - Add GitHub workflow to run weekly and create PRs for main, 24.9, and 24.8 branches - Workflow runs every Monday at 04:00 UTC 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
Artur-
force-pushed
the
update-frontend-deps
branch
from
f5dfb8f to
40ec062
Compare
|
|
Running the script on maintenance branches causes the build to succeed with no errors if there are deprecated packages that do not have a patch available but require a major version bump. Could the script run This way we could manually review each package and make a PR manually. |
Add validation step to detect deprecated packages after running npm-check-updates. On maintenance branches where only patch updates are allowed, deprecated packages requiring major version bumps will cause the workflow to fail, alerting maintainers to manually review. Changes: - Rename script: update-frontend-depdendencies.sh → update-frontend-dependencies.sh - Add deprecated package check using `npm-check-updates --no-deprecated` - Exit with error code 1 when deprecated packages are found - Remove `|| true` from workflow to propagate failures - Fix typo in workflow filename reference This prevents silent failures where deprecated packages remain in maintenance branches because no patch version is available. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]>
|
Updated the script with that |
|
Instead of running once a week, maybe it would be better if it ran once a day, used a dedicated branch so if a PR is left open, it can push additional updates in there |
🤖 Generated with Claude Code