Update Slider to reflect changes immediately

[dratwas]

Fixes #2192
Gutenberg PR: WordPress/gutenberg#22421

To test:
1.

• open mobile app
• add spacer block
• open settings of the spacer block
• change the height of spacer - change should be visible while moving the slider

• add button block
• open settings of that button
• change the border-radius - change should be visible while moving the slider

PR submission checklist:

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

[peril-wordpress-mobile]

Wanna run full suite of Android and iOS UI tests? Click here and 'Approve' CI job!

[geriux]

Approved via WordPress/gutenberg#22421 (review)

Just one thing about the release notes.

[mchowning]

We're preparing to cut the 1.30 release branches now. Let's merge this ASAP or update the milestone to 1.31.

[dratwas]

Hey @mchowning, unfortunately, we had to revert the PR that fixed the issue with creating undo levels when using the slider. WordPress/gutenberg#22933

The issue is described here #2192 (comment)

I'm moving it to the milestone 1.31

[mchowning]

👋 @dratwas! We're close to merging the monorepo changes 🎉 , and we will be cutting the release branches as soon as the monorepo changes are merged to gutenberg-mobile. As a result, we may be cutting the 1.31 release branches earlier than normal.

Because every merge further delays the monorepo work (ends up requiring conflicts to be fixed and other work due to the monorepo feature branch and the squash policy in gutenberg), we want to cut the release branch with no further changes. For that reason, I'll bump this milestone to 1.32. Of course, if this has to make the 1.31 release, go ahead and move it back to the 1.31 milestone, and let me know. 🙇

[mchowning]

👋 @dratwas ! We're getting ready to cut the 1.32 release branch, so I'm bumping this to the 1.33 milestone. If this needs to make the 1.32 release though, go ahead and change the milestone back and try to get this merged as soon as possible. If you're trying to get this into the release, please also let us know in Slack. 🙇

[dratwas]

Hey @mchowning thanks for the heads up i need to wait for the wordpress-mobile/WordPress-Android#12144 with this one.

[SergioEstevao]

👋 @dratwas ! We're getting ready to cut the 1.33 release branch, so I'm bumping this to the 1.34 milestone. If this needs to make the 1.33 release though, go ahead and change the milestone back and try to get this merged as soon as possible. If you're trying to get this into the release, please also let us know in Slack. 🙇

[ceyhun]

👋 @dratwas ! We're getting ready to cut the 1.34 release branch, so I'm bumping this to the 1.35 milestone. If this needs to make the 1.35 release though, go ahead and change the milestone back and try to get this merged as soon as possible. If you're trying to get this into the release, please also let us know in Slack. 🙇

[ceyhun]

@dratwas heads up we'll be cutting the 1.35 release branch beginning of next week. Please try to get this merged by than or bump the milestone 🙇

[cameronvoell]

@dratwas heads up we'll be cutting the 1.35 release branch beginning of next week. Please try to get this merged by than or bump the milestone 🙇

Bumping milestone

[cameronvoell]

@dratwas not sure if this PR is needed for package.json updates, or if we can close it since I believe the gutenberg side is already merged and updated in gb-mobile develop. If you want to merge this one, I think merging in develop should fix CI (fix PR - #2571).

I'll cut the branches for 1.36 later in the day on Monday 8/31, see please merge before then if needed, thanks!

[dratwas]

Closing since these changes are merged already.