github/arm-trusted-firmware - arm-trusted-firmware - Gitea: Git with home nas server

Author	SHA1	Message	Date
Chris Kay	ba748f3c35	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>	3 years ago
Chris Kay	c503b42c09	docs(changelog): fix version tag links The Standard Version tool will not recognize a release header as a release header without the minor version, and will overwrite them when generating the next release changelog. Additionally, it will not generate a link to the tag diff unless a tag of the form `vX.Y.Z` exists. We ought to generate tags with this version format in the future to ensure the diff links are generated. Change-Id: I7864ab7a5822f83ddb7a7917208d2d029ae34729 Signed-off-by: Chris Kay <chris.kay@arm.com>	3 years ago
Chris Kay	f64c55826e	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>	3 years ago
Chris Kay	c4e8edab21	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>	3 years ago