merge queue: embarking main (9fbb471) and #34790 together

[mergify]

❌ This pull request has failed checks. #34790 will be removed from the queue. ❌

Branch main (9fbb471) and #34790 are embarked together for merge.

This pull request has been created by Mergify to speculatively check the mergeability of #34790.
You don't need to do anything. Mergify will close this pull request automatically when it is complete.

Required conditions of queue default-squash for merge:

• status-success=build
• status-success=validate-pr
• status-success~=AWS CodeBuild us-east-1
• any of [🛡 GitHub branch protection]:
  • check-neutral = validate-pr
  • check-skipped = validate-pr
  • check-success = validate-pr
• any of [🛡 GitHub branch protection]:
  • check-neutral = AWS CodeBuild us-east-1 (AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv)
  • check-skipped = AWS CodeBuild us-east-1 (AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv)
  • check-success = AWS CodeBuild us-east-1 (AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv)
• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • fix(pipelines): ensure assets with same hash but different destinations are published separately #34790
• #approved-reviews-by>=1
  • fix(pipelines): ensure assets with same hash but different destinations are published separately #34790
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • fix(pipelines): ensure assets with same hash but different destinations are published separately #34790
• #changes-requested-reviews-by=0
  • fix(pipelines): ensure assets with same hash but different destinations are published separately #34790
• -approved-reviews-by~=author
  • fix(pipelines): ensure assets with same hash but different destinations are published separately #34790
• -closed
  • fix(pipelines): ensure assets with same hash but different destinations are published separately #34790
• -label~=(blocked|do-not-merge|no-squash|priority-pr)
  • fix(pipelines): ensure assets with same hash but different destinations are published separately #34790
• -merged
  • fix(pipelines): ensure assets with same hash but different destinations are published separately #34790
• -title~=(WIP|wip)
  • fix(pipelines): ensure assets with same hash but different destinations are published separately #34790
• base!=release

Required conditions to stay in the queue:

• #approved-reviews-by >= 1 [🛡 GitHub branch protection]
  • fix(pipelines): ensure assets with same hash but different destinations are published separately #34790
• #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
  • fix(pipelines): ensure assets with same hash but different destinations are published separately #34790
• any of [🛡 GitHub branch protection]:
  • check-success = validate-pr
    • fix(pipelines): ensure assets with same hash but different destinations are published separately #34790
  • check-neutral = validate-pr
    • fix(pipelines): ensure assets with same hash but different destinations are published separately #34790
  • check-skipped = validate-pr
    • fix(pipelines): ensure assets with same hash but different destinations are published separately #34790
• any of [🛡 GitHub branch protection]:
  • check-success = AWS CodeBuild us-east-1 (AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv)
    • fix(pipelines): ensure assets with same hash but different destinations are published separately #34790
  • check-neutral = AWS CodeBuild us-east-1 (AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv)
    • fix(pipelines): ensure assets with same hash but different destinations are published separately #34790
  • check-skipped = AWS CodeBuild us-east-1 (AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv)
    • fix(pipelines): ensure assets with same hash but different destinations are published separately #34790

---
previous_failed_batches: []
pull_requests:
  - number: 34790
...

[github-actions]

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.

[aws-cdk-automation]

The pull request linter fails with the following errors:

❌ The title prefix of this pull request must be one of "feat|fix|build|chore|ci|docs|style|refactor|perf|test|revert"

If you believe this pull request should receive an exemption, please comment and provide a justification. A comment requesting an exemption should contain the text Exemption Request. Additionally, if clarification is needed, add Clarification Request to a comment.

[aws-cdk-automation]

AWS CodeBuild CI Report

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

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