semantic-release | semantic-release written in go | Continous Integration library

by go-semantic-release Go Version: v2.20.2 License: MIT

X-Ray Key Features Code Snippets Community Discussions(10)Vulnerabilities Install Support

kandi X-RAY | semantic-release Summary

semantic-release is a Go library typically used in Devops, Continous Integration, Docker applications. semantic-release has no bugs, it has no vulnerabilities, it has a Permissive License and it has low support. You can download it from GitHub, GitLab.

semantic-release written in go

Support

Quality

Security

License

Reuse

Support

semantic-release has a low active ecosystem.

It has 208 star(s) with 33 fork(s). There are 4 watchers for this library.

It had no major release in the last 12 months.

There are 10 open issues and 50 have been closed. On average issues are closed in 91 days. There are no pull requests.

It has a neutral sentiment in the developer community.

The latest version of semantic-release is v2.20.2

Quality

semantic-release has no bugs reported.

Security

semantic-release has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.

License

semantic-release is licensed under the MIT License. This license is Permissive.

Permissive licenses have the least restrictions, and you can use them in most projects.

Reuse

semantic-release releases are available to install and integrate.

Installation instructions are not available. Examples and code snippets are available.

Top functions reviewed by kandi - BETA

kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of semantic-release

Get all kandi verified functions for this library.

semantic-release Key Features

No Key Features are available at this moment for semantic-release.

semantic-release Examples and Code Snippets

No Code Snippets are available at this moment for semantic-release.

Community Discussions

Trending Discussions on semantic-release

How to automatically version npm package in Azure DevOps (without triggering new pipeline)?

Starting from existing project with semantic-release to publish package NOT starting at 1.0.0

Applying semver on mono-repo node js projects

Setup @semantic-release for considering 'refactor' commits in the CHANGELOG

Cannot run semantic-release-cli setup for GitHub action

How to get release notes from Semantic Release output using grep command

How to grant permission for semantic-release to push code to master

How to solve permission problems when using GitLab CI Runner with Docker and non-root user?

Extract version number of string

How to upload an app to the Play Store for the second time? you already have one with version code 1 error

QUESTION

How to automatically version npm package in Azure DevOps (without triggering new pipeline)?

Asked 2021-Jun-04 at 02:36

What we're trying to do

We are using Azure Pipelines (azure-pipelines.yml) to automate ci/cd. Part of our configuration completes the versioning of our project for publishing to Azure Artifacts. We're also trying to configure this to update the existing version number in package.json without triggering a new pipeline in Azure DevOps.

This is the relevant section for our azure-pipelines.yml file:

...

ANSWER

Answered 2021-Jun-04 at 02:36

You can add another script task to push back to your devops git repo. But firstly, you need to add checkout step and set the persistCredentials to true to authenticate the git command. See below example:

Source https://stackoverflow.com/questions/67811509

QUESTION

Starting from existing project with semantic-release to publish package NOT starting at 1.0.0

Asked 2021-May-08 at 22:47

I have a private npm package that is currently published to npm. The maintainer before me did not consider automated versioning, and the version is 1.0.58.

I have installed semantic-release and a small GitHub app that can be found here: https://github.com/zeke/semantic-pull-requests

My Github Action is setup properly, because when I push to main, the process goes through and reach the publishing step. However, the tags that are created started at 1.0.0, then 1.0.1, etc.

I tried creating a tag manually on the main branch at the latest merge, that tag is v1.0.58, but when I publish again, the tag that is created is still 1.0.2, etc. As such, I get an error message that says I can't publish "over" the current version.

How do I go the 1.0.59 with a fix:... commit?

Thanks everyone!

...

ANSWER

Answered 2021-May-08 at 22:47

Forgot to post solution...

It seems Semantic Pull Requests did not have a proper starting point as the initial tag was created after it was linked to the repository. Uninstalling Semantic Pull Requests, adding the latest tag (corresponding to current version of published npm package) manually and reinstalling Semantic Pull Requests caused to process to go through flawlessly with semantic-release.

Source https://stackoverflow.com/questions/67274294

QUESTION

Applying semver on mono-repo node js projects

Asked 2021-Apr-05 at 21:47

I have used npx semantic-release for tagging projects in GitHub. I am currently working on a project that uses a mono-repo layout, something like:

mono-repo

api
web
mobile

I'd like to generate tags/releases separated each per component. I am not quite sure about how the tagging mechanism should work in this case. I was thinking about addiing logic to identify which component has been updated and generate a tag prefixing the component name like mobile-1.0.1, api-1.2.1, etc... Does anybody have previous experience working on something similar?

I was also thinking about creating a separate repo, each per component and from there everything will be easier to manage, any advice is appreciated.

...

ANSWER

Answered 2021-Apr-05 at 21:47

It seems the way to go it's lerna. I found out this library pretty useful in these cases. https://github.com/lerna/lerna/tree/main/commands/version

If you guys are using any other different approach, I'd like to know about any other alternative

Source https://stackoverflow.com/questions/66959620

QUESTION

Setup @semantic-release for considering 'refactor' commits in the CHANGELOG

Asked 2021-Feb-25 at 09:42

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 release:

...

ANSWER

Answered 2021-Feb-25 at 09:42

If anyone finds this useful: we need to config "@semantic-release/release-notes-generator" for considering other keywords besides feat and fix including these dicts:

Source https://stackoverflow.com/questions/66337234

QUESTION

Cannot run semantic-release-cli setup for GitHub action

Asked 2021-Feb-02 at 06:42

When running npx semantic-release-cli setup with GitHub Actions for my public repository https://github.com/henrycity/movie-browser-frontend, I got this error

...

ANSWER

Answered 2021-Feb-02 at 06:42

The issue is fixed in version 5.4.3.

Source https://stackoverflow.com/questions/65787779

QUESTION

How to get release notes from Semantic Release output using grep command

Asked 2021-Jan-24 at 14:43

I am trying to automate the release of software using semantic-release. Everything is working fine. I run this command npx semantic-release --no-ci --dry-run and get the following output in the terminal

...

ANSWER

Answered 2021-Jan-24 at 08:32

With GNU sed.

Source https://stackoverflow.com/questions/65868106

QUESTION

How to grant permission for semantic-release to push code to master

Asked 2020-Dec-12 at 12:52

I'm using semantic-release to automatically define the next version, update package.json and push to git. However, I'm facing a problem where it stop me from direct pushing to master.

I'm using GitLab.

my release.config.js

...

ANSWER

Answered 2020-Dec-12 at 12:52

1.In GitLab you have to explicitly set the script to push to Git. For this you need to create a token and pass it to your CI via env variable.

In example, see how we do it in our integration project via setting GIT_PUSH_TOKEN - here: https://gitlab.com/taleodor/sample-helm-cd

and the actual ci yaml code here: https://gitlab.com/taleodor/sample-helm-cd/-/blob/master/.gitlab-ci.yml (lines 25-30).

2.Yes, direct push on version bump is common.

Source https://stackoverflow.com/questions/65212359

QUESTION

How to solve permission problems when using GitLab CI Runner with Docker and non-root user?

Asked 2020-Nov-24 at 13:32

I am using a GitLab CI Runner with Docker.

My dockerfile looks as follows:

...

ANSWER

Answered 2020-Nov-24 at 13:32

I finally solved the issue through:

Removing USER ciuser from the Dockerfile so that the runner is starting with the root user again
Changing the test command as follows sudo -H -u ciuser bash -c "npm install && npm run test:cobertura" so that it is executed by the ciuser as it is described in this post.

Source https://stackoverflow.com/questions/64983984

QUESTION

Extract version number of string

Asked 2020-Oct-05 at 20:32

I'm trying to get the version number out of a string which looks like this:

...

ANSWER

Answered 2020-Oct-05 at 20:32

You could use Busybox awk:

Source https://stackoverflow.com/questions/64215365

QUESTION

How to upload an app to the Play Store for the second time? you already have one with version code 1 error

Asked 2020-Sep-05 at 18:35

I was sucessfully uploading my apk to the play store in branch internal testing and suddently, it started to refuse my new apk with this error:

...

ANSWER

Answered 2020-Aug-29 at 03:38

It's a problem with version code. Play store detects previous or same version code in your code. So Just Replace your version code with 360010306. After that may resolve your issue.

Source https://stackoverflow.com/questions/63643108

Community Discussions, Code Snippets contain sources that include Stack Exchange Network

Vulnerabilities

No vulnerabilities reported

Install semantic-release

You can download it from GitHub, GitLab.

Support

Beta release support empowers you to release beta, rc, etc. versions with semantic-release (e.g. v2.0.0-beta.1). To enable this feature you need to create a new branch (e.g. beta/v2) and check in a .semrelrc file with the following content:. If you commit to this branch a new incremental pre-release is created everytime you push. (2.0.0-beta.1, 2.0.0-beta.2, ...).

Find more information at: