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

Merging main into 3.1-branch #637

Merged
merged 34 commits into from
Dec 20, 2023
Merged

Merging main into 3.1-branch #637

merged 34 commits into from
Dec 20, 2023

Conversation

andergmartins
Copy link
Contributor

Description

Benefits

Possible drawbacks

Applicable issues

Checklist

  • I have created a specific branch for this pull request before committing, starting off the current HEAD of development branch.
  • I'm submitting to the development, feature/hotfix/release branch. (Do not submit to the master branch!)
  • This pull request relates to a specific problem (bug or improvement).
  • I have mentioned the issue number in the pull request description text.
  • All the issues mentioned in this pull request relate to the problem I'm trying to solve.
  • The code I'm sending follows the PSR-12 coding style.

Replaced the char "@" by the char "&" to avoid using a char used by
npm for namespaces.
The main reason for moving to 6.1 is the fact we are using some of the
block editor components instead of introducing a new dependency of a
3rd party library, or creating components from scratch (in the JS side).
@andergmartins andergmartins self-assigned this Dec 20, 2023
@andergmartins andergmartins merged commit 2595348 into 3.1-branch Dec 20, 2023
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.

None yet

1 participant