Skip to content

chore: yarn upgrade dependencies requiring intervention - #18

Open
pahud wants to merge 1 commit into
mainfrom
automation/yarn-upgrade-dependencies-requiring-intervention
Open

chore: yarn upgrade dependencies requiring intervention#18
pahud wants to merge 1 commit into
mainfrom
automation/yarn-upgrade-dependencies-requiring-intervention

Conversation

@pahud

@pahud pahud commented Jul 15, 2026

Copy link
Copy Markdown
Owner

Ran npm-check-updates and yarn upgrade for the following dependencies:

@aws-cdk/asset-awscli-v1

Checkout this branch and run integration tests locally to update snapshots.

(cd packages/@aws-cdk-testing/framework-integ && yarn integ --update-on-failed)

See https://www.npmjs.com/package/@aws-cdk/integ-runner for more integ runner options.

@amazon-q-developer amazon-q-developer Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This PR upgrades @aws-cdk/asset-awscli-v1 from version 2.2.282 to 2.2.289, which is a patch-level update. The changes appear routine and follow semantic versioning practices for patch updates.

As noted in the PR description, ensure integration tests are run locally to verify compatibility and update any affected snapshots before merging.


You can now have the agent implement changes and create commits directly on your pull request's source branch. Simply comment with /q followed by your request in natural language to ask the agent to make changes.

@github-actions

Copy link
Copy Markdown

⚠️ This pull request description does not follow the correct template structure.

PRs without a linked issue will receive lower priority for review and merging. Please update the description to follow the PR template and include a line like Closes #123 in the Issue section. If no existing issue matches your change, create one first.

@pahud
pahud force-pushed the automation/yarn-upgrade-dependencies-requiring-intervention branch from e512a4c to 100d735 Compare July 22, 2026 14:25
@pahud
pahud force-pushed the automation/yarn-upgrade-dependencies-requiring-intervention branch from 100d735 to 5482b32 Compare July 29, 2026 14:29
Ran npm-check-updates and yarn upgrade to keep the `yarn.lock` file up-to-date.
@pahud
pahud force-pushed the automation/yarn-upgrade-dependencies-requiring-intervention branch from 5482b32 to 3840424 Compare August 5, 2026 14:29
@pahud
pahud force-pushed the main branch 4 times, most recently from 3608a7f to d249354 Compare August 14, 2026 01:01
@pahud
pahud force-pushed the main branch 2 times, most recently from 4cbcfe5 to f93ea41 Compare August 19, 2026 00:36
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants