Note that even though this is technically a breaking change, every change is a breaking change. The question is really how likely is this to break people.
The chances that people rely on capitalization for version precedence seems highly unlikely.
Also, SemVer applies to libraries, not necessarily specifications. Though I would agree that a library based on SemVer would probably want to increment the major version possibly putting it out of sync with the version of this spec.
Software is messy, isn't it?
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.
## 📋 Pull Request Information
**Original PR:** https://github.com/semver/semver/pull/276
**Author:** [@haacked](https://github.com/haacked)
**Created:** 10/3/2015
**Status:** ❌ Closed
**Base:** `master` ← **Head:** `case-sensitivity`
---
### 📝 Commits (3)
- [`478b9f0`](https://github.com/semver/semver/commit/478b9f054adc9f58a6d247967851a05041ac883f) Fixes #176 by clarifying that versions are case insensitive
- [`c886078`](https://github.com/semver/semver/commit/c8860782584a9160ec60c60d847b31b5daa13a1d) Updated to 2.1.0 instead of 2.0.1 per feedback.
- [`bdc10c2`](https://github.com/semver/semver/commit/bdc10c2865d43409e1c6524114069b50cf22105e) Clarify that versions are case-insensitive
### 📊 Changes
**1 file changed** (+14 additions, -7 deletions)
<details>
<summary>View changed files</summary>
📝 `semver.md` (+14 -7)
</details>
### 📄 Description
Fixes #176
Continued from #177
Note that even though this is technically a breaking change, _every_ change is a breaking change. The question is really how likely is this to break people.
The chances that people rely on capitalization for version precedence seems highly unlikely.
Also, SemVer applies to libraries, not necessarily specifications. Though I would agree that a library based on SemVer would probably want to increment the major version possibly putting it out of sync with the version of this spec.
Software is messy, isn't it?
---
<sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
📋 Pull Request Information
Original PR: https://github.com/semver/semver/pull/276
Author: @haacked
Created: 10/3/2015
Status: ❌ Closed
Base:
master← Head:case-sensitivity📝 Commits (3)
478b9f0Fixes #176 by clarifying that versions are case insensitivec886078Updated to 2.1.0 instead of 2.0.1 per feedback.bdc10c2Clarify that versions are case-insensitive📊 Changes
1 file changed (+14 additions, -7 deletions)
View changed files
📝
semver.md(+14 -7)📄 Description
Fixes #176
Continued from #177
Note that even though this is technically a breaking change, every change is a breaking change. The question is really how likely is this to break people.
The chances that people rely on capitalization for version precedence seems highly unlikely.
Also, SemVer applies to libraries, not necessarily specifications. Though I would agree that a library based on SemVer would probably want to increment the major version possibly putting it out of sync with the version of this spec.
Software is messy, isn't it?
🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.