Merge extra enhancements landed in beta.4 branch into new rc.1 branch #273
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…y replace images without using the preg_match call.
…ace the same images.
…ources Replace images in frontend content without using an additional regular expression
felixarntz
added
[Type] Enhancement
eugene-manuilov
approved these changes
Mar 29, 2022
mitogh
approved these changes
Mar 29, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Per the decision in #253, we're going to ship
1.0.0-rc.1as next release rather than1.0.0-beta.4. I've therefore created a new branchrelease/1.0.0-rc.1fromtrunk(since everything currently intrunkalso makes sense to include there). The otherrelease/1.0.0-beta.4branch was created a bit early, and I suggest we merge the additional enhancements from it into this new branch and then delete it afterwards.cc @mitogh
All code here has already been reviewed and approved, so the approval here is just a formality.
Checklist
[Focus]orInfrastructurelabel.[Type]label.no milestonelabel.