commit | 7bfcce37f64326e9f37ebf696e0bf0642ec0cb25 | [log] [tgz] |
---|---|---|
author | dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> | Tue Jul 11 11:54:30 2023 +0000 |
committer | GitHub <noreply@github.com> | Tue Jul 11 11:54:30 2023 +0000 |
tree | a01807dd4f389f73c166d78e2d4d3a609c8f3bf3 | |
parent | 424b3f7df4cb21a0554f75c14ead98c746a7eebe [diff] |
Bump semver from 5.5.0 to 5.7.2 Bumps [semver](https://github.com/npm/node-semver) from 5.5.0 to 5.7.2. - [Release notes](https://github.com/npm/node-semver/releases) - [Changelog](https://github.com/npm/node-semver/blob/v5.7.2/CHANGELOG.md) - [Commits](https://github.com/npm/node-semver/compare/v5.5.0...v5.7.2) --- updated-dependencies: - dependency-name: semver dependency-type: indirect ... Signed-off-by: dependabot[bot] <support@github.com>
npm i
npm run dev
npm run checkLicenses
npm run runProd
. This is only to test if AOT is working and should never be used in a production environment.npm run build
. Files will be stored under /dist.npm run test
The version numbers follow the Semantic Versioning scheme.
In addition to MAJOR.MINOR.PATCH the following postfixes are used to indicate the development state.
The versioning layout is {MAJOR}.{MINOR}.{PATCH}-{INDICATOR}[.{PATCH}]. Only milestones and release candidates can have patch versions. Some examples:
1.2.3-snapshot
1.3.5-m.1
1.5.7-rc.2
2.0.0-ga
See CONTRIBUTING file.
See LICENSE file.