@gravity-ui/page-constructor 2.8.1 → 2.8.2
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 +7 -0
- package/README.md +17 -0
- package/package.json +1 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,12 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## [2.8.2](https://github.com/gravity-ui/page-constructor/compare/v2.8.1...v2.8.2) (2023-04-12)
|
|
4
|
+
|
|
5
|
+
|
|
6
|
+
### Bug Fixes
|
|
7
|
+
|
|
8
|
+
* allow everyone to publish release and remove execess maintainers ([#301](https://github.com/gravity-ui/page-constructor/issues/301)) ([2bfe490](https://github.com/gravity-ui/page-constructor/commit/2bfe490f643707427383be104ffe699fd6db4e27))
|
|
9
|
+
|
|
3
10
|
## [2.8.1](https://github.com/gravity-ui/page-constructor/compare/v2.8.0...v2.8.1) (2023-04-11)
|
|
4
11
|
|
|
5
12
|
|
package/README.md
CHANGED
|
@@ -323,3 +323,20 @@ When you receive the approval of your pull-request from the code owners and pass
|
|
|
323
323
|
3. Wait until robot creates a PR with a new version of the package and information about your changes in CHANGELOG.md. You can see the process on [the Actions tab](https://github.com/gravity-ui/page-constructor/actions).
|
|
324
324
|
4. Check your changes in CHANGELOG.md and approve robot's PR.
|
|
325
325
|
5. Squash and merge PR. You can see release process on [the Actions tab](https://github.com/gravity-ui/page-constructor/actions).
|
|
326
|
+
|
|
327
|
+
### Beta-major versions release
|
|
328
|
+
|
|
329
|
+
If you want to release a new major version, you will probably need for a beta versions before a stable one, please do the following:
|
|
330
|
+
|
|
331
|
+
1. Create or update the branch `beta`.
|
|
332
|
+
2. Add there your changes.
|
|
333
|
+
3. When you ready for a new beta version, release it manually with an empty commit (or you can add this commit message with footer to the last commit):
|
|
334
|
+
|
|
335
|
+
```bash
|
|
336
|
+
git commit -m 'fix: last commit
|
|
337
|
+
|
|
338
|
+
Release-As: 3.0.0-beta.0' --allow-empty
|
|
339
|
+
```
|
|
340
|
+
|
|
341
|
+
4. Release please robot will create a new PR to the branch `beta` with updated CHANGELOG.md and bump version of the package
|
|
342
|
+
5. You can repeat it as many as you want. When you ready to release the latest major version without beta tag, you have to create PR from branch `beta` to branch `main`. Notice that it is normal that your package version will be with beta tag. Robot knows that and change it properly. `3.0.0-beta.0` will become `3.0.0`
|