Issue
Semantic-release does not auto-release the already pre-tagged versions to github-releases. This means it does not work for the versions, which were already tagged before setting up semantic-release on the repo.
My sample GitHub repo with…
We were using GitLab release job to create releases whenever a tag is manually created, and we have already few tags/releases created that way, now we are moving to semantic-release to create releases for each commit to release branch, now when we…
I'm using semantic-release with saitho/semantic-release-backmerge.
The branch structure looks like this: release <- beta <- alpha The branches alpha, beta are pre-release branches and release is the stable branch.
The usual flow works fine:
commits…
I noticed that when using semantic-release/commit-analyzer plugin in gitlab ci, if there is a "/" in the commit message this breaks semantic release resulting in the following "error":
[7:28:38 AM] [semantic-release]…
I'm running a semantic-release job in a GitLab pipeline, it works great but only for my user (I configured it). No one else seems able to trigger a release, even if I merge their code. No errors, everything seems to run smoothly. I'm assuming…
I am developing a handful of WordPress projects on Gitlab and I would like to use semantic-release to automatically manage releases. To that end I'm trying to accomplish a few additional things:
Update and commit applicable version strings in the…
I am trying to publish my releases with semantic-release. Everything has worked well but the tool so far only generated tags rather than an actual GitHub Release.
My .releaserc
{
"branches": "main",
"plugins": [
[
…
I have this Angular library uploaded to a package registry that I created on Gitlab. I've already been able to upload my library successfully to this registry using the CI. I now want to implement semantic versionning to this library, but I'm not…
i am using semantic release with gitlab. I have added a job in ci for running semantic release which seems to run normally for normal number of commits but when i ran it on a branch with around 1500 commits it failed
Analyze commits run and then it…
I want to do something like this,
["@semantic-release/exec", {
"prepareCmd": "echo hello ${HOME};"
}],
And then run this CI job with an environmental variable? Is there a method of making this work in semantic-release?
I am using github actions for my project and to release I am using semantic release, Once semantic release releases the version Is it possible to forward that version to next steps?
release:
runs-on: ubuntu-latest
steps:
- name:…
I am creating a GitHub Actions workflow to build and publish npm packages to GitHub Packages. The repo is a monorepo with several packages, so I am using the semantic-release-monorepo tool. However, the step to publish is failing and I can't figure…
When running a check and release on CircleCI, the process started to fail on the release stage using semantic_release. It had been working fine for months.
The error message was:
[3:24:45 AM] [semantic-release] › ✖ An error occurred while running…
I am looking at implementing semantic-release in my GitLabCI build process, for a C++ application. However I'm concerned about potential race conditions.
Firstly, if two builds are running concurrently, both with the same kind of version increment…
Using @semantic-release I'd like to consider refactor changes for both, triggering a new release and write down in the CHANGELOG.md file.
So far, I've included refactor commits at "@semantic-release/commit-analyzer" so they are triggering a patch…