@doist/reactist 27.2.1 → 27.2.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.
Files changed (2) hide show
  1. package/README.md +33 -55
  2. package/package.json +1 -1
package/README.md CHANGED
@@ -203,58 +203,36 @@ When you open a GitHub PR, you'll notice the "UI Review" and "UI Tests" CI steps
203
203
 
204
204
  # Releasing
205
205
 
206
- A new version of reactist is published both on npm and GitHub Package Registry whenever a new release on GitHub is created.
207
-
208
- ## Before merging your changes
209
-
210
- In the GitHub PR that contains your new changes, make sure that you also include the following:
211
-
212
- 1. Add tests for bugs and new feature
213
-
214
- 2. Update relevant docs (storybooks, readme)
215
-
216
- 3. Execute:
217
-
218
- ```sh
219
- npm run validate
220
- ```
221
-
222
- and make sure no errors nor warnings are shown
223
-
224
- 4. Describe your changes in [`CHANGELOG.md`](CHANGELOG.md)
225
-
226
- 5. Bump the version in [`package.json`](package.json) and [`package-lock.json`](package-lock.json) by running:
227
-
228
- ```sh
229
- npm --no-git-tag-version version <major|minor|patch>
230
- ```
231
-
232
- [ref](https://docs.npmjs.com/cli/v6/commands/npm-version)
233
-
234
- Note that the steps above are also documented in the [PR template](.github/PULL_REQUEST_TEMPLATE.md) that you will be prompted with whenever you open a new reactist GitHub PR.
235
-
236
- ## After merging your changes
237
-
238
- Once your changes have been merged to `main`, create a new GitHub release:
239
-
240
- 1. Visit https://github.com/Doist/reactist/releases/new
241
-
242
- 2. In the "Choose a tag" dropdown, type the new release version (i.e. vX.Y.Z) and select "Create new tag: vX.Y.Z on publish"
243
-
244
- 3. In the "Release title" field, type the new release version (i.e. vX.Y.Z)
245
-
246
- 4. In the "Describe the release" box, paste the same content you added to the [`CHANGELOG.md`](CHANGELOG.md), but without the title header
247
-
248
- 5. Make sure the "Set as the latest release" checkbox is checked
249
-
250
- 6. Click "Publish release"
251
-
252
- 7. Visit https://github.com/Doist/reactist/actions
253
-
254
- 8. Make sure that a new GitHub action is now running (this will automatically perform all the necessary steps to publish the package)
255
-
256
- 9. Once the action is complete, check https://npmjs.com/package/@doist/reactist and verify that there's a new public release
257
-
258
- Finally, be sure to update both [todoist-web](https://github.com/Doist/todoist-web) and [twist-web](https://github.com/Doist/twist-web) to use the new reactist version you just published.
259
-
260
- The storybook hosted on GitHub pages will be automatically updated on each push to `main`. Should there be a problem, try running the action manually from the [Actions settings](https://github.com/Doist/reactist/actions).
206
+ This project uses [release-please](https://github.com/googleapis/release-please) to automate version management and package publishing.
207
+
208
+ ## How it works
209
+
210
+ 1. Make your changes using [Conventional Commits](https://www.conventionalcommits.org/):
211
+
212
+ - `feat:` for new features (minor version bump)
213
+ - `fix:` for bug fixes (patch version bump)
214
+ - `style:` for code style changes
215
+ - `perf:` for performance improvements
216
+ - `refactor:` for refactoring code
217
+ - `test:` for adding/updating tests
218
+ - `build:` for build/dependency changes
219
+ - `docs:` for documentation changes
220
+ - `ci:` for CI changes
221
+ - `revert:` for reverting previous commits
222
+ - `feat!:` or `fix!:` for breaking changes (major version bump)
223
+ - `chore:` for maintenance tasks (NOTE: these are not included in the changelog)
224
+
225
+ 2. When commits are pushed to `main`:
226
+
227
+ - Release-please automatically creates/updates a release PR
228
+ - The PR includes version bump and changelog updates
229
+ - Review the PR and merge when ready
230
+
231
+ 3. After merging the release PR:
232
+ - A new GitHub release is automatically created
233
+ - A new tag is created
234
+ - The `publish` workflow is triggered
235
+ - The package is published to npm and GitHub Packages
236
+ - Storybook documentation is automatically updated
237
+
238
+ The storybook hosted on GitHub pages will be automatically updated on each push to `main`. If there's a problem, try running the action manually from the [Actions settings](https://github.com/Doist/reactist/actions).
package/package.json CHANGED
@@ -6,7 +6,7 @@
6
6
  "email": "henning@doist.com",
7
7
  "url": "http://doist.com"
8
8
  },
9
- "version": "27.2.1",
9
+ "version": "27.2.2",
10
10
  "license": "MIT",
11
11
  "homepage": "https://github.com/Doist/reactist#readme",
12
12
  "repository": {