From 5087b490286d3a1652cdb008aa9d4e742a30cd65 Mon Sep 17 00:00:00 2001 From: shiraz Date: Thu, 18 Dec 2025 18:24:56 -0500 Subject: [PATCH] feat: add experiment type --- content/next/index.md | 7 ++++++- content/v1.0.0/index.md | 7 ++++++- 2 files changed, 12 insertions(+), 2 deletions(-) diff --git a/content/next/index.md b/content/next/index.md index 7e0f1119..d0482fa0 100644 --- a/content/next/index.md +++ b/content/next/index.md @@ -35,7 +35,7 @@ consumers of your library: A BREAKING CHANGE can be part of commits of any _type_. 1. **INITIAL STABLE RELEASE:** a commit that has a footer `INITIAL STABLE RELEASE:`, or appends `!!` after the type/scope, and introduces a new `MAJOR` even on versions `< 1.0.0`, denoting the promotion from a pre-release version `0.y.z` to `1.0.0`. 1. _types_ other than `fix:` and `feat:` are allowed, for example [@commitlint/config-conventional](https://github.com/conventional-changelog/commitlint/tree/master/%40commitlint/config-conventional) (based on the [the Angular convention](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines)) recommends `build:`, `chore:`, - `ci:`, `docs:`, `style:`, `refactor:`, `perf:`, `test:`, and others. + `ci:`, `docs:`, `style:`, `refactor:`, `perf:`, `test:`, `experiment:`, and others. 1. _footers_ other than `BREAKING CHANGE: ` or `INITIAL STABLE RELEASE: ` may be provided and follow a convention similar to [git trailer format](https://git-scm.com/docs/git-interpret-trailers). @@ -98,6 +98,11 @@ docs: correct spelling of CHANGELOG feat(lang): add polish language ``` +### Commit message with experiment type +``` +experiment: try new caching strategy for API responses +``` + ### Commit message with multi-paragraph body and multiple footers ``` fix: prevent racing of requests diff --git a/content/v1.0.0/index.md b/content/v1.0.0/index.md index 3b783f60..4e73083b 100644 --- a/content/v1.0.0/index.md +++ b/content/v1.0.0/index.md @@ -35,7 +35,7 @@ consumers of your library: 1. **BREAKING CHANGE:** a commit that has a footer `BREAKING CHANGE:`, or appends a `!` after the type/scope, introduces a breaking API change (correlating with [`MAJOR`](http://semver.org/#summary) in Semantic Versioning). A BREAKING CHANGE can be part of commits of any _type_. 1. _types_ other than `fix:` and `feat:` are allowed, for example [@commitlint/config-conventional](https://github.com/conventional-changelog/commitlint/tree/master/%40commitlint/config-conventional) (based on the [Angular convention](https://github.com/angular/angular/blob/22b96b9/CONTRIBUTING.md#-commit-message-guidelines)) recommends `build:`, `chore:`, - `ci:`, `docs:`, `style:`, `refactor:`, `perf:`, `test:`, and others. + `ci:`, `docs:`, `style:`, `refactor:`, `perf:`, `test:`, `experiment:`, and others. 1. _footers_ other than `BREAKING CHANGE: ` may be provided and follow a convention similar to [git trailer format](https://git-scm.com/docs/git-interpret-trailers). @@ -79,6 +79,11 @@ docs: correct spelling of CHANGELOG feat(lang): add Polish language ``` +### Commit message with experiment type +``` +experiment: try new caching strategy for API responses +``` + ### Commit message with multi-paragraph body and multiple footers ``` fix: prevent racing of requests