Skip to content

Commit 4f7ca64

Browse files
BryanBryan
authored andcommitted
Tweak release notes, update documentation
1 parent 2e39f04 commit 4f7ca64

File tree

2 files changed

+9
-3
lines changed

2 files changed

+9
-3
lines changed

docs/content/release_notes.md

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,5 +1,11 @@
11
<!-- releases_open -->
22

3+
## 5.0.1
4+
**Functionally identical to 4.1.1. Major version bumped in strict compliance with [semver](https://semver.org/) standards**
5+
6+
* Any breaking change should be a new major version (read more [here](https://semver.org/#if-even-the-tiniest-backwards-incompatible-changes-to-the-public-api-require-a-major-version-bump-wont-i-end-up-at-version-4200-very-rapidly)).
7+
* A minor version with breaking changes should be re-released as a major version (read more [here](https://semver.org/#what-do-i-do-if-i-accidentally-release-a-backwards-incompatible-change-as-a-minor-version)).
8+
39
## 4.1.1
410
**Refactor price formatting and parsing. As a result, breaking changes may have been introduced.**
511

docs/content/releases/5.0.1.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,4 @@
1-
**Functionally the same aw 4.1.1. Major version released in strict compliance with (semver)[https://semver.org/] standards**
1+
**Functionally identical to 4.1.1. Major version bumped in strict compliance with [semver](https://semver.org/) standards**
22

3-
* Any breaking change should be a new major version (read (here)[https://semver.org/#if-even-the-tiniest-backwards-incompatible-changes-to-the-public-api-require-a-major-version-bump-wont-i-end-up-at-version-4200-very-rapidly]).
4-
* A minor version with breaking changes should be re-released as a major version (read (here)[https://semver.org/#what-do-i-do-if-i-accidentally-release-a-backwards-incompatible-change-as-a-minor-version]).
3+
* Any breaking change should be a new major version (read more [here](https://semver.org/#if-even-the-tiniest-backwards-incompatible-changes-to-the-public-api-require-a-major-version-bump-wont-i-end-up-at-version-4200-very-rapidly)).
4+
* A minor version with breaking changes should be re-released as a major version (read more [here](https://semver.org/#what-do-i-do-if-i-accidentally-release-a-backwards-incompatible-change-as-a-minor-version)).

0 commit comments

Comments
 (0)