Say, the previous release was done by squashing the commits. And including BREAKING CHANGE text at the end of the squashed commit message which released version 2.0.0.
thereafter, a new patch release was done which published version 2.0.1.
After…
I'm currently using semantic-release for versioning of my react library.
https://github.com/semantic-release/semantic-release
Question:
Is it possible to generate the artifacts without publishing it?
For example, in my use case I would like to…
I'm working on an Angular Library and I'm trying to make the process of releasing as much automatic as I can. I've been researching different tools and I've seen several that are very helpful:
Commitizen for commit message format
Husky to enforce…
I have a react component project created with nwb. I'm using Travis and semantic-release to make the releases.
But now, when I publish a new version, the package published from Travis is almost empty, and only have three files: README, LICENSE and…
I'm new to GitHub Packages (or publishing NPM packages in general) and am trying to publish packages to my private repository using semantic release following this excellent blog post.
However, I'm running into issues authenticating with GitHub…
Update2: I spent way to many hours trying to make this work, it has been tiring and frustrating, I am now doing everything manually. I do the release manually and I publish the package locally with my terminal, as it works fine with no problem.
I…
we probably have a really specific case. We are using
Private NPM registry on Azure DevOps
Yarn v1
Semantic-Release Monorepo (containing multiple packages. I think if it would only be one package, it would be ok)
Everything works fine and as…
I am trying to automate publishing the SDKs for Python, Java, GO, and Node. My main goal is to make the CI run whenever a new PR is created against main branch that will:
bump the version in all files.
publish the new release to the related public…
I have teams I work with that love semantic-release, but often developers forget to put the commit message keywords in (e.g. fix, feat, perf). I understand this is something we need to hammer home or implement a pre-commit hook to require…
I have a repository that I am using as a template for semantic release:
release.yml
workflow:
rules:
- if: $CI_COMMIT_TAG
when: never
- if: $CI_COMMIT_BRANCH == "test"
when: always
- if: $CI_COMMIT_BRANCH == "main"
…
I'm (mis)using semantic-release when building a C++ application in a GitLab CI.
My config is quite minimal
.releaserc.json
{
"branches": ["main", "develop"],
"plugins": [
"@semantic-release/commit-analyzer",
"@semantic-release/gitlab",
…
I have an NPM package that up until now, I have been manually bumping the version in package.json and then my GitHub actions CI publishes.
I have now added semantic release with the following config but it keeps trying to update the package version…
My default branch is main and while merging it to main branch I am getting this error. I have added env for NPM_TOKEN and GH_TOKEN in vercel environment variable.
vercel.json
{
"$schema": "https://openapi.vercel.sh/vercel.json",
"buildCommand":…
I am currently try to auto publish my npm package to GitHub packages using semantic release with GitHub Actions. The package publishes successfully but when Installed, only the package.json file is found in the published package.
I have a build…