# release-log **Repository Path**: mirrors_Financial-Times/release-log ## Basic Information - **Project Name**: release-log - **Description**: Automate opening/closing of change requests for FT applications - **Primary Language**: Unknown - **License**: Not specified - **Default Branch**: master - **Homepage**: None - **GVP Project**: No ## Statistics - **Stars**: 0 - **Forks**: 0 - **Created**: 2020-09-24 - **Last Updated**: 2026-07-18 ## Categories & Tags **Categories**: Uncategorized **Tags**: None ## README Release Log =========== 🚨 The [Konstructor Change Request API](https://biz-ops.in.ft.com/System/koncrapi) that this package uses has been decommissioned. 🚨 If you're looking for a replacement for this, the Change API documentation includes [some useful integration examples](https://github.com/Financial-Times/change-api#integration-examples). --- Automate opening/closing of release log change requests for FT applications. [![Build status](https://img.shields.io/circleci/project/Financial-Times/release-log.svg)][ci] [![MIT licensed](https://img.shields.io/badge/license-MIT-blue.svg)][license] ```sh release-log \ --owner-email "you@ft.com" \ --summary "Hello World" \ --description "This is a description" \ --service "my service" \ --api-key "xxxxxx" ``` Table Of Contents ----------------- * [Requirements](#requirements) * [Install](#install) * [Usage](#usage) * [Testing](#testing) * [Deployment](#deployment) * [License](#license) Requirements ------------ Running the release log tool requires [Node.js] 4.x and [npm]. Install ------- ```sh npm install -g @financial-times/release-log ``` Usage ----- ``` Usage: release-log [options] Options: -h, --help output usage information -V, --version output the version number -a, --api-key the API key to use when accessing the CR API -o, --owner-email the release log owner email address -s, --summary a short summary of the release -d, --description a short description of the release -f, --description-file file to read description from, instead of --description -r, --reason the reason for the release. Default: "Deployment" -c, --open-category the category for opening the release log. One of "Major", "Minor", "Significant". Default: "Minor" -C, --close-category the category for closing the release log. One of "Implemented", "Partially Implemented", "Rejected", "Rolled back", "Cancelled". Default: "Implemented" -R, --risk-profile the risk profile for the release log. One of "Low", "Medium", "High". Default: "Low" -e, --environment the environment the release log applies to. One of "Production", "Test", "Development", "Disaster Recovery". Default: "Test" -O, --outage whether there will be an outage. Default: false -S, --service the service that the release log applies to -n, --notify-channel the slack channel to notify of the release ``` Testing ------- To run tests on your machine you'll need to install [Node.js] and run `make install`. Then you can run the following commands: ```sh make test # run all the tests make test-unit # run the unit tests ``` You can run the unit tests with coverage reporting, which expects 90% coverage or more: ```sh make test-unit-coverage verify-coverage ``` The code will also need to pass linting on CI, you can run the linter locally with: ```sh make verify ``` We run the tests and linter on CI, you can view [results on CircleCI][ci]. `make test` and `make lint` must pass before we merge a pull request. Deployment ---------- New versions of the module are published automatically by CI when a new tag is created matching the pattern `/v.*/`. License ------- The Financial Times has published this software under the [MIT license][license]. [ci]: https://circleci.com/gh/Financial-Times/release-log [license]: http://opensource.org/licenses/MIT [node.js]: https://nodejs.org/ [npm]: https://www.npmjs.com/ [semver]: http://semver.org/