-
In the past we struggled with SemVer compliance (See #140, #169, #200, #246).
Today I read about [`cargo-semver-checks`](https://github.com/obi1kenobi/cargo-semver-check) (also see the [article on…
-
I use `setuptools_scm` for versioning hg-git, with the `release-branch-semver` scheme, where I have release branches named e.g. `1.0.x` and `1.1.x`. When doing a stable release, I do it on the release…
-
If multiple prereleases exist, they may confuse each other.
Add test logic that ensures that only the relevant tags are used for the latest tag
-
On our repository we've been using the format `release-%major%.%minor%.%patch%` for our releases. I tried to introduce your action so we could auto tag and release instead of our current manual proces…
-
[Pre-releases are now supported](https://code.visualstudio.com/updates/v1_63#_pre-release-extensions), but they require a non-pre-release semantic version.
The official docs says that [_support for…
-
### Is there an existing issue for this?
- [X] I have searched the existing issues
### This issue exists in the latest npm version
- [X] I am using the latest npm
### Current Behavior
Package nam…
-
As Dotscience developers, we'd like all the parts of our product to use the same versioning/release process, so we don't need to remember two.
Therefore, we should make Dotmesh use the lightweight …
-
Hey 👋🏼
Thanks for your work on this project! Integrating it into some of our repositories over at https://github.com/cda-tum was pretty smooth sailing and works nicely. Consider this issue more a …
-
This is a minor nitpick but with semantic versioning in an SCM like git the standard advice says to name it `v${major}.${minor}.${patch}`
- https://semver.org/spec/v1.0.0.html#tagging-specification…
-
We have a mixed monorepo. There're some webapps served individually and some libs published to be reused.
I'm using a non-commit style to create tags with release note for each commit on master bra…