Hey @geriux, not sure if I am missing some context but usually the practice is that we update bundle files through the release process.

The release process for the v1.18.0 started yesterday so you can be sure that, if we merge this PR, spacer will be part of the new release bundle.

Hey @geriux, not sure if I am missing some context but usually the practice is that we update bundle files through the release process.

The release process for the v1.18.0 started yesterday so you can be sure that, if we merge this PR, spacer will be part of the new release bundle.

Yup, I updated the bundles so reviewers were able to test the Spacer block in the main apps before merging. It also was a good test as part of my onboarding to know how to generate bundles, etc =)

I'm not sure if there is a process for this, but I'll drop the bundle changes from the PR and keep the gutenberg ref change only.

@geriux the e2e tests seem to fail - can you check it's related to your changes?

I'll drop the bundle changes from the PR and keep the gutenberg ref change only

Sounds good 👍bundles are usually generated only on release branches, this one was needed just for testing purposes because we needed to verify Spacer block appearing in the block picker while metro is off.

@geriux the e2e tests seem to fail - can you check it's related to your changes?

It shouldn't be but I'll check, thanks!