Skip to content

Merge releases/v4 into releases/v3#4034

Merged
mbg merged 12 commits into
releases/v3from
backport-v3.37.3-e4fba868f
Jul 22, 2026
Merged

Merge releases/v4 into releases/v3#4034
mbg merged 12 commits into
releases/v3from
backport-v3.37.3-e4fba868f

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 22, 2026

Copy link
Copy Markdown
Contributor

Merging e4fba86 into releases/v3.

Conductor for this PR is @mbg.

Contains the following pull requests:

Please do the following:

  • Ensure package.json file contains the correct version.
  • Add a commit to this branch to resolve the merge conflicts in the following files:
    • lib/entry-points.js
  • Rebuild the Action locally (npm run build) and push any changes to the built output in lib as a separate commit named exactly Rebuild.
  • Ensure another maintainer has reviewed the additional commits you added to this branch to resolve the merge conflicts.
  • Ensure the CHANGELOG displays the correct version and date.
  • Ensure the CHANGELOG includes all relevant, user-facing changes since the last release.
  • Check that there are not any unexpected commits being merged into the releases/v3 branch.
  • Ensure the docs team is aware of any documentation changes that need to be released.
  • Approve running the full set of PR checks if you have not pushed any changes.
  • Approve and merge this PR. Make sure Create a merge commit is selected rather than Squash and merge or Rebase and merge.

@github-actions
github-actions Bot requested a review from a team as a code owner July 22, 2026 05:38
@github-actions github-actions Bot added the size/XS Should be very easy to review label Jul 22, 2026
@mbg
mbg merged commit 4187e74 into releases/v3 Jul 22, 2026
234 checks passed
@mbg
mbg deleted the backport-v3.37.3-e4fba868f branch July 22, 2026 06:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size/XS Should be very easy to review

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants