-
Currently dsm requires the version input to be an exact version string. as in "3.0.5" will work but "3.0" wont resolve to the latest patch of the version. This is partly due to a lack of available ind…
-
| Metadata | |
| -------- | --- |
| Owner(s) | @obi1kenobi |
| Team(s) | [cargo](https://github.com/rust-lang/cargo) |
| Goal document | [2024h2/cargo-semver-checks](https://rust…
-
The latest published stable tag on Docker Hub is [v4.39-9772-beta](https://hub.docker.com/layers/softethervpn/vpnserver/v4.39-9772-beta/images/sha256-98da8ab479bda750a548d6e3c4aaf803018d97bd02e6a8dd93…
-
Writing this to encourage discussion of two issues I hope to solve with a single PR:
1. There is no way to tell whether a version string is a SemVer v1, 2 or whatever is next string.
2. There ha…
-
Did you know I wrote this? It can help you ensure tags and branches in your repo are setup correctly to ensure proper versioning
https://github.com/jessehouwing/actions-semver-checker
-
In a pipeline that I am simply trying to bump a semver file. If the resource is
```
- name: semver-version
type: semver
source:
driver: gcs
bucket: lf-semver-version
key: VERS…
-
It is a recommended practice in docker to create layers with only the required files so that docker can properly calculate whether that layer can be skipped (through the build cache) in case the files…
-
## CVE-2022-25883 - High Severity Vulnerability
Vulnerable Libraries - semver-7.0.0.tgz, semver-7.3.5.tgz, semver-6.3.0.tgz, semver-5.7.1.tgz
semver-7.0.0.tgz
The semantic version parser used by n…
-
Need to develop a process with circle.ci to deploy semver versions of each lambda function. Ideally driven by git tags --tag v1.0.0
-
The github and docker/OCI has done something interesting in terms of naming read-only snapshots of content, which is to name each one with the cryptographic checksum of its content. Such a name isn't …