Closed Finii closed 7 months ago
The original problem statement seems wrong, as described in the readme:
We should move that in the release workflow anyhow, why is it in the npm workflow? I can not remember.
Ah now I know, to prevent a new readme after release started before release published. Fixing.
The workflow fails ... of course.
Have no time now, will fix that later this week. NPM publishing succeeded.
Forgot that the release is not on a branch :grimacing: