chore: update aws service spec in a separate job #26531
Conversation
aws-cdk-automation
added
the
pr/needs-maintainer-review
mrgrain
force-pushed
the
mrgrain/chore/spec-upgrade-workflow
branch
from
5f9ea23
to
89c1371
Compare
| run: |- | ||
| # Upgrade dependencies at repository root | ||
| ncu --upgrade --filter=typescript --target=patch | ||
| ncu --upgrade --reject=@types/node,@types/prettier,constructs,typescript,lerna --target=minor |
There was a problem hiding this comment.
Special case notice was:
We special-case lerna because we have a patch on it that stops applying if Lerna upgrades. Remove this once lerna/lerna#2874 releases.
The linked PR has now been published and we have already upgraded lerna manually beyond it.
The patch is long gone as well.
aws-cdk-automation
removed
the
pr/needs-maintainer-review
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
AWS CodeBuild CI Report
Powered by github-codebuild-logs, available on the AWS Serverless Application Repository |
|
Thank you for contributing! Your pull request will be updated from main and then merged automatically (do not update manually, and be sure to allow changes to be pushed to your fork). |
Currently this is just part of the
Yarn upgradeworkflow.We want a separate workflow so the updates are visible in the CHANGELOG.
This should also reduce potential failures in the
Yarn upgradeworkflow and vice-versa, so they don't block each other.Tested o fork: https://github.com/mrgrain/aws-cdk/actions/runs/5680204361
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license