-
Lets discuss the specification for the semantic versioning schema for packages here.
-
tag project without "v" to be compliant with semantic versioning, used by SPM.
Thanks.
-
instead of "2022.10" -> "0.3.0"
-
Description: It appears that the update from version 0.4.2 to 0.4.3 introduced a breaking change regarding the location of the CurrencyMismatch class. Specifically, code that previously imported Curre…
-
### Environment
SaaS (https://sentry.io/)
### Steps to Reproduce
1. Have events from two different releases with semantic versioning
2. Search by `release.version` with multiple values
### Expecte…
-
It would be preferable to use semantic versioning of all of the images rather than just a single integer version number. The challenge is that there are multiple images being built from the same repo…
-
When upgrading a cross-built project from Scala 2.13.14 to 2.13.15, there are some dependency errors reported by `versionPolicyReportDependencyIssues`. See for example here: https://github.com/durban/…
-
### Description
Dear Gittyup Developers,
I have noticed an inconsistency in the version tagging within the releases section that could potentially confuse users trying to track changes or unders…
-
With the introduction of the GenericMemory type and the revamping of Array implementation, the interface for embedding in C has changed in breaking ways. As someone who has built and distributed a [fr…
-
### Problem Statement
Breaking changes without proper versioning
### Proposed Solution
Usage of Semantic Versioning as mentioned in https://semver.org/
### Additional Context
If sem ver…