diff options
| author | Kian-Meng Ang <kianmeng.ang@gmail.com> | 2025-03-10 09:01:38 +0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2025-03-09 21:01:38 -0400 |
| commit | 51be3c341c2f1a2295d0ed22615d80581e86742c (patch) | |
| tree | e0b6f73756137c00fb55960c378e9d607add64b0 /CONTRIBUTING.md | |
| parent | a378c6d544ad43143939e2b247751279abec8019 (diff) | |
docs(fix): fix typos (#2344)
* docs(fix): fix typos
Found via `codespell -L fom,fo,wil,nd,wit` and `typos --hidden --format brief`
* docs(fix): regenerate docs
Signed-off-by: Dave Henderson <dhenderson@gmail.com>
---------
Signed-off-by: Dave Henderson <dhenderson@gmail.com>
Co-authored-by: Dave Henderson <dhenderson@gmail.com>
Diffstat (limited to 'CONTRIBUTING.md')
| -rw-r--r-- | CONTRIBUTING.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 3382b3d1..1ba0c607 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -22,7 +22,7 @@ If you think you've found a sensitive security issue, please e-mail me before op ## Versioning, API and Deprecation -I try to follow [Semantic Versioning 2.0.0](https://semver.org/spec/v2.0.0.html) as much as possible, and as such the version numbers attached to gomplate releases have _semantic meaning_. That is, patch-level releases (e.g. when going from 2.3.0 to 2.3.1) will only contain bug fixes and will not otherwise add or remove features, while minor-level releses (e.g. 2.3.0 to 2.4.0) will only contain new features and will not remove or make breaking changes to features, and major-level releases (e.g. 2.3.0 to 3.0.0) will contain breaking changes (either feature removals, renames, or significant behaviour changes). +I try to follow [Semantic Versioning 2.0.0](https://semver.org/spec/v2.0.0.html) as much as possible, and as such the version numbers attached to gomplate releases have _semantic meaning_. That is, patch-level releases (e.g. when going from 2.3.0 to 2.3.1) will only contain bug fixes and will not otherwise add or remove features, while minor-level releases (e.g. 2.3.0 to 2.4.0) will only contain new features and will not remove or make breaking changes to features, and major-level releases (e.g. 2.3.0 to 3.0.0) will contain breaking changes (either feature removals, renames, or significant behaviour changes). When making a change that'll require either a _minor_ or _major_ version bump upon release, the PR should be labeled with the `api/minor` or `api/major` labels. |