Semantic Release Config

[Gijsdeman]

The semantic release workflow should have constent release accross all repositories, instead of every repository having to define their own .releaserc.json config file.

I think the best way of achieving this is using the extends flag, as plugins cannot be set directly using flags only. However, for this we need:

1. A shareable configuration, for this, see Extend repository to include more shared configs js-configs#5
2. A way to publish the shared configurations, as this is required by the workflow. If only for a few files, possibly consider simply publishing to npm (as there is nothing particularly interesting released). Otherwise, look into how to publish packages privately.

[JustSamuel]

for 2. I suppose using github packages for hosting the .releaserc.json config?

[Gijsdeman]

I think that should work. In that instance we also have to add a workflow for releasing packages in GitHub.

Has this been discussed earlier at ABC meetings? I recall this being brought up for PDF-generator earlier. Not that we make the executive decision to do this now, and then have to move to another registry later.

[JustSamuel]

It kinda works, but not really, sementic release doesn't seem to download the preset / package and crashes. Maybe you have more luck.

edit: now that the shared config is published on npm, couldn't we simply just use that in the release workflow? just add an extra step + a flag to not overwrite it?