GitVersion
semantic-release
Our great sponsors
GitVersion | semantic-release | |
---|---|---|
7 | 43 | |
2,269 | 15,714 | |
1.6% | 2.2% | |
9.5 | 7.7 | |
3 days ago | 7 days ago | |
C# | JavaScript | |
MIT License | - |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
GitVersion
-
How do you track which version of microservice is deployed on a stage at any given point
Iām not sure about in Bitbucket, but our pipeline has installed GitVersion which ups the build version based on SemVer. https://gitversion.net/docs/ We have a HealthCheck endpoint to return this version.
-
Automating release notes with conventional commits
I know that GitVersion exists, which I think can automatically calculate the version number for me. But it's not entirely clear to me that it will do this. Also it doesn't seem to have a nbgv set-version equivalent that will just create a tag based on the calculated version number.
-
Kuberentes CI/CD
Kind of like you mention though, I tend to still create a build script using gitversion then just have the GitHub Action kick off the script. I find value in being able to create artifacts on a developer machine so having a simple script to run makes that as painless as possible and when I last looked a year or so ago there wasn't a good way of running GitHub Actions on your development machine.
-
Constant merge conflicts on csproj files
Self promotion: I made Verlite for this purpose, tho something like GitVersion might be more suitable for your workflow.
- New to cloud CI infrastructure (Bitbucket Pipelines in my case). What is the proper way to make a release?
-
Artifact/Package versioning
We use gitversion to generate semver based on commit height. https://github.com/GitTools/GitVersion
-
What build tool(s) do people use for their applications?
GitHub - GitTools/GitVersion: From git log to SemVer in no time
semantic-release
-
Automate npm publishing with GitHub Actions, proper changelog, and release notes
Unlike Conventional Commits and semantic-release, we let the developer choose the release type (major, minor, patch) and the time at which the package is released.
-
How to split Gatsby Build and Deploy GitHub actions
You could configure your actions to run on new tags (I highly recommend semantic release or similar) on the main branch to publish to GH releases, then on new tags on the prod branch, deploy from the release archive.
-
š”ļø This is how we maintain & release Secured Software on Github š¤
Then to release software we rely on semantic-release to implement a solid Semantic Versioning scheme and get a
-
How to Write a Great Git Commit Message
I like the conventional commit style [0]. You may have seen these in open source repos or used them at work. They look like
feat: support new line chart
fix: update props for new line chart
chore: bump dependency version
What's also cool is there are tools (semantic release) that will then handle automatically publishing and/or creating a new version of your module based on these commits using on the commit type (feat, fix, chore etc) to determine how to bump the version [1].
-
semantic-release VS release - a user suggested alternative
2 projects | 23 Apr 2022
-
How to automate change log and release creation
We're just in the process of implementing automated releases (following semantic versioning concepts) on every push to the main branch of our terraform module using semantic-release . It supports releases, changelogs, and has plugins for GitHub actions and that makes it really easy to integrate into the pipeline if you're keen.
-
semver: v1 vs v1000
The easiest way to enforce proper semver is by using tools like semantic-release and force major version bump based on keyword detection in the commit log (like "breaking change").
-
Is there an easy way to version between dev, rc and main branches with Go?
Judging from a quick skim of https://semantic-release.gitbook.io/semantic-release/ and https://github.com/semantic-release/semantic-release it doesn't look like there's any reason you couldn't use it on a go project. You'd have to install node in your dev and CI environments, but otherwise this should work.
-
Template for creating a typescript Hardhat-based repository for EVM Smart Contract development
Uses semantic-release and commitlint for a streamline CI
-
First steps in semantic versioning
semantic-release
What are some alternatives?
standard-version - :trophy: Automate versioning and CHANGELOG generation, with semver.org and conventionalcommits.org
release-drafter - Drafts your next release notes as pull requests are merged into master.
NUKE - š The AKEless Build System for C#/.NET
commitlint - š Lint commit messages
tsdx - Zero-config CLI for TypeScript package development
cz-cli - The commitizen command line utility. #BlackLivesMatter
LibGit2Sharp - Git + .NET/Mono = ā¤
semver - Semantic Versioning Specification
GitLink - Making .NET open source accessible!
GitExtensions - Git Extensions is a standalone UI tool for managing git repositories. It also integrates with Windows Explorer and Microsoft Visual Studio (2015/2017/2019).
gradle-git-versioner - A Gradle plugin to automatically version a project based on commit messages and semantic versioning principles
keel - Kubernetes Operator to automate Helm, DaemonSet, StatefulSet & Deployment updates