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: docs/RELEASE-PROCESS.md
+3-25Lines changed: 3 additions & 25 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,30 +1,8 @@
1
1
## Publish to NPM
2
2
3
-
To publish this library to NPM, create a tag and push it to GitHub. Make sure that the version in ```package.json``` matches the version you define in the tag. A workflow will do all the necessary steps:
4
-
5
-
```bash
6
-
git checkout main
7
-
git tag -a v1.14.1 -m "version 1.14.1"
8
-
git push origin v1.14.1
9
-
```
10
-
11
-
Do not use `git push --tags` as it can accidentally push tags from other repositories.
12
-
13
-
## Workflow Description
14
-
15
-
The logic is split in two jobs
16
-
* First jobs perform tests. It runs on Windows runner since Linux runners don't have GPU, which is required by many tests.
17
-
* Second job runs on Linux and creates builds minified library, creates github release, uploads release assets,
18
-
updates version in npm package and submits package in the npm registry.
19
-
20
-
Pushing a tag triggers the publishing workflow, but it can also be triggered manually.
21
-
The workflow searches for the most recent version tag matching [semantic version rules](https://classic.yarnpkg.com/en/docs/dependency-versions#toc-semantic-versioning),
22
-
and must be prefixed with a `v`
23
-
24
-
There can be release versions such as `v1.14.0`, and release candidates, e.g. `v1.14.0-rc.1`.
25
-
26
-
In case of release version the action parses `CHANGELOG.md` and creates release notes based on current and last version.
27
-
Release candidate versions do not generate release notes.
3
+
1. Use [semantic version rules](https://classic.yarnpkg.com/en/docs/dependency-versions#toc-semantic-versioning) to define a version in `package.json`.
4
+
2. Update `CHANGELOG.md`.
5
+
3. Run `release.yml` by manual workflow dispatch. This builds the minified library, tags the commit based on the version in `package.json`, creates a GitHub release, uploads release assets, and publishes the build output to NPM.
28
6
29
7
The changelog should be updated on every PR - there is a placeholder at the top of the document - and heading should be renamed to the same version which is going to be set in the version tag during release.
0 commit comments