There are visual regression tests (a.k.a ui-tests) running on Chromatic for PRs opened on the tokens and vue-components packages of WiKit.
If these tests detect changes CI fails. If those changes are intentional one has to go to Chromatic and manually review and approve the visual differences, then restart the CI jobs.

Upon merging the PR we run CI again and consequently, the ui-tests are also run again.
Surprisingly, the fact that those changes were reviewed and approved when the PR was open doesn't matter, because Chromatic still considers them unreviewed and makes the CI fail on master. One has to go and approve them again etc.

According to the Chromatic docs that shouldn't be the case, see https://www.chromatic.com/docs/test#merge

WiKit uses Chromatic's cli in its GitHub actions. Instead, we want to use the official Chromatic GitHub Action as described in their docs, see https://www.chromatic.com/docs/github-actions
We think this will improve our workflow and get rid of the problems described above.