-
Hello Team,
We are facing an issue from this Monday where we are now unable to push our release on GitHub using postTarget attribute of version.
We are first using @jscutlery/semver:version exec…
-
Is there a possibility to work on proper versioning and release tags ? The last tag dates back to 2016 and it would help much upstream distros to have a regular release schedule.
-
Hi.
I am trying to automatically determine my semver tag on push to main instead of having to supply it. Unfortunately when doing this the change log is only using the latest commit, since I can…
-
### Issue Description
Right now new release of the SGrPython library are build und pushed locally by a developer. This leads to unwanted dependencies on some developers.
### Proposed Solution
Imp…
-
## Problem
There is an issue in the git client of the conventional changelog. If you have a commit that has multiple semver tags on it and one of the tags is an unstable version, the git client wil…
-
Hey @dominz88, thanks for this snap!
Recently I set up [CI for nushell](https://github.com/sed-i/nushell-snap/blob/main/.github/workflows/release.yml) ([post](https://forum.snapcraft.io/t/cross-compi…
-
Releases to date are all versioned `2.0.0-dev.*`, which suggests (to me, at least) they aren't meant for public or production use. The releases have been quite stable — I think we could start releasin…
-
-
Hi all :)
I'm opening this to talk about what we want our SemVer MAJOR release policy to be.
Right now, for v7, we've opted for the approach of "implement as many breaking changes then release v7"…
ephys updated
2 years ago
-
# Summary
https://github.com/argoproj/argo-cd/pull/17566 updated Argo CD to be able to compare semver tags. This allows us to use a constraint like `>=1.2.0` to select the latest git tag that meets…