-
This would be better, dynamic releases will prevent wheels being uploaded to PyPI which are not on tagged releases.... (e.g. how long are we on v0.0.1)?
Here is also the time to take a stand on v…
-
ORT Server project currently uses a commit convention that looks like [Conventional Commits](https://www.conventionalcommits.org/en/v1.0.0/), but the convention does not semantically adhere to Convent…
-
We build charts for multiple hyperscalers and they sometimes have same version but differs with plus sign (GCP, AWS ..).
Like here we have two "other-chart" with same version but different hypersca…
-
To ensure that the CLI code expectations match the deployed infra.
-
### 🔍 Search Terms
`semantic versioning`
### ✅ Viability Checklist
- [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [X] This wouldn't change the runtime behavior of…
-
There are changes between 1.8.0 and 1.10.0 that break API compatibility. A minor version change is supposed to be backward compatible with 1.9.0 and 1.8.0.
**Reporter**: [Vlad Rozov](https://issues.a…
-
Perhaps future releases could use semantic versioning (http://semver.org/) so I can include a pre-release modifier such as "1.0.0-rc.1-SNAPSHOT". Here's a potential implementation:
``` scala
import s…
-
As per http://semver.org - I think this should be a given, although it probably isn't vitally important yet but once we get to a conceptual 0.1.0 it'll probably start to matter. Right now we're 0.0.1 …
-
Does your project use the Semantic Versioning system? (semver.org) Because if it does, you should already be at 1.0.0-; one of my Ruby projects has your gem as one of its dependencies. It would be muc…
-
**Describe the bug**
I'm using go client library (`/pkg/promtail/client`) instead of promtail to push log entries to Loki.
After updating Loki to v2.0.0 I cannot use go client library in projects w…