do not rely on <style scoped="true">

[drzraf]

The currently generated markup looks like:

<div class="wp-block-cp-timeline-content-timeline-block Cool-Content-Timeline">
<div class="cool-timeline-block-b238fb3a-989b-4379-8fae-61af5ad138f2">
<style scoped="true">
.cool-timeline-block-b238fb3a-989b-4379-8fae-61af5ad138f2 .cool-vertical-timeline-body .story-time p{color: #333;}
 ... [lot of CSS] ...
</style>
<div class="cool-vertical-timeline-body both-sided left">
<div class="cool-timeline-block-list">...

But any change to the style.scss (like one that recently introduced linear-gradient(to bottom, rgba(230, 230, 230, 0) 0%, #D91B3E 10%) break the generated markup identity.

While such a thing is something difficult to avoid, inlining the CSS is calling for problems and should rather not be done.

[drzraf]

I think having a Github red tag "forward-compatibility" would be important to keep track of issues/change that intend to avoid future block breakages.