build(deps): bump versions

[driskull]

build(deps): bump versions

[jcfranco]

🌮 🎉

[paulcpederson]

@eriklharper will this fix #1121 ?

[eriklharper]

@eriklharper will this fix #1121 ?

Doubt it. Ionic still has not addressed this underlying bug with relocating default slotted content in scoped components: ionic-team/stencil#2801.

Based on recent discussions I've been having about labelling form components, I think we should deprecate built-in label support in calcite-radio-button (and any other component that is currently doing this like calcite-checkbox) and have users supply their own label instead. Because both calcite-radio-button and calcite-label components are scoped and use default <slot />s, this issue could still persist inside calcite-label even after the built-in labelling support is removed from said components, but this would simplify them and remove the need for a fix on Ionic's end.

As far as how to handle the Stencil bug that is still affecting calcite-label, a possible solution would be to turn calcite-label back into a shadowed component, but then require the user to pass their own <label> tag into the default slot so that calcite-label can style it and keep the label available for form and accessibility on the document.

The crux of this Stencil bug is that it is difficult to replicate slot functionality for non-shadow DOM components because manual dom manipulation is required, which interferes with VDOM tools, which are designed to strictly control the DOM structure.