-
### Describe the bug
Considering the newly released SurrealDB 2.0 it could be beneficial to rearrange the image container tags to follow semver specs.
Taking into example any other project, such…
-
- [ ] Use Github Actions to modify release semver when generating new packages nightly based on the following rules
- [ ] Increment MAJOR number when any commits tagged as MAJOR are detected
- [ ] I…
-
The OCI specification lacks a strict definition of valid tags.
I believe that image tags should support the full semver specification. To be clear, I am not saying all tags must be valid semver, I…
-
**Is your feature request related to a problem? Please describe.**
[isFeatureAvailable](https://github.com/grafana/grafana/blob/main/public/app/plugins/datasource/tempo/datasource.ts#L252) is used in…
-
Currently, every change here is published every day by GHA workflow: https://github.com/semver/semver.org/blob/gh-pages/.github/workflows/sync.yml
But it means every change _needs_ to bump up the s…
-
We should follow the following release format for docker images, inspired by minio https://hub.docker.com/r/minio/minio/tags
`RELEASE.2023-09-30T07-02-29Z`
Every release should have a correspond…
-
Most of the time, the version that is in package.json reflects the latest tag. However this is not the case when creating releases off of stable branches, e.g. the package version is `1.13.4` when th…
-
This may need further investigation before it can be addressed.
One benefit to having such a check would be allowing users to see when their project is relying on dependencies that do not communic…
-
-
## CVE-2022-25883 - High Severity Vulnerability
Vulnerable Libraries - semver-7.3.5.tgz, semver-6.3.0.tgz, semver-5.7.1.tgz
semver-7.3.5.tgz
The semantic version parser used by npm.
Library home p…