Ivan Sanz Carasa

## Workaround until this is fixed properly: Beware! this hacks the global CSS scope to target parent elements! ```tsx // hack for .mdx backgrounds addDecorator((story, context) => { const defaultBackgroundColorKey...

@dmackerman https://storybook.js.org/docs/react/writing-stories/decorators#global-decorators

any updates on this?

I tried multiple approaches to "exclude" some values **before storing** but they weren't reliable due to HMR and other angular internals, including custom serialization/deserialization. I did successfully manage to run...

it would be ideal to be able to exclude only certain parts of the store too (per-store `beforeStore(obj: any) => any` function?)

any update on this?

hey, im running into this issue with a multi-version-policy project. Any progress?

in my case, running `rush version --bump -b master` bumps every single package. It doesn't matter if its used as a `devDependency` or not, it bumps every package with a...

found the cause: I never ran a proper bump+publish against master in that repo and it was detecting changes as it was the "first" one. After doing the initial bump+publish...

Hey @ziofat , are you using a nextBump in the version policies or not? When no `nextBump` is speficied, all the projects that use the policy get updated together, think...