You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+8-7Lines changed: 8 additions & 7 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -215,14 +215,15 @@ import { SYNTAX_I18NEXT } from "react-interpolate"
215
215
216
216
# Releasing
217
217
218
-
A new version of @doist/react-interpolate is published both on npm and GitHub Package Registry whenever a new release on GitHub is created.
218
+
Merges to `main` automatically trigger `semantic-release`.
219
219
220
-
To update the version in both `package.json` and `package-lock.json` run:
220
+
The release workflow will:
221
221
222
-
```sh
223
-
npm --no-git-tag-version version <major|minor|patch>
224
-
```
222
+
- determine the next version from Conventional Commits
223
+
- update `package.json`, `package-lock.json`, and `CHANGELOG.md`
224
+
- create the Git tag and GitHub release
225
+
- publish `@doist/react-interpolate` to both npm and GitHub Packages
225
226
226
-
Once these changes have been pushed and merged, create a release on GitHub.
227
+
This means there is no manual version bump and no manual GitHub release creation step anymore.
227
228
228
-
A GitHub Action will automatically perform all the necessary steps and will release the version number that's specified inside the `package.json`'s `version` field so make sure that the release tag reflects the version you want to publish.
229
+
Because the repository uses squash-merge style commit messages, pull request titles must follow the [Conventional Commits specification](https://www.conventionalcommits.org/). CI validates this automatically.
0 commit comments