feat: set up pre-release workflow #94
Conversation
jonkoops
force-pushed
the
semantic-release-beta
branch
from
017fea2
to
7307705
Compare
Signed-off-by: Jon Koops <[email protected]>
jonkoops
force-pushed
the
semantic-release-beta
branch
from
7307705
to
9c3f550
Compare
|
Looks like the failures here are some kind of bug likely due to older workflows, I've created #95 to upgrade everything and that seems to fix it. |
Those are probably showing up because of some settings in the PR merge settings/rules. I'll have a look. Actually, the test failure on node 14 seems legit. |
Looking at the logs I see it is using NPM 10, even though NPM 9 is installed explicitly. I am not quite sure why this is happening to be honest. |
It would be good to get this passing as well if possible. |
| with: | ||
| fetch-depth: 0 # fetch all history |
There was a problem hiding this comment.
Is this needed? Defaults should work.
There was a problem hiding this comment.
It needs to be there as semantic release needs to know the commit history, it it is omitted only the last commit is present. You can also see it in the example code.
| permissions: | ||
| contents: read # for checkout |
There was a problem hiding this comment.
Is this a global setting for any operation?
There was a problem hiding this comment.
Correct, this sets up the minimum permissions for the entire workflow. Individual jobs can then specify the permissions they need individually.
I'll check it out when I have some more time. Let's get #95 merged first just to make sure the actions or environment don't have anything to do with it. |
What kind of change does this PR introduce?
Did you add tests for your changes?
If relevant, did you update the documentation?
Summary
Sets up the release workflow with the latest conventions from semantic release. This includes a
betabranch for pre-releases and NPM provenance.Does this PR introduce a breaking change?
Nope.
Other information
None.