-
Notifications
You must be signed in to change notification settings - Fork 0
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Semantic Release Config #4
Comments
for 2. I suppose using github packages for hosting the |
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. |
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? |
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:
The text was updated successfully, but these errors were encountered: