Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merge 1.43.0 release back to the development branch after resolving conflicts #2929

Merged
merged 19 commits into from
Dec 23, 2020

Conversation

guarani
Copy link
Contributor

@guarani guarani commented Dec 23, 2020

This PR was needed because there are conflicts on the trunkdevelop branch here: #2909

To avoid pushing straight to trunk, a new branch is made here called merge_release_1.43.0_to_develop, develop is merged into it, conflicts are resolved, and this PR merges this to develop. This has the result of updating develop with the release that's in trunk.

To test

Check that the Gutenberg submodule ref points to WordPress/gutenberg@a454634, as described in #2909 (review).

PR submission checklist:

  • I have considered adding unit tests where possible.
  • I have considered if this change warrants user-facing release notes more info and have added them to RELEASE-NOTES.txt if necessary.

Copy link
Contributor

@ceyhun ceyhun left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM!

@guarani guarani merged commit 84825d6 into develop Dec 23, 2020
@guarani guarani deleted the merge_release_1.43.0_to_develop branch December 23, 2020 16:56
@guarani guarani added this to the 1.45 (16.6) milestone Jan 4, 2021
@guarani guarani mentioned this pull request Jan 4, 2021
2 tasks
@guarani guarani modified the milestones: 1.45 (16.6), 1.44 (16.5) Jan 4, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants