Some merged PRs not considered by semantic-release

[MikeMcC399]

Issue

When the following PRs were merged into the master branch, the release job in CircleCI failed to consider their contents. The information message was:

ℹ The local branch master is behind the remote one, therefore a new version won't be published.

5936243 ci(deps): update semantic-release to 24.2.3 (#944)
875b5dc ci: use node.js 22 in circleci mac job (#941)
1362fed ci: use node.js 22 in circleci windows jobs (#939)

• For instance, for PR ci: use node.js 22 in circleci windows jobs #939 before semantic-release was updated, and using the older version:

npm warn exec The following package was not found and will be installed: [email protected]
npm warn deprecated [email protected]: Renamed to read-package-up
[1:16:37 PM] [semantic-release] › ℹ  Running semantic-release version 23.1.1
[1:16:37 PM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "@semantic-release/npm"
[1:16:37 PM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "@semantic-release/github"
[1:16:37 PM] [semantic-release] › ✔  Loaded plugin "analyzeCommits" from "@semantic-release/commit-analyzer"
[1:16:37 PM] [semantic-release] › ✔  Loaded plugin "generateNotes" from "@semantic-release/release-notes-generator"
[1:16:37 PM] [semantic-release] › ✔  Loaded plugin "prepare" from "@semantic-release/npm"
[1:16:37 PM] [semantic-release] › ✔  Loaded plugin "publish" from "@semantic-release/npm"
[1:16:37 PM] [semantic-release] › ✔  Loaded plugin "publish" from "@semantic-release/github"
[1:16:37 PM] [semantic-release] › ✔  Loaded plugin "addChannel" from "@semantic-release/npm"
[1:16:37 PM] [semantic-release] › ✔  Loaded plugin "addChannel" from "@semantic-release/github"
[1:16:37 PM] [semantic-release] › ✔  Loaded plugin "success" from "@semantic-release/github"
[1:16:37 PM] [semantic-release] › ✔  Loaded plugin "fail" from "@semantic-release/github"
[1:16:39 PM] [semantic-release] › ✔  Run automated release from branch master on repository git+https://github.com/cypress-io/cypress-example-kitchensink.git
[1:16:39 PM] [semantic-release] › ℹ  The local branch master is behind the remote one, therefore a new version won't be published.

Analysis

• In PR ci: use node.js 22 in circleci windows jobs #939 there is no log entry that the branch was updated with the master branch before merging into the master branch.

Suggestion

Consider setting a branch protection rule for the master branch according to:

Require status checks before merging

with "Require branch to be up to date before merging" selected: