aboutsummaryrefslogtreecommitdiffstatshomepage
path: root/DEVELOPMENT.md
blob: 9fb520f5f20090ad7b1f26881b42150e6e90c75c (plain) (blame)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
Releases
--------

* Update the version in package.json & package-lock.json using

      npm version --git-tag-version=false patch

    * Instead of `patch`, use `minor` or `major`.
* Check if you need to update it in the README.
* Commit changes & make/update the required git tags.
    * Best done using [tag-release].

[tag-release]: https://github.com/egor-tensin/tag-release

Development
-----------

To upgrade Node dependencies in package-lock.json:

    npm upgrade

The main dependencies are listed in package.json.
Specifically, the actions/core is the main dependency.
To upgrade it, modify package.json and run `npm upgrade`.
The list of actions/core version can be found
[here](https://www.npmjs.com/package/@actions/core?activeTab=readme).

The versioning scheme (and the usage of `^` and `~` symbols) is described
[here](https://docs.npmjs.com/about-semantic-versioning).