-
Notifications
You must be signed in to change notification settings - Fork 4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: npm-check-updates && yarn upgrade #28434
Conversation
9eb3e50
to
d0f7cf7
Compare
0ffefa6
to
32a48d6
Compare
@Mergifyio update |
☑️ Nothing to do
|
32a48d6
to
afe97ad
Compare
@Mergifyio update |
✅ Branch has been successfully updated |
The update on eslint is causing the following error: ``` @aws-cdk/spec2cdk: 165:3 error An array of Promises may be unintentional. Consider handling the promises' fulfillment or rejection with Promise.all or similar, or explicitly marking the expression as ignored with the `void` operator @typescript-eslint/no-floating-promises ``` This PR has been separated out from [28434](#28434) because there are other failures. I am splitting these out to make clear which code is fixing which issue. ---- *By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
186ffef
to
e74abcb
Compare
e74abcb
to
5a4be49
Compare
5a4be49
to
6ad62b6
Compare
➡️ PR build request submitted to A maintainer must now check the pipeline and add the |
6ad62b6
to
e5f6eb4
Compare
Ran npm-check-updates and yarn upgrade to keep the `yarn.lock` file up-to-date.
e5f6eb4
to
cfbcce2
Compare
… automation/yarn-upgrade
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). |
Ran npm-check-updates and yarn upgrade to keep the
yarn.lock
file up-to-date.