Skip to content

Commit f985b8d

Browse files
Release 4.2.0
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
1 parent 64b9f89 commit f985b8d

3 files changed

Lines changed: 344 additions & 1439 deletions

File tree

README.md

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -39,3 +39,29 @@ Check out the [Documentation](https://docs.ux4iot.com/implementing-your-custom-s
3939
- API documentation on grant requests with ux4iot
4040
- Why you would need to use this library when using ux4iot
4141
- How to write a security backend for ux4iot
42+
43+
## Releasing
44+
45+
Releases are published to npm automatically via GitHub Actions when a version tag is pushed.
46+
47+
1. Bump the version in `package.json` (and `package-lock.json`) using npm:
48+
```bash
49+
npm version patch # 4.2.0 → 4.2.1
50+
npm version minor # 4.2.0 → 4.3.0
51+
npm version major # 4.2.0 → 5.0.0
52+
```
53+
Use `--no-git-tag-version` if you want to create the commit and tag manually.
54+
55+
2. Commit the version bump:
56+
```bash
57+
git add package.json package-lock.json
58+
git commit -m "Release 4.2.0"
59+
```
60+
61+
3. Create and push the tag:
62+
```bash
63+
git tag 4.2.0
64+
git push && git push --tags
65+
```
66+
67+
The CI workflow triggers on any pushed tag, runs `npm ci` and `npm run build`, then publishes to npm using the `NPM_TOKEN` secret.

0 commit comments

Comments
 (0)