@gravity-ui/page-constructor 2.1.0 → 2.1.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,12 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## [2.1.1](https://github.com/gravity-ui/page-constructor/compare/v2.1.0...v2.1.1) (2023-03-28)
|
|
4
|
+
|
|
5
|
+
|
|
6
|
+
### Bug Fixes
|
|
7
|
+
|
|
8
|
+
* quotes validator schema ([#247](https://github.com/gravity-ui/page-constructor/issues/247)) ([87b8587](https://github.com/gravity-ui/page-constructor/commit/87b8587bcd5fe2bb96b5d70aae9eb6ca9e189f33))
|
|
9
|
+
|
|
3
10
|
## [2.1.0](https://github.com/gravity-ui/page-constructor/compare/v2.0.3...v2.1.0) (2023-03-27)
|
|
4
11
|
|
|
5
12
|
|
package/README.md
CHANGED
|
@@ -306,6 +306,13 @@ In usual cases we use two types of commits:
|
|
|
306
306
|
1. fix: a commit of the type fix patches a bug in your codebase (this correlates with PATCH in Semantic Versioning).
|
|
307
307
|
2. feat: a commit of the type feat introduces a new feature to the codebase (this correlates with MINOR in Semantic Versioning).
|
|
308
308
|
3. 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 in Semantic Versioning). A BREAKING CHANGE can be part of commits of any type.
|
|
309
|
+
4. To set release package version manually you need to add `Release-As: <version>` to your commit message e.g.
|
|
310
|
+
|
|
311
|
+
```bash
|
|
312
|
+
git commit -m 'chore: bump release
|
|
313
|
+
|
|
314
|
+
Release-As: 1.2.3'
|
|
315
|
+
```
|
|
309
316
|
|
|
310
317
|
You can see all information [here](https://www.conventionalcommits.org/en/v1.0.0/).
|
|
311
318
|
|