I am using the shareable config feature of semantic-release to create a re-usable configuration which will use the exec plugin to upload a file to S3. I would like the file path to include the name of the repository which creates the release and I…
I would like to achieve this using semantic release.
master: 1.1.0 (release1) ---- 1.1.1 (release2)--------
\
\
release1: \ ---- feat(Something): ---- 1.1.0-mr.0 --- feat(SomethingElse): --- 1.1.0-mr.1
So release/1 could be…
I have an issue with the GitHub action workflow that I have created for the purpose of automatically releasing versions of my NX monorepo. During the process, I encountered an issue when the workflow was executed, as shown below. I am using the…
I'm trying out "semantic-release" scenarios, and if I create a next branch and publish a breaking change on that branch, the branch triggers a version 2.0.0, which is good.
Now if I do a pull from the origin while I'm on the next branch, I get the…
We have semantic-release set up in our repo at work. Tech leads asking me to:
Let people merge to the main branch and it shouldn't trigger the release.
It requires to automatically creating releases at 5pm from the main branch (not triggered by…
When I merge my release candidate branch into my main brach i receive a 401 error.
I have a release candidate "rc" branch that is at 1.06. I am trying to merge that branch into my main branch "release" which is still at 1.0. I'm pretty new to using…
I have an NPM package I am trying to set up semantic release for so it will automatically deploy with a version bump.
I recently migrated from an old repo / npm package to a new one and since doing so semantic version wont create a new release for…
I've been upgrading our workflow to add an automatic version bump. The problem is that I accidentally added these steps with a typo in the .bumpversion.cfg file and from that moment, the workflow is sure that the releases start at tag 1.0.0. I've…
I am using semantic release for handling versioning in my repo. But recently i am facing issues when running the job. I have a beta branch where beta versions are released. But when the changes are added to beta semantic release runs and shows
The…
I am using semantic-release package for automatic versioning. I want to maintenance my old versions. But when i configure the semantic-release like below, consumers who are use old version can not install last update.They always have to specify…
When using semantic-release and doing beta pre-releases.
https://semantic-release.gitbook.io/semantic-release/usage/workflow-configuration#pre-release-branches
They say that if the last version on main is 1.0.0, if you push a breaking change to…
Article for reference
I can set up Github Actions but get stuck on GitHub Release; it says
Run npx semantic-release [semantic-release]: node version >=16 ||
^14.17 is required. Found…
I am trying to put release notes on the github summary.
Using the exec plugin, I echo the notes (nextRelease.notes) into a file (called .NOTES) and the content is then put on the workflow summary.
During the execution of a release, the notes are…
I have an Electron app that I want to publish with semantic-release.
I need to create a matrix in Github Action to build the app on different platforms:
strategy:
matrix:
os: [windows-latest, ubuntu-latest, macos-latest]
Now, if I run…