auro-button: Updating to 6.3.3 breaks headless chrome tests

[diana-wang]

Describe the bug

I tried updating from 6.2.0 to 6.3.3, but this broke the headless chrome integration tests. Nothing else was changed

I would not expect all those tests to break simply by updating the version for auro-button.

The tests still work when updating to 6.3.2, so it seems to be something specifically with the 6.3.3 release. I'm unsure if there's another change that I'm supposed to be making in Component Hanger, or a dependency I'm missing.

To Reproduce

Here is the pipeline with the tests failing: Component Hanger Build

I don't think there's an easy way to reproduce it with just auro-button. The easiest way is to set up Component Hanger repository and run the tests locally.

[geoffrich]

I think I know what the issue is here. For now, it seems like you can work around it by installing the following commands (I tested this with the hangar locally):

npm i lit-element@latest
npm i lit-html@latest
npm dedupe

After that, I was able to successfully run the Headless Chrome tests.

[geoffrich]

The root cause is an update to the button's dependencies that required a higher version of lit-html than was installed in the component hangar. There were then 2 versions of lit-html, resulting in the broken button you saw above. See da4edec

I think we can fix this by lowering the required version of lit-html. @blackfalcon I'll be submitting a PR shortly.

[diana-wang]

Sweet, thank you @geoffrich! I'll use that for now. Once auro-button is updated I'll update to the newer version with the fix.

[AuroDesignSystem]

🎉 This issue has been resolved in version 6.3.4 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[geoffrich]

I confirmed that the new version fixes the Component Hangar tests on my local box.