-
### Bug description
I push a tag `release/v2.0.1` to [my forked node module repository](https://github.com/jspark-gigworks/skipper-gcstorage). And then add dependency in package.json of…
-
## Observed Behavior
Based on previous releases, it seems the tags `v16.0.0` and `v17.0.0` were not yet pushed to Git. The links from the CHANGELOG currently don't resolve correctly as they require…
-
-
# Context
The current version of semver (2.x) has some known limitations mainly because we designed it as an Nx executor.
Here are some examples:
- performance issues as we have to run the execut…
-
It seems if this action has to generate a default tag it fails
```
Run SOLIDSoftworks/semver-tags@v1.5.3
Generating version regex pattern
Generated pattern: ^hatch-test-suite-v(\d+)\.(\d+)\.(\d+…
-
Thanks for updating powerline-rust!
I'd love to learn what changes have taken place by glancing at https://github.com/cirho/powerline-rust/releases
-
Hi, it would be great if the repository occasionally tagged a version, since the API changes frequently. For instance, knowing that you have code working with tag 0.1.0 means you can re-install that v…
-
https://osv.dev/vulnerability/GSD-2021-1000677
The "Affected versions" and the GIT "Affected ranges" range values are available. But providing the SEMVER "Afected ranges" too, will help with the en…
-
Ideas (need specs):
``` shell
git semver --init
git semver --commit
git semver --push
git semver --tag
```
-
I'm using scoop, a package manager for Windows, I wrote manifests for Thorium. I enjoy it so much.
I'm have problems automating getting recent releases.
In previous releases, I obtain `version` from…