search

chromaui / storybook-addon-pseudo-states

CSS pseudo-classes for Storybook
MIT License
90 stars 31 forks source link

Release v2 stable for Storybook v7 #69

Closed JReinhold closed 1 year ago

JReinhold commented 1 year ago

Version

Published prerelease version: v2.0.0-next.3

Changelog #### 💥 Breaking Change - Set Storybook deps to v7 [#68](https://github.com/chromaui/storybook-addon-pseudo-states/pull/68) ([@JReinhold](https://github.com/JReinhold)) - Convert to TypeScript and upgrade to Storybook 7 [#47](https://github.com/chromaui/storybook-addon-pseudo-states/pull/47) ([@ghengeveld](https://github.com/ghengeveld)) #### 🐛 Bug Fix - Fix media queries breaking rules override [#58](https://github.com/chromaui/storybook-addon-pseudo-states/pull/58) ([@filipw01](https://github.com/filipw01)) - Remove optional chaining in next [#70](https://github.com/chromaui/storybook-addon-pseudo-states/pull/70) ([@filipw01](https://github.com/filipw01) [@ghengeveld](https://github.com/ghengeveld) runner@fv-az491-751.is1xdb2m0b3ubcod5yxy40qnsg.phxx.internal.cloudapp.net [@kasperpeulen](https://github.com/kasperpeulen)) #### ⚠️ Pushed to `next` - Typo ([@JReinhold](https://github.com/JReinhold)) #### Authors: 5 - Filip Wachowiak ([@filipw01](https://github.com/filipw01)) - Gert Hengeveld ([@ghengeveld](https://github.com/ghengeveld)) - ghengeveld (runner@fv-az491-751.is1xdb2m0b3ubcod5yxy40qnsg.phxx.internal.cloudapp.net) - Jeppe Reinhold ([@JReinhold](https://github.com/JReinhold)) - Kasper Peulen ([@kasperpeulen](https://github.com/kasperpeulen))
filipw01 commented 1 year ago

@JReinhold Can we merge #58 and #67 first? These are 2 bugs that I've struggled with in the beta and I believe they should be included in the stable 2.0

JReinhold commented 1 year ago

Thanks for bringing this up @filipw01.

The main issue we're trying to solve here is to get v2 released to stable at the same time as Storybook 7.0.0 goes stable, so that when users install this addon with v7, they'll get the correct version automatically, and not v1 which won't be compatible.

Even though those are important bugs, they are not as big as no support for v7 at all. We can easily release a patch version soon after v2 with your fixes.