‘needs-xxx-review’ label is not attached to the pull request that has passed all CI processes

[badmintoncryer]

Describe the bug

The ‘needs-community/maintainer-review’ label would be attached to the pull requests which had passed all CI processes but this feature is failed now.

Ex.1 needs-community-review label is not attached. #35246

Ex.2 needs-maintainer-review label is not attached. #34599

Regression Issue

• Select this option if this issue appears to be a regression.

Last Known Working CDK Library Version

No response

Expected Behavior

These labels are successfully attached.

Current Behavior

These labels are not attached in spite of passing all of CI processes.

Reproduction Steps

Create a new pull request and pass the all CI processes.

Possible Solution

No response

Additional Information/Context

No response

AWS CDK Library version (aws-cdk-lib)

Irrelevant

AWS CDK CLI version

Irrelevant

Node.js Version

Irrelevant

OS

Irrelevant

Language

TypeScript

Language Version

No response

Other information

No response

[related-issues-bot-for-aws]

Hi @badmintoncryer,

Thanks for reporting! While a member of the CDK team reviews this, we've identified this as a potential duplicate.

Potential Duplicate Issues

• prlint: assess needs review after codebuild job succeeds #30128: Both issues report the same problem where the PR linter fails to attach review labels ("needs-community-review" or "needs-maintainer-review") to PRs that have passed CI processes. Both expect the same behavior - automatic application of review labels after CI checks pass. They involve the same PR labeling mechanism with identical expected functionality where PRs should be reassessed after CI completion to apply the appropriate review labels.

This message was generated automatically to help connect related conversations and improve discoverability.

Please react with 👍 or 👎 to let us know if this response was helpful!

Thank you for helping improve CDK! 🙌

Related Issues

• prlint: a review label doesn't appear when a PR is approved if there are too many comments #31294
• community review workflow stuck with Action Required state #31870

[pahud]

Root Cause Analysis

The issue is a CodeBuild context name mismatch in the PR Linter configuration:

The Problem:

1. Expected CodeBuild Context: The PR linter in tools/@aws-cdk/prlint/constants.ts is configured to look for:

 export const CODE_BUILD_CONTEXT = 'AWS CodeBuild us-east-1 (AutoBuildv2Project1C6BFA3F-wQm2hXv2jqQv)';

2. Actual CodeBuild Context: The CI system is now using a different CodeBuild project with the context:

Actual Context (PR #35246 status):

{
  "context": "AWS CodeBuild us-east-1 (aws-cdk-github-actions-runner)",
  "state": "success"
}

Bringing this up to the team for review.