semantic-release automates package release workflow.
semantic-release automates package release workflow.
Links
Questions tagged [semantic-release]
161 questions
4
votes
1 answer
Semantic release not publishing correct folder
For the past few days, I'm trying to publish my package to github by using semantic-release. Unfortunately, I can't publish the correct folder as source code (zip) file in my npm package hosted on github.
My github action pipeline:
on:
push:
…
Giga Meta
- 299
- 2
- 16
4
votes
1 answer
Multiple pre-releases from any branch that follows a particular naming convention using semantic-release?
We’ve been using a branching strategy (previously along with release-it) like this:
main
Our production branch, of course.
release/DEV-123-branch-name
With our epics in Jira we’ve been creating an associated release/* branch. Any stories within…
Brandon Durham
- 7,096
- 13
- 64
- 101
4
votes
0 answers
There is a problem when creating a release with Git(Hub) branches
We're serving a Node.js application and operating branch policy on GitHub such as:
main: Production environment release base
develop: Development environment (beta) release base
Basically, we're writing some code on a new branch from the develop…
Eric Choi
- 41
- 2
4
votes
1 answer
How to publish a whole directory using Github Actions with the semantic-release Github plugin?
I want to publish a whole directory (the build directory) on a Github release using semantic-release but unfortunately it releases each build file as a single asset.
For reproduction:
I'm using the Vue CLI to generate a project vue create…
Question3r
- 2,166
- 19
- 100
- 200
4
votes
1 answer
How to add the build files as an asset to a release in Github?
I have a project based on Node/npm and use commitlint, husky and semantic-release. Whenever I push to the protected main branch I want to create a new release.
In Github I added the following workflow
name: Release on push on main
on:
push:
…
user17298649
4
votes
1 answer
semantic-release: fatal: tag 'vX.Y.Z' already exists
Trying to set up semantic-release/gitlab, I'm getting this in my GitLab logs,
Error: Command failed with exit code 128: git tag v1.0.0 2c30602010d7d9f26cc0880b988ff9de6405daa5
fatal: tag 'v1.0.0' already exists
at makeError…
Evan Carroll
- 78,363
- 46
- 261
- 468
4
votes
1 answer
GitHub - semantic-release release notes using all commits in PR
I would like to be able to have semantic-release gather all commit messages being merged from a separate branch into one release notes entry. Our workflow is as below:
all development commits are made to separate branches, using Angular commit…
Y.Y.
- 111
- 10
4
votes
3 answers
Deleted tags are present in Gitlab-CI
I'm using semantic-release for versioning. Whenever I push something to my branch, the CI (Gitlab) executes the semantic-release. My problem is that I pushed to my git branch, semantic-release created a release and created the tag (e.g. 1.0.0).…
Nrgyzer
- 783
- 1
- 14
- 38
4
votes
1 answer
semantic-release is configured to only publish from master
[16:07:15] [semantic-release] › ℹ Running semantic-release version 17.0.4
[16:07:18] [semantic-release] › ✔ Loaded plugin "verifyConditions" from "@semantic-release/npm"
[16:07:19] [semantic-release] › ✔ Loaded plugin "verifyConditions" from…
Андрей СТ
- 41
- 1
- 2
4
votes
1 answer
How to force a version in semantic release
I have a npm package that I need to release in npmjs.com but because I unpublished a previously wrong version now npmjs doesn't allow me to re-publish an artefact with the same version (it throws an error saying You cannot publish over the…
kioli
- 635
- 1
- 10
- 26
4
votes
1 answer
Semantic Release - Add more sections to auto-generated release notes
I've just finished setting up semantic-release for my node project and made the first release with it:
It seems that only commits with type fix or feat are added to the release notes... I want to be able to show improvement type as well.
Is there a…
Gee VB
- 183
- 3
- 8
4
votes
1 answer
semantic-release fails to publish to npm
I am using semantic-release npm module to do the releases in circle ci. I am getting following error
[semantic-release] [@semantic-release/npm] › ℹ Write version 1.0.0 to
package.json in /home/circleci/tmp npm ERR! Version not changed, might
…
It worked yesterday.
- 4,507
- 11
- 46
- 81
4
votes
1 answer
Handling nextRelease version in semantic release
so I have been reading the docs and kind of got a glimpse of
what I should do, but no real grasp of how I can do it.
Here is my problem:
- I am using semantic release to publish my package to npm
- I also have contract testing in place with Pact.
-…
Moustachiste
- 412
- 4
- 14
3
votes
2 answers
use different to master branch as release branch on semantic release
When Im trying to use another release branch for trigger a release with semantic release. Semantic release is telling me
This test run was triggered on the branch jose, while semantic-release is configured to only publish from master, therefore a…
Chekuda
- 31
- 1
- 2
3
votes
1 answer
Semantic-Release - pre-release version not incrementing for patch, minor or major version
Current behavior
This is a brand new project, so fresh versions etc.
Currently have a pre-release branch called "next", release branch called "stable", all features all worked on in our "development" branch and they have the correct feat(test): this…
Nicholas Devlin
- 31
- 1
- 2