commit | fee35b7dfb4a1694009b819ef70a4bf19085a8a8 | [log] [tgz] |
---|---|---|
author | dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> | Wed Oct 05 06:19:39 2022 +0000 |
committer | GitHub <noreply@github.com> | Wed Oct 05 06:19:39 2022 +0000 |
tree | ca5e2484ee862e40001e9ea6327a8edd4a348c52 | |
parent | 8a1a84855f23a51c73e1745067189f3cb4b6c53f [diff] |
Bump css-what from 2.1.0 to 2.1.3 Bumps [css-what](https://github.com/fb55/css-what) from 2.1.0 to 2.1.3. - [Release notes](https://github.com/fb55/css-what/releases) - [Commits](https://github.com/fb55/css-what/compare/v2.1.0...v2.1.3) --- updated-dependencies: - dependency-name: css-what 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
See https://github.com/apache/fineract-cn-docker-compose for running all the Fineract-CN services from Docker.
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.