semantic-release | Fully automated version management and package publishing | DevOps library

 by   semantic-release JavaScript Version: 23.0.2 License: No License

kandi X-RAY | semantic-release Summary

kandi X-RAY | semantic-release Summary

semantic-release is a JavaScript library typically used in Devops applications. semantic-release has no bugs, it has no vulnerabilities and it has medium support. You can install using 'npm i travis-semantic-release' or download it from GitHub, npm.

:package::rocket: Fully automated version management and package publishing

            kandi-support Support

              semantic-release has a medium active ecosystem.
              It has 18038 star(s) with 1726 fork(s). There are 54 watchers for this library.
              There were 10 major release(s) in the last 6 months.
              There are 273 open issues and 1035 have been closed. On average issues are closed in 81 days. There are 44 open pull requests and 0 closed requests.
              It has a neutral sentiment in the developer community.
              The latest version of semantic-release is 23.0.2

            kandi-Quality Quality

              semantic-release has 0 bugs and 0 code smells.

            kandi-Security Security

              semantic-release has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
              semantic-release code analysis shows 0 unresolved vulnerabilities.
              There are 0 security hotspots that need review.

            kandi-License License

              semantic-release does not have a standard license declared.
              Check the repository for any license declaration and review the terms closely.
              Without a license, all rights are reserved, and you cannot use the library in your applications.

            kandi-Reuse Reuse

              semantic-release releases are available to install and integrate.
              Deployable package is available in npm.
              Installation instructions are not available. Examples and code snippets are available.

            Top functions reviewed by kandi - BETA

            kandi has reviewed semantic-release and discovered the below as its top functions. This is intended to give you an instant insight into semantic-release implemented functionality, and help decide if they suit your requirements.
            • Run the repository .
            • recursive function to find maintenance branches .
            • Takes an array of releases and returns a maximum version for the release .
            • Fetch a branch .
            • Formats the authorization url with git credentials .
            • Unshifts the notes in the project .
            • Logs errors and warnings
            • Generate prerelease specification .
            • Parse a plugin
            • Get a specific reference .
            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

            @open-sauced/semantic-release-conventional-config,🧪 GitHub actions usage
            JavaScriptdot img1Lines of Code : 69dot img1License : Permissive (MIT)
            copy iconCopy
            name: "Release container"
                  - main
                  - next
                  - next-major
                  - alpha
                  - beta
                  name: production
                  url:${{ github.repository }}/releases/tag  
            Travis example
            JavaScriptdot img2Lines of Code : 20dot img2License : Permissive (MIT)
            copy iconCopy
            # .travis.yml
                - ~/.npm
              - npm test
              - test
              - name: release
                if: branch = master AND type = push AND fork = false
                - stage: release
                  language: node_js
                  node_js: '10.18'  
            copy iconCopy
            language: node_js
              - 8
              - 6
              - 4
              - linux
              - osx
              - npm run semantic-release

            Community Discussions


            How to publish a release with semantic-release on GitHub?
            Asked 2022-Feb-22 at 13:40

            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



            Answered 2022-Feb-22 at 13:40

            As jonrsharpe pointed out, implementing the plugin semantic-release/github fixed my problem and tags and releases are now created automatically.



            Running into Nektos/Act error permission denied when running actions locally
            Asked 2022-Feb-11 at 07:01

            Pretty new to Nektos/act and in general running workflows locally and cant seem to find a solution to a permissions denied error when installing Node version 16. Here is the error I am running into when I run the following:




            Answered 2022-Feb-11 at 07:01

            Appears to be a bug with the recent release. I confirm that downgrading to 0.2.24 fixed this issue.




            Could not resolve peer dependency between my Angular app and my custom Angular library
            Asked 2022-Feb-10 at 15:05

            I have created this Angular library that I now want to use in my other Angular apps, but I seem to have trouble with my peer dependencies. I have tried fiddling around in my App's package.json, but couldn't seem to remove any of my errors.

            What I have tried (in that order) :

            • Removing node_modules
            • ng update
            • npm update
            • npm audit --fix
            • npm i
            • Recreating a new test app all together

            Here are the errors :



            Answered 2022-Feb-10 at 15:05

            This is not the issue with peer dependencies. This is more to do with version conflict. I guess you are using npm >=7 that's why you are getting this error:-

            As mentioned in the error log try the below command to fix the issue:-



            semantic-release does not update package.json of my Angular library
            Asked 2022-Feb-10 at 08:32

            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 quite sure how to do it... The version of my library does not seem to update. Here is my current Gitlab CI config :



            Answered 2022-Feb-10 at 08:32

            The problem was that I was not triggering a release with my commit messages. Once that was sorted out, the package.json updated normally.



            Universal typescript npm module
            Asked 2022-Feb-07 at 14:05

            I am modifying an existing library so it can be imported in typescript. I've boiled it down to a Minimal working example

            The requirements
            • To remain backwards compatible, the library needs to be importable with a simple

              It works. So far so good.

              In another typescript project

              Next, I created a simple typescript project that utilizes my library.

              File structure:



            Answered 2022-Feb-07 at 14:05

            I've figured it out. In my lib.ts I had to change the way I export my class:



            Semantic release not accepting GITLAB_TOKEN on gitlab private repository
            Asked 2022-Jan-21 at 01:20

            Here is the error log message:

            [3:40:55 PM] [semantic-release] › ✖ The command "git push --dry-run --no-verify https://gitlab-ci-token:[secure]@[repository-url].git HEAD:main" failed with the error message remote: You are not allowed to upload code. fatal: unable to access 'https://gitlab-ci-token:[secure]@[repository-url]/': The requested URL returned error: 403.

            I have a GITLAB_TOKEN set up in the repository settings with all the necessary permissions, but it seems it isn't even being used:

            Here is my .releaserc.json config:



            Answered 2022-Jan-20 at 20:45

            So in the end the problem was that I had to add the created GITLAB_TOKEN access token in Settings > CI/CD > Variables



            SHA of Tag Created by Semantic-Release
            Asked 2022-Jan-11 at 05:12

            We're updating our release workflow to use semantic-release, and I need to be able to grab the SHA of the latest tag, create a new branch with it, build our assets, commit them to that new branch.

            The action I'm using to create the branch, requires the SHA of the parent branch if you're building a branch based on something other than the branch the runs the workflow.

            So I have a couple actions to determine if the release is major, minor, or patch, and then will find the latest semver tag name. But I don't know how to get the SHA of this Ref.

            So far I have this:



            Answered 2022-Jan-11 at 05:12

            To answer your question:

            git log -1 --format="%H" REF-NAME

            REF-NAME here could be a tag, branch, or a commit ID, any of which the command will return the commit ID.

            Note though that you should be able to create a branch by just supplying the tag name without the commit ID.



            Is it possible to automate .Net assembly versioning using semantic-release?
            Asked 2021-Dec-31 at 12:45

            I have a C# solution containing a single project and multiple libraries using .Net 6. I'm using conventional commits (commitlint with husky) and want to use semantic-release to deploy the latest build as a ZIP file on Github based on the commit messages.

            The setup I tried for C# projects:

            • Install packages




            Answered 2021-Dec-31 at 12:45

            You could dry-run semantic-release before dotnet publish to fetch the version number of the release (using the @semantic-release/exec plugin). Then pass this fetched version number to dotnet publish:

            Add the @semantic-release/exec plugin to your npm install commands and adjust your .releaserc.json file to store the next release version (for example in an environment variable):



            How to update the package.json version using semantic-release/git?
            Asked 2021-Dec-29 at 12:28

            What I want to do

            Based on the FAQ


            I want to update the package.json version number on a new release.

            What I did

            • Create a new empty private Github repository for an organization temp with a and .gitignore for node
            • Clone the repository
            • Fix the first commit message via git rebase -i --root and change it to feat: initial commit
            • Create a package.json with the content


            Answered 2021-Dec-29 at 12:28

            Based on this issue


            you also need the npm module.

            • npm install @semantic-release/npm -D
            • add "private": true, to your package.json if you don't want to publish to npm
            • add the npm plugin to the release configuration file (the order matters)




            Is it possible to migrate Gitlab releases to a Github repository?
            Asked 2021-Dec-13 at 09:54

            I want to migrate all the releases from a Gitlab repository that is using semantic release to a Github repository.

            I can create new releases in the new Github repository starting from the last Gitlab repository, but I don't know how to transfer all Gitlab releases to Github, is this possible?



            Answered 2021-Dec-13 at 09:54

            There is no first-party feature for this in either GitLab or GitHub (when migrating to GitHub anyhow). Scripting it would be your best bet which using the GitLab and GitHub APIs.

            Gitlab releases API

            GitHub releases API reference


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


            No vulnerabilities reported

            Install semantic-release

            You can install using 'npm i travis-semantic-release' or download it from GitHub, npm.


            Usage Getting started Installation CI Configuration Configuration Plugins Workflow configuration Shareable configurationsExtending Plugins Shareable configurationRecipes CI configurations Git hosted services Release workflowDeveloper guide JavaScript API Plugins development Shareable configuration developmentSupport Resources Frequently Asked Questions Troubleshooting Node version requirement Node Support Policy
            Find more information at:

            Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items

            Find more libraries
          • npm

            npm i semantic-release

          • CLONE
          • HTTPS


          • CLI

            gh repo clone semantic-release/semantic-release

          • sshUrl


          • Stay Updated

            Subscribe to our newsletter for trending solutions and developer bootcamps

            Agree to Sign up and Terms & Conditions

            Share this Page

            share link

            Explore Related Topics

            Consider Popular DevOps Libraries


            by ansible


            by bregman-arie


            by dotnet


            by semantic-release


            by Carthage

            Try Top Libraries by semantic-release


            by semantic-releaseJavaScript


            by semantic-releaseJavaScript


            by semantic-releaseJavaScript


            by semantic-releaseJavaScript


            by semantic-releaseJavaScript