Setup release-plan

[SergeAstapov]

created using https://github.com/embroider-build/create-release-plan-setup

[villander]

I don't think we should switch our release workflow. it has been working well and I don't see any advantage in using the release plan over what we have in place @SergeAstapov @void-mAlex

[SergeAstapov]

@villander release-plan does bit more automation compared to release-it, e.g. release preview PR so worth the shot (if we can make it work reliably easily)

[void-mAlex]

I don't think we should switch our release workflow. it has been working well and I don't see any advantage in using the release plan over what we have in place @SergeAstapov @void-mAlex

the issue with the current release flow is that it's not possible, due to mainly no npm access to the package

the change to release-plan ensures that npm access can be given only as a GH secret and access managed on GH with correct perissions to merge, it also ensures the builds are correct and reproducible with no human error 'possible' in the process as the only thing it involves are correct pr titles and labels
at the same time we get more automation and control over the release and if there is something else we need release plan to do it's easier to upstream as long as we have the use case.

for those reasons but mainly the ability to centrally release are why we need this before we merge the rest

[villander]

thanks for the context @void-mAlex that makes sense now. We can move forward @SergeAstapov given the release has been a pain point to us requiring Chris to publish npm package every single time

[SergeAstapov]

Thank you @void-mAlex @mansona !