Skip to content

chore: npm-check-updates && yarn upgrade#34378

Merged
mergify[bot] merged 1 commit intomainfrom
automation/yarn-upgrade
May 9, 2025
Merged

chore: npm-check-updates && yarn upgrade#34378
mergify[bot] merged 1 commit intomainfrom
automation/yarn-upgrade

Conversation

@aws-cdk-automation
Copy link
Copy Markdown
Collaborator

Ran npm-check-updates and yarn upgrade to keep the yarn.lock file up-to-date.

@aws-cdk-automation aws-cdk-automation added auto-approve contribution/core This is a PR that came from AWS. dependencies This issue is a problem in a dependency or a pull request that updates a dependency file. labels May 7, 2025
@aws-cdk-automation aws-cdk-automation requested review from a team May 7, 2025 03:38
@github-actions github-actions bot added the p2 label May 7, 2025
@codecov
Copy link
Copy Markdown

codecov bot commented May 7, 2025

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 83.99%. Comparing base (ce7b307) to head (1b32bec).

Additional details and impacted files
@@           Coverage Diff           @@
##             main   #34378   +/-   ##
=======================================
  Coverage   83.99%   83.99%           
=======================================
  Files         121      121           
  Lines        6934     6934           
  Branches     1164     1164           
=======================================
  Hits         5824     5824           
  Misses        999      999           
  Partials      111      111           
Flag Coverage Δ
suite.unit 83.99% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components Coverage Δ
packages/aws-cdk ∅ <ø> (∅)
packages/aws-cdk-lib/core 83.99% <ø> (ø)
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@aws-cdk-automation aws-cdk-automation force-pushed the automation/yarn-upgrade branch 2 times, most recently from c792936 to 907bdd7 Compare May 7, 2025 15:19
@moelasmar moelasmar closed this May 7, 2025
@moelasmar moelasmar reopened this May 7, 2025
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented May 7, 2025

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 7, 2025
@aws aws unlocked this conversation May 7, 2025
@samson-keung
Copy link
Copy Markdown
Contributor

samson-keung commented May 7, 2025

Following integ tests failed:

@aws-cdk/aws-eks-v2-alpha: Failed: /codebuild/output/src1698213287/src/github.com/aws/aws-cdk/packages/@aws-cdk/aws-eks-v2-alpha/test/integ.eks-auto.js
@aws-cdk/aws-redshift-alpha: Failed: /codebuild/output/src1698213287/src/github.com/aws/aws-cdk/packages/@aws-cdk/aws-redshift-alpha/test/integ.cluster-maintenance-track-name.js

It is due to the recommended value of the @aws-cdk/aws-lambda:createNewPoliciesWithAddToRolePolicy feature flag got changed in the integ-runner:

aws/aws-cdk-cli@4bd6149#diff-cc2aa6328f725cd5a81d9ded74633857d38594c65a715e3411b80ec52ca5cdacR68

To avoid this from happening again, I made a PR to set the feature flag explicitly inside the integ test file: #34385

Edit: I changed my direction. I noticed that many snapshots were impacted due to the recommended value change. Instead of going through each integ test to set the the FF explicitly, I decided to upgrade the integ-runner AND simply update the snapshots because I don't believe that the recommended value will change again, so not really worth going into every impact integ test to add the explicitly value.

mergify bot pushed a commit that referenced this pull request May 8, 2025
### Issue # (if applicable)

N/A

### Reason for this change

The integ tests changed in this PR are failing the yarn upgrade job: #34378

This is because recommended value of the `createNewPoliciesWithAddToRolePolicy` feature flag changed in the `integ-runner` package: 

aws/aws-cdk-cli@4bd6149#diff-cc2aa6328f725cd5a81d9ded74633857d38594c65a715e3411b80ec52ca5cdacR68

So making this PR specifically for upgrading `@aws-cdk/integ-runner` and updating the snapshots required by it.

### Description of changes

Upgraded `@aws-cdk/integ-runner`, then updated the snapshots

### Description of how you validated changes

There is no actual code change to CDK constructs.

Checked the snapshots and see expected changes resulted from feature flag value being changed.

### Checklist
- [x] My code adheres to the [CONTRIBUTING GUIDE](https://github.com/aws/aws-cdk/blob/main/CONTRIBUTING.md) and [DESIGN GUIDELINES](https://github.com/aws/aws-cdk/blob/main/docs/DESIGN_GUIDELINES.md)

----

*By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license*
@aws-cdk-automation aws-cdk-automation force-pushed the automation/yarn-upgrade branch 2 times, most recently from c397e66 to 1b32bec Compare May 8, 2025 21:37
Ran npm-check-updates and yarn upgrade to keep the `yarn.lock` file up-to-date.
@aws-cdk-automation aws-cdk-automation force-pushed the automation/yarn-upgrade branch from 1b32bec to bbe6cbb Compare May 9, 2025 01:36
@aws-cdk-automation
Copy link
Copy Markdown
Collaborator Author

AWS CodeBuild CI Report

  • CodeBuild project: AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv
  • Commit ID: bbe6cbb
  • Result: SUCCEEDED
  • Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository

@mergify
Copy link
Copy Markdown
Contributor

mergify bot commented May 9, 2025

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).

@mergify mergify bot merged commit c50cb87 into main May 9, 2025
10 checks passed
@mergify mergify bot deleted the automation/yarn-upgrade branch May 9, 2025 02:05
@github-actions
Copy link
Copy Markdown
Contributor

github-actions bot commented May 9, 2025

Comments on closed issues and PRs are hard for our team to see.
If you need help, please open a new issue that references this one.

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 9, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

auto-approve contribution/core This is a PR that came from AWS. dependencies This issue is a problem in a dependency or a pull request that updates a dependency file. p2

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants