-
Notifications
You must be signed in to change notification settings - Fork 58
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
Release 1.112.0 #6597
Release 1.112.0 #6597
Conversation
@derekblank we usually perform the testing plan the week after the release. Not sure if you already covered this, although I don't see comments in this PR related to testing. Let me know if we should leave it unchecked. Thanks 🙇 ! |
In 5d9a47f, I noticed that some E2E tests failed: Test iOS on Device – Full iPhone
Test iOS on Device – Full iPad
I'm going to retry the tests but if they fail again, it would be great to investigate them further. |
They keep failing, so I'm going to take a deeper look. |
It's a bit subtle but I noticed that the images seem one pixel taller, this seems causing the first failure. I wonder if #6550 has impacted somehow the size. UPDATE: I confirmed that #6550 added 1 pixel. |
I presume that the extra pixel was unintended. However, since it doesn't produce a critical change to the editor, I'll proceed with updating the screenshots. @derekblank let me know if you'd rather remove the extra pixel. If so, we could update the screenshots again. Thanks 🙇 ! |
This is needed to reflect a minor change in the size of the image frame.
This is needed to reflect a minor change in the size of the image frame.
This case is the same as the one shared in #6597 (comment). The one-pixel size difference in the image frame makes the visual check to fail. I'll proceed to update the screenshots. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fluiddot The extra pixel is actually intended, but I didn't realize that the E2E screenshots would be that sensitive to detect such a small visual change. It makes sense, however, so thanks for updating the screenshots. We can keep them as-is. To provide more technical detail on the 1 pixel change, the extra pixel comes from a non-visible FastImage instance that acts as a preloader using its Also noting that @dcalhoun and I consider this change a progressive-enhancement interim fix while we explore longer-term solutions for the Image component as a group, and potentially moving away from FastImage due to lack of maintenance. |
🟢 Writing Flow checklist - Android
General
Rich Text Format
Splitting and merging |
🟢 Unsupported Block Editor - Android
|
🟢 Functionality Test Suite 2 - Android
DarkMode - 1
Group - 1
Buttons-1
Button-2
Button-3
Color Settings - 1Image - 1
Drag and Drop Blocks - 1
VideoPress - 2 |
🟢 Writing Flow checklist - iOS
General
Rich Text Format
Splitting and merging |
🟢 Unsupported Block Editor - iOS
|
🟡 Functionality Test Suite 3 - iOS
Gallery - 2
Gallery - 3MediaText - 3
Video ExampleVideo.movMediaText - 4Shortcode-1
Cover - 2
Video ExampleRPReplay_Final1707198268.MP4
Image - 2
I believe the Story tests are no longer relevant due to Stories being removed from the mobile apps. I added a Story block from web and confirmed it shows up as Unsupported in the mobile app: Story block - 1 |
Release for Gutenberg Mobile 1.112.0
Related PRs
Changes
Test plan
Once the installable builds of the main apps are ready, perform a quick smoke test of the editor on both iOS and Android to verify it launches without crashing. We will perform additional testing after the main apps cut their releases.
Release Submission Checklist
RELEASE-NOTES.txt
is updated with all the changes that made it to the release. ReplaceUnreleased
section with the release version and create a newUnreleased
section.gutenberg/packages/react-native-editor/CHANGELOG.md
is updated with all the changes that made it to the release. Replace## Unreleased
with the release version and create a new## Unreleased
.