[mrgrain]

On release, we check for every package if a new release should be made. We do this by checking if any new feat or fix commits have been made in the package itself or any of it declared dependencies. By design, this is nothing but a crude approximation. But so far has been mostly good enough.

We've now discovered an edge case where sometimes unrelated files can change as part of a feat or fix (likely unintentionally) and thus causing a release where it shouldn't. This PR fixes that by excluding these patterns.

Checklist

• This change contains a major version upgrade for a dependency and I confirm all breaking changes are addressed
  • Release notes for the new version:

---

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

[github-actions]

Dependency Review

✅ No vulnerabilities or license issues or OpenSSF Scorecard issues found.

Scanned Files

None

[maintainer-for-aws]

Automated review

A maintainer will still review this — treat the notes below as a starting point.

📌 Commit 3ed8e85

This chore reduces pointless package releases in the CDK Toolkit monorepo. The releasable-commits check scans git history for feat/fix commits under a package and its dependencies; when such a commit only touches meta/generated files it still cuts a needless release. The fix adds a global set of git pathspec exclusions (:!THIRD_PARTY_LICENSES, :!.github, :!.projen) in .projenrc.ts, and the six regenerated .projen/tasks.json files carry the matching mechanical edit, consistently and in sync with the source. The change is release-automation plumbing only and touches no shipped CDK code or runtime behavior; it is low-risk. One minor observation: the :!.github exclusion resolves to a non-existent package-local path and is effectively a no-op, noted inline.

🔴 0 blocking · 🟡 0 recommended · ⚪ 1 optional

Files with findings (1)

File	Findings
.projenrc.ts	⚪ 1

---

Generated automatically. React 👍 or 👎 to tell us whether this review helped, so we can improve these reviews.

[maintainer-for-aws]

See the review summary comment for the overview; the notes below are inline.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 92.08%. Comparing base (fee6951) to head (3ed8e85).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #2110   +/-   ##
=======================================
  Coverage   92.08%   92.08%           
=======================================
  Files          83       83           
  Lines       13246    13246           
  Branches     1886     1886           
=======================================
  Hits        12197    12197           
  Misses       1011     1011           
  Partials       38       38           

Flag	Coverage Δ
suite.unit	92.08% <ø> (ø)

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

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

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