is a merge commit, go back to the PR page–-we don't want merge commits, we want the actual commits. However, if this does not show a merge commit, it means that the PR was squash-merged. In that case, patch directly to the backport branch if appropriate.) Building test binaries After the backport PR has been merged into the release-x.y branch, update your local clone of Julia, then get the SHA of The last thing we want to do to the branch is to adjust the version number. To do this, submit a PR against release-x.y that edits the VERSION file to remove -pre from the version number. Once that's

is a merge commit, go back to the PR page–-we don't want merge commits, we want the actual commits. However, if this does not show a merge commit, it means that the PR was squash-merged. In that case, patch directly to the backport branch if appropriate.) Building test binaries After the backport PR has been merged into the release-x.y branch, update your local clone of Julia, then get the SHA of The last thing we want to do to the branch is to adjust the version number. To do this, submit a PR against release-x.y that edits the VERSION file to remove -pre from the version number. Once that's

is a merge commit, go back to the PR page–-we don't want merge commits, we want the actual commits. However, if this does not show a merge commit, it means that the PR was squash-merged. In that case, patch directly to the backport branch if appropriate.) Building test binaries After the backport PR has been merged into the release-x.y branch, update your local clone of Julia, then get the SHA of The last thing we want to do to the branch is to adjust the version number. To do this, submit a PR against release-x.y that edits the VERSION file to remove -pre from the version number. Once that's

is a merge commit, go back to the PR page–-we don't want merge commits, we want the actual commits. However, if this does not show a merge commit, it means that the PR was squash-merged. In that case, patch directly to the backport branch if appropriate.) Building test binaries After the backport PR has been merged into the release-x.y branch, update your local clone of Julia, then get the SHA of The last thing we want to do to the branch is to adjust the version number. To do this, submit a PR against release-x.y that edits the VERSION file to remove -pre from the version number. Once that's

is a merge commit, go back to the PR page–-we don't want merge commits, we want the actual commits. However, if this does not show a merge commit, it means that the PR was squash-merged. In that case, patch directly to the backport branch if appropriate.) Building test binaries After the backport PR has been merged into the release-x.y branch, update your local clone of Julia, then get the SHA of The last thing we want to do to the branch is to adjust the version number. To do this, submit a PR against release-x.y that edits the VERSION file to remove -pre from the version number. Once that's

is a merge commit, go back to the PR page—we don't want merge commits, we want the actual commits. However, if this does not show a merge commit, it means that the PR was squash-merged. In that case, patch directly to the backport branch if appropriate.) Building test binaries After the backport PR has been merged into the release-x.y branch, update your local clone of Julia, then get the SHA of The last thing we want to do to the branch is to adjust the version number. To do this, submit a PR against release-x.y that edits the VERSION file to remove -pre from the version number. Once that's

is a merge commit, go back to the PR page–-we don't want merge commits, we want the actual commits. However, if this does not show a merge commit, it means that the PR was squash-merged. In that case, patch directly to the backport branch if appropriate.) Building test binaries After the backport PR has been merged into the release-x.y branch, update your local clone of Julia, then get the SHA of The last thing we want to do to the branch is to adjust the version number. To do this, submit a PR against release-x.y that edits the VERSION file to remove -pre from the version number. Once that's

is a merge commit, go back to the PR page–-we don't want merge commits, we want the actual commits. However, if this does not show a merge commit, it means that the PR was squash-merged. In that case, patch directly to the backport branch if appropriate.) Building test binaries After the backport PR has been merged into the release-x.y branch, update your local clone of Julia, then get the SHA of The last thing we want to do to the branch is to adjust the version number. To do this, submit a PR against release-x.y that edits the VERSION file to remove -pre from the version number. Once that's

is a merge commit, go back to the PR page–-we don't want merge commits, we want the actual commits. However, if this does not show a merge commit, it means that the PR was squash-merged. In that case, patch directly to the backport branch if appropriate.) Building test binaries After the backport PR has been merged into the release-x.y branch, update your local clone of Julia, then get the SHA of The last thing we want to do to the branch is to adjust the version number. To do this, submit a PR against release-x.y that edits the VERSION file to remove -pre from the version number. Once that's

is a merge commit, go back to the PR page–-we don't want merge commits, we want the actual commits. However, if this does not show a merge commit, it means that the PR was squash-merged. In that case, patch directly to the backport branch if appropriate.) Building test binaries After the backport PR has been merged into the release-x.y branch, update your local clone of Julia, then get the SHA of The last thing we want to do to the branch is to adjust the version number. To do this, submit a PR against release-x.y that edits the VERSION file to remove -pre from the version number. Once that's