-
This is part of the series of proposals spanning out of the meta #16.
# String Versions
All localization systems have to facilitate the string changes as part of the project life cycle. While ad…
-
# Summary
Come up with a plan to handle breaking changes:
- appropriate semantic versioning
- do we want to maintain old versions for bug fix support or always move users to the latest version? W…
-
## Bug report
### What is the current behavior?
I've updated the release, because I needed to use a version of poetry compatible with the latest pyproject.toml standard.
I made the release …
-
**Modified by dietmarw on 2 Dec 2015 10:08 UTC**
We identified several potential “levels” of semantics. The first level was the idea that all libraries must use semantic versions syntax. This would …
-
## The problem
If one sets the matches value of semantic_release.branches.main.match property to "*", the --version command fails with an confusing error message.
```toml
[semantic_release.branch…
b0lle updated
1 month ago
-
In my experience, the [semantic versioning scheme](https://semver.org/) has proven quite useful and widespread. However, it mandates that version numbers MUST include a patch version (i.e. have three …
-
Could you document which version(s) of semantic UI (CSS) your library supports?
3noch updated
6 years ago
-
STR:
- Install 1.1.0-beta.2
- (Release 1.1.0)
- Go to Settings -> Updates
Expected:
- Shows new version available
Actual:
- "Your system is up to date"
It appears that the `compareSemver…
-
Due to how pre-releases are categorized in semantic versioning, for us to easily test CI builds after a new release is published we need to remember to increase the semantic version in some way (it ca…
-
something like v1.0.0
Given a version number MAJOR.MINOR.PATCH, increment the:
MAJOR version when you make incompatible API changes,
MINOR version when you add functionality in a backwards-compat…