Financial-Times/n-gage
### [`v8.3.0`](https://togithub.com/Financial-Times/n-gage/compare/v8.2.0...v8.3.0)
[Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v8.2.0...v8.3.0)
### [`v8.2.0`](https://togithub.com/Financial-Times/n-gage/releases/v8.2.0)
[Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v8.1.1...v8.2.0)
see [#252](https://togithub.com/Financial-Times/n-gage/issues/252)
### [`v8.1.1`](https://togithub.com/Financial-Times/n-gage/compare/v8.1.0...v8.1.1)
[Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v8.1.0...v8.1.1)
### [`v8.1.0`](https://togithub.com/Financial-Times/n-gage/releases/v8.1.0)
[Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v8.0.0...v8.1.0)
If in a CI environment and a `package-lock.json` exists, the `npm ci` command will be called to freshly install `node_modules` from `package-lock.json`.
`npm ci` is the install command intended for use in CI environments and is faster and safer than `npm install` (safer because installs will fail if `package-lock.json` is inconsistent with `package.json`).
### [`v8.0.0`](https://togithub.com/Financial-Times/n-gage/releases/v8.0.0)
[Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v7.0.0...v8.0.0)
hey so previously we'd prevent npm from creating `package-lock.json` files and delete them on sight for a few reasons:
- they made it more difficult to keep versions of `n-ui` in sync between npm and bower and between apps
- they made it more difficult to roll out security updates
- they were unstable
none of these reasons are valid anymore!
- `n-ui` is dead, and Page Kit doesn't require version parity everywhere or keeping bower in sync
- Renovate handles `package-lock.json` files just fine thx
- 2017 was a long time ago
so we can now let npm create those files. this is **opt-in**: if you have `package-lock.json` in your repo's `.gitignore`, which you probably do, `n-gage` will keep its old behaviour. if not, it'll do a default `npm install` allowing `package-lock.json` to be created. since this automatically prunes superfluous dependencies, we don't need to do that ourselves any more.
we'd strongly encourage you to enable `package-lock.json`: this will potentially drastically speed up your CI builds and allow better caching of dependencies.
### [`v7.0.0`](https://togithub.com/Financial-Times/n-gage/compare/v6.2.1...v7.0.0)
[Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v6.2.1...v7.0.0)
### [`v6.2.1`](https://togithub.com/Financial-Times/n-gage/releases/v6.2.1)
[Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v6.2.0...v6.2.1)
upgrades eslint-config-next to version 2.0.0 that has dependencies working correctly
### [`v6.2.0`](https://togithub.com/Financial-Times/n-gage/releases/v6.2.0)
[Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v6.1.0...v6.2.0)
This release uses the ESLint shareable configuration for Next projects [eslint-config-next](https://togithub.com/Financial-Times/eslint-config-next).
### [`v6.1.0`](https://togithub.com/Financial-Times/n-gage/releases/v6.1.0)
[Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v6.0.1...v6.1.0)
### Review app assets
[#233](https://togithub.com/Financial-Times/n-gage/issues/233) Heroku review apps now deploy their assets to a separate S3 bucket. Since review apps currently host their own assets, this is not a breaking change.
Apps should migrate to using assets from this S3 bucket so the review app environment is closer to production. See https://github.com/Financial-Times/next-static/pull/159/files for an example migration.
### Documentation rewrite
The README has been rewritten to our new documentation format.
### [`v6.0.1`](https://togithub.com/Financial-Times/n-gage/releases/v6.0.1)
[Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v6.0.0...v6.0.1)
- Fix warning from `eslint-plugin-react` about version ([#230](https://togithub.com/Financial-Times/n-gage/issues/230))
### [`v6.0.0`](https://togithub.com/Financial-Times/n-gage/releases/v6.0.0)
[Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v5.1.2...v6.0.0)
Remove `deploy-hashed-assets` step in deploy which looks for a `asset-hashes.json` file in the project.
Check if you have a `asset-hashes.json` file, if you do not, there is nothing to do.
If you do have a `asset-hashes.json` file, migrate to using `public/manifest.json` which is generated by Page Kit by default.
See the `n-heroku-tools` release for more details: https://github.com/Financial-Times/n-heroku-tools/releases/tag/v10.0.0
Pull request: https://github.com/Financial-Times/n-gage/pull/229
### [`v5.1.2`](https://togithub.com/Financial-Times/n-gage/releases/v5.1.2)
[Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v5.1.1...v5.1.2)
- Update Vault documentation URL ([#225](https://togithub.com/Financial-Times/n-gage/issues/225))
- Fix issues for users with a space in their PATH ([#226](https://togithub.com/Financial-Times/n-gage/issues/226))
### [`v5.1.1`](https://togithub.com/Financial-Times/n-gage/releases/v5.1.1)
[Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v5.1.0...v5.1.1)
See [#224](https://togithub.com/Financial-Times/n-gage/issues/224) for details
### [`v5.1.0`](https://togithub.com/Financial-Times/n-gage/releases/v5.1.0)
[Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v5.0.0...v5.1.0)
Add flag for disabling configuration of git hooks ([#223](https://togithub.com/Financial-Times/n-gage/issues/223)).
### [`v5.0.0`](https://togithub.com/Financial-Times/n-gage/releases/v5.0.0)
[Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v4.0.0...v5.0.0)
- checks for the new Husky format and migrates apps to it [#221](https://togithub.com/Financial-Times/n-gage/issues/221)
- runs staging smoke tests on `https` for consistency with review apps [#222](https://togithub.com/Financial-Times/n-gage/issues/222)
### [`v4.0.0`](https://togithub.com/Financial-Times/n-gage/releases/v4.0.0)
[Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v3.12.0...v4.0.0)
This release removes all n-ui related code.
Configuration
📅 Schedule: "after 10pm every weekday,before 5am every weekday,every weekend" in timezone Europe/London.
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
[ ] If you want to rebase/retry this PR, check this box.
This PR contains the following updates:
^3.6.0->^8.0.0:information_source: Find our documentation at https://github.com/Financial-Times/next/wiki/Renovate.
Release Notes
Financial-Times/n-gage
### [`v8.3.0`](https://togithub.com/Financial-Times/n-gage/compare/v8.2.0...v8.3.0) [Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v8.2.0...v8.3.0) ### [`v8.2.0`](https://togithub.com/Financial-Times/n-gage/releases/v8.2.0) [Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v8.1.1...v8.2.0) see [#252](https://togithub.com/Financial-Times/n-gage/issues/252) ### [`v8.1.1`](https://togithub.com/Financial-Times/n-gage/compare/v8.1.0...v8.1.1) [Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v8.1.0...v8.1.1) ### [`v8.1.0`](https://togithub.com/Financial-Times/n-gage/releases/v8.1.0) [Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v8.0.0...v8.1.0) If in a CI environment and a `package-lock.json` exists, the `npm ci` command will be called to freshly install `node_modules` from `package-lock.json`. `npm ci` is the install command intended for use in CI environments and is faster and safer than `npm install` (safer because installs will fail if `package-lock.json` is inconsistent with `package.json`). ### [`v8.0.0`](https://togithub.com/Financial-Times/n-gage/releases/v8.0.0) [Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v7.0.0...v8.0.0) hey so previously we'd prevent npm from creating `package-lock.json` files and delete them on sight for a few reasons: - they made it more difficult to keep versions of `n-ui` in sync between npm and bower and between apps - they made it more difficult to roll out security updates - they were unstable none of these reasons are valid anymore! - `n-ui` is dead, and Page Kit doesn't require version parity everywhere or keeping bower in sync - Renovate handles `package-lock.json` files just fine thx - 2017 was a long time ago so we can now let npm create those files. this is **opt-in**: if you have `package-lock.json` in your repo's `.gitignore`, which you probably do, `n-gage` will keep its old behaviour. if not, it'll do a default `npm install` allowing `package-lock.json` to be created. since this automatically prunes superfluous dependencies, we don't need to do that ourselves any more. we'd strongly encourage you to enable `package-lock.json`: this will potentially drastically speed up your CI builds and allow better caching of dependencies. ### [`v7.0.0`](https://togithub.com/Financial-Times/n-gage/compare/v6.2.1...v7.0.0) [Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v6.2.1...v7.0.0) ### [`v6.2.1`](https://togithub.com/Financial-Times/n-gage/releases/v6.2.1) [Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v6.2.0...v6.2.1) upgrades eslint-config-next to version 2.0.0 that has dependencies working correctly ### [`v6.2.0`](https://togithub.com/Financial-Times/n-gage/releases/v6.2.0) [Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v6.1.0...v6.2.0) This release uses the ESLint shareable configuration for Next projects [eslint-config-next](https://togithub.com/Financial-Times/eslint-config-next). ### [`v6.1.0`](https://togithub.com/Financial-Times/n-gage/releases/v6.1.0) [Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v6.0.1...v6.1.0) ### Review app assets [#233](https://togithub.com/Financial-Times/n-gage/issues/233) Heroku review apps now deploy their assets to a separate S3 bucket. Since review apps currently host their own assets, this is not a breaking change. Apps should migrate to using assets from this S3 bucket so the review app environment is closer to production. See https://github.com/Financial-Times/next-static/pull/159/files for an example migration. ### Documentation rewrite The README has been rewritten to our new documentation format. ### [`v6.0.1`](https://togithub.com/Financial-Times/n-gage/releases/v6.0.1) [Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v6.0.0...v6.0.1) - Fix warning from `eslint-plugin-react` about version ([#230](https://togithub.com/Financial-Times/n-gage/issues/230)) ### [`v6.0.0`](https://togithub.com/Financial-Times/n-gage/releases/v6.0.0) [Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v5.1.2...v6.0.0) Remove `deploy-hashed-assets` step in deploy which looks for a `asset-hashes.json` file in the project. Check if you have a `asset-hashes.json` file, if you do not, there is nothing to do. If you do have a `asset-hashes.json` file, migrate to using `public/manifest.json` which is generated by Page Kit by default. See the `n-heroku-tools` release for more details: https://github.com/Financial-Times/n-heroku-tools/releases/tag/v10.0.0 Pull request: https://github.com/Financial-Times/n-gage/pull/229 ### [`v5.1.2`](https://togithub.com/Financial-Times/n-gage/releases/v5.1.2) [Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v5.1.1...v5.1.2) - Update Vault documentation URL ([#225](https://togithub.com/Financial-Times/n-gage/issues/225)) - Fix issues for users with a space in their PATH ([#226](https://togithub.com/Financial-Times/n-gage/issues/226)) ### [`v5.1.1`](https://togithub.com/Financial-Times/n-gage/releases/v5.1.1) [Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v5.1.0...v5.1.1) See [#224](https://togithub.com/Financial-Times/n-gage/issues/224) for details ### [`v5.1.0`](https://togithub.com/Financial-Times/n-gage/releases/v5.1.0) [Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v5.0.0...v5.1.0) Add flag for disabling configuration of git hooks ([#223](https://togithub.com/Financial-Times/n-gage/issues/223)). ### [`v5.0.0`](https://togithub.com/Financial-Times/n-gage/releases/v5.0.0) [Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v4.0.0...v5.0.0) - checks for the new Husky format and migrates apps to it [#221](https://togithub.com/Financial-Times/n-gage/issues/221) - runs staging smoke tests on `https` for consistency with review apps [#222](https://togithub.com/Financial-Times/n-gage/issues/222) ### [`v4.0.0`](https://togithub.com/Financial-Times/n-gage/releases/v4.0.0) [Compare Source](https://togithub.com/Financial-Times/n-gage/compare/v3.12.0...v4.0.0) This release removes all n-ui related code.Configuration
📅 Schedule: "after 10pm every weekday,before 5am every weekday,every weekend" in timezone Europe/London.
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by WhiteSource Renovate. View repository job log here.