andrius
/
arm-trusted-firmware
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity
arm-trusted-firmware/package.json

24 lines
580 B
JSON
Raw Normal View History

build(hooks): add Husky configuration Husky is a tool for managing Git hooks within the repository itself. Traditionally, commit hooks need to be manually installed on a per-user basis, but Husky allows us to install these hooks either automatically when `npm install` is invoked within the repository, or manually with `npx husky install`. This will become useful for us in the next few patches when we begin introducing tools for enforcing a commit message style. Change-Id: I64cae147e9ea910347416cfe0bcc4652ec9b4830 Signed-off-by: Chris Kay <chris.kay@arm.com>
2020-12-09 12:56:27 +00:00
{
build(npm): add additional package metadata Introduces the `name` and `version` fields to the NPM package metadata file, which are used by Standard Version. Change-Id: I5266465f746bf29805f36cd94b5e5c20417d7fd0 Signed-off-by: Chris Kay <chris.kay@arm.com>
2021-11-02 13:40:09 +00:00
"name": "trusted-firmware-a",
docs(changelog): changelog for v2.7 release Change-Id: I573e5eb3c7fad097892292c8a967dc02d72d12e6 Signed-off-by: Jayanth Dodderi Chidanand <jayanthdodderi.chidanand@arm.com>
2022-05-19 11:03:07 +01:00
"version": "2.7.0",
build(npm): add license field This change adds the `license` field to our `package.json` file, which allows some license checking tools to analyze our dependencies for license incompatibilities. The current state of our licensed dependencies is as follows: ``` $ license-checker --summary ├─ MIT: 198 ├─ ISC: 31 ├─ Apache-2.0: 5 ├─ (MIT OR CC0-1.0): 3 ├─ BSD-3-Clause: 2 ├─ BSD-2-Clause: 2 ├─ 0BSD: 2 ├─ (MIT OR Apache-2.0): 1 ├─ CC-BY-3.0: 1 └─ CC0-1.0: 1 ``` Change-Id: I7b9dae1c9f732c7f7491b5d6557dd193b894d70c Signed-off-by: Chris Kay <chris.kay@arm.com>
2021-11-02 12:11:32 +00:00
"license": "BSD-3-Clause",
build(hooks): add Husky configuration Husky is a tool for managing Git hooks within the repository itself. Traditionally, commit hooks need to be manually installed on a per-user basis, but Husky allows us to install these hooks either automatically when `npm install` is invoked within the repository, or manually with `npx husky install`. This will become useful for us in the next few patches when we begin introducing tools for enforcing a commit message style. Change-Id: I64cae147e9ea910347416cfe0bcc4652ec9b4830 Signed-off-by: Chris Kay <chris.kay@arm.com>
2020-12-09 12:56:27 +00:00
"private": true,
"scripts": {
build(docs): introduce release script This change introduces a new NPM run script to automatically generate the release changelog, as well as bump version numbers across the code-base and create the release tag. This script runs [Standard Version] to execute this, which is a tool designed around automating substantial parts of the release process. This can be done by running: npm run release -- [<standard-version args>] Standard Version expects the project to adhere to the [Semantic Versioning] convention which TF-A does not, so you may need to specify the version manually, e.g.: npm run release -- --release-as 2.6.0 Individual steps of the release process may also be skipped at-will, which may be necessary when, for example, tweaking the changelog: npm run release -- --skip.commit --skip.tag Standard Version is configured by the `.versionrc.js` file, which contains information about the Conventional Commits types and scopes used by the project, and how they map to the changelog. To maintain continuity with the existing changelog style - at least to the extent possible in the move from manual to automatic creation - a customized changelog template has been introduced, based on the Conventional Commits template provided by Standard Version. This template package extends the Conventional Commits template package by introducing support for parsing the Conventional Commits scopes into changelog sections, similarly to how they were previously organized. [Standard Version]: https://github.com/conventional-changelog/standard-version [Semantic Versioning]: https://semver.org Change-Id: I5bafa512daedc631baae951651c38c1c62046b0a Signed-off-by: Chris Kay <chris.kay@arm.com>
2021-11-09 20:05:38 +00:00
"postinstall": "husky install",
docs(changelog): fix broken version bumping Standard Version was not bumping the package metadata files as it should have been. It's not clear to me why, but there is an open [GitHub issue][1] for documenting this behaviour. [1]: https://github.com/conventional-changelog/standard-version/issues/506 Change-Id: Ie89a81272fe507a3d2e1cd33c6ac1bdcc8ac3d75 Signed-off-by: Chris Kay <chris.kay@arm.com>
2021-12-03 11:22:09 +00:00
"release": "standard-version"
build(hooks): add Husky configuration Husky is a tool for managing Git hooks within the repository itself. Traditionally, commit hooks need to be manually installed on a per-user basis, but Husky allows us to install these hooks either automatically when `npm install` is invoked within the repository, or manually with `npx husky install`. This will become useful for us in the next few patches when we begin introducing tools for enforcing a commit message style. Change-Id: I64cae147e9ea910347416cfe0bcc4652ec9b4830 Signed-off-by: Chris Kay <chris.kay@arm.com>
2020-12-09 12:56:27 +00:00
},
build(npm): mandate Node.js engine version This change mandates a particular version of Node.js when running `npm install`. When using a version of Node.js that does not meet these expectations, a warning will be emitted to the user to let them know that they are using an unsupported version of Node.js Change-Id: I3f9bcf8be483a80b5882d65b034c6655013df19f Signed-off-by: Chris Kay <chris.kay@arm.com>
2021-12-03 12:04:24 +00:00
"engines": {
"node": ">=16.0.0"
},
build(hooks): add Husky configuration Husky is a tool for managing Git hooks within the repository itself. Traditionally, commit hooks need to be manually installed on a per-user basis, but Husky allows us to install these hooks either automatically when `npm install` is invoked within the repository, or manually with `npx husky install`. This will become useful for us in the next few patches when we begin introducing tools for enforcing a commit message style. Change-Id: I64cae147e9ea910347416cfe0bcc4652ec9b4830 Signed-off-by: Chris Kay <chris.kay@arm.com>
2020-12-09 12:56:27 +00:00
"devDependencies": {
refactor(hooks): replace cz-conventional-changelog with cz-commitlint This change replaces cz-conventional-changelog with cz-commitlint, which automatically configures Commitizen using our commitlint configuration file. Currently, we use some manual Javascript magic to load our Commitizen configuration into commitlint (the opposite of what's introduced by this change), which can be removed. With this change, we also move our commitlint configuration into a new `changelog.yaml` file. This file holds the same data as `.cz.json` previously did. Change-Id: I14ff2308f1a0b2b293c2128b28ca2df578ce9c1c Signed-off-by: Chris Kay <chris.kay@arm.com>
2021-12-01 16:34:55 +00:00
"@commitlint/cli": "^16.1.0",
"@commitlint/config-conventional": "^16.0.0",
"@commitlint/cz-commitlint": "^16.1.0",
build(hooks): update Commitizen to ^4.2.4 An indirect dependency of Commitizen (`merge`) is currently failing the NPM.js auditor due to vulnerability CVE-2020-28499. This commit moves the minimum version of Commitizen to 4.2.4, which has resolved this vulnerability. Change-Id: Ia9455bdbe02f7406c1a106f173c4095943a201ed Signed-off-by: Chris Kay <chris.kay@arm.com>
2021-05-12 15:22:42 +01:00
"commitizen": "^4.2.4",
build(docs): introduce release script This change introduces a new NPM run script to automatically generate the release changelog, as well as bump version numbers across the code-base and create the release tag. This script runs [Standard Version] to execute this, which is a tool designed around automating substantial parts of the release process. This can be done by running: npm run release -- [<standard-version args>] Standard Version expects the project to adhere to the [Semantic Versioning] convention which TF-A does not, so you may need to specify the version manually, e.g.: npm run release -- --release-as 2.6.0 Individual steps of the release process may also be skipped at-will, which may be necessary when, for example, tweaking the changelog: npm run release -- --skip.commit --skip.tag Standard Version is configured by the `.versionrc.js` file, which contains information about the Conventional Commits types and scopes used by the project, and how they map to the changelog. To maintain continuity with the existing changelog style - at least to the extent possible in the move from manual to automatic creation - a customized changelog template has been introduced, based on the Conventional Commits template provided by Standard Version. This template package extends the Conventional Commits template package by introducing support for parsing the Conventional Commits scopes into changelog sections, similarly to how they were previously organized. [Standard Version]: https://github.com/conventional-changelog/standard-version [Semantic Versioning]: https://semver.org Change-Id: I5bafa512daedc631baae951651c38c1c62046b0a Signed-off-by: Chris Kay <chris.kay@arm.com>
2021-11-09 20:05:38 +00:00
"conventional-changelog-tf-a": "file:tools/conventional-changelog-tf-a",
build(npm): add Standard Version v9.3.2 This tool is used to generate changelogs, tag repositories and bump version numbers across the code-base. In preparation for the v2.6.0 release of TF-A, we will be incorporating it into our release workflow, with the hope that it can reduce some of the workload involved going forward. After this change our dependency license situation is as follows: ``` $ license-checker --summary ├─ MIT: 249 ├─ ISC: 43 ├─ Apache-2.0: 6 ├─ BSD-2-Clause: 3 ├─ (MIT OR CC0-1.0): 3 ├─ BSD-3-Clause: 2 ├─ 0BSD: 2 ├─ (MIT OR Apache-2.0): 1 ├─ BSD*: 1 ├─ CC-BY-3.0: 1 └─ CC0-1.0: 1 ``` Change-Id: Ie41443045ecff22f322d155a4bed8ab5d92208cd Signed-off-by: Chris Kay <chris.kay@arm.com>
2021-11-02 13:23:38 +00:00
"husky": "^7.0.4",
refactor(hooks): replace cz-conventional-changelog with cz-commitlint This change replaces cz-conventional-changelog with cz-commitlint, which automatically configures Commitizen using our commitlint configuration file. Currently, we use some manual Javascript magic to load our Commitizen configuration into commitlint (the opposite of what's introduced by this change), which can be removed. With this change, we also move our commitlint configuration into a new `changelog.yaml` file. This file holds the same data as `.cz.json` previously did. Change-Id: I14ff2308f1a0b2b293c2128b28ca2df578ce9c1c Signed-off-by: Chris Kay <chris.kay@arm.com>
2021-12-01 16:34:55 +00:00
"js-yaml": "^4.1.0",
build(npm): add Standard Version v9.3.2 This tool is used to generate changelogs, tag repositories and bump version numbers across the code-base. In preparation for the v2.6.0 release of TF-A, we will be incorporating it into our release workflow, with the hope that it can reduce some of the workload involved going forward. After this change our dependency license situation is as follows: ``` $ license-checker --summary ├─ MIT: 249 ├─ ISC: 43 ├─ Apache-2.0: 6 ├─ BSD-2-Clause: 3 ├─ (MIT OR CC0-1.0): 3 ├─ BSD-3-Clause: 2 ├─ 0BSD: 2 ├─ (MIT OR Apache-2.0): 1 ├─ BSD*: 1 ├─ CC-BY-3.0: 1 └─ CC0-1.0: 1 ``` Change-Id: Ie41443045ecff22f322d155a4bed8ab5d92208cd Signed-off-by: Chris Kay <chris.kay@arm.com>
2021-11-02 13:23:38 +00:00
"standard-version": "^9.3.2"
build(hooks): add Husky configuration Husky is a tool for managing Git hooks within the repository itself. Traditionally, commit hooks need to be manually installed on a per-user basis, but Husky allows us to install these hooks either automatically when `npm install` is invoked within the repository, or manually with `npx husky install`. This will become useful for us in the next few patches when we begin introducing tools for enforcing a commit message style. Change-Id: I64cae147e9ea910347416cfe0bcc4652ec9b4830 Signed-off-by: Chris Kay <chris.kay@arm.com>
2020-12-09 12:56:27 +00:00
}
}