This repository has been archived by the owner on Mar 25, 2020. It is now read-only.
Update dependency @financial-times/n-gage to v5 #33
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
^2.0.1
->^5.0.0
ℹ️ Find our documentation at https://github.com/Financial-Times/next/wiki/Renovate.
Release Notes
Financial-Times/n-gage
v5.0.0
Compare Source
https
for consistency with review apps #222v4.0.0
Compare Source
This release removes all n-ui related code.
v3.12.0
Compare Source
This is following a discussion on Slack.
We're in a situation on Conversion where we need to have E2E tests run on a predictable url and to block code from going out if tests fail. The best place to do this would be on staging, and to do that we need to break up the deploy task so that we can run our tests in between staging being set up and it being promoted to prod and then scaled down.
Related PR: #210
v3.11.2
Compare Source
v3.11.1
Compare Source
v3.11.0
Compare Source
Simplify the logging and provide the Change API with more information.
This should help for projects that deploy on a tag. And also stop us exposing the API key in the logs.
v3.10.1
Compare Source
v3.10.0
Compare Source
bower_components
folder before doingbower install
to prevent a class of spurious conflicts.review-app
doesn't existreturn await
warning to ESLint rulesv3.9.2
Compare Source
v3.9.1
Compare Source
Releases #204
v3.9.0
Compare Source
Releases #202
v3.8.1
Compare Source
v3.8.0
Compare Source
v3.7.2
Compare Source
v3.7.1
Compare Source
v3.7.0
Compare Source
adds
--custom-env
to get-config for use with non-standard env names likesandbox
orstaging
v3.6.0
Compare Source
As per the following discussion on Slack: https://financialtimes.slack.com/archives/C0ECBA4GY/p1554372261034100, which followed on from this Tweet: https://twitter.com/roelvangils/status/1113074439976075264
See #185
v3.5.0
Compare Source
Rise ecmaVersion version to fix deprecated property which caused warning on linting.
v3.4.3
Compare Source
v3.4.2
Compare Source
versions of n-gage from 2.2 onwards have an issue (#162) where dotfiles weren't being correctly copied for fresh local installs. i have no idea why it wasn't working but i've fixed it now
v3.4.1
Compare Source
Releases #180.
Updates the
make deploy-assets
target.Passes a new option
--app anvil
when callingnht deploy-hashed-assets
.v3.4.0
Compare Source
This release removes the check to enforce repo ownership with an ft.yml file.
Moving to CODEOWNERS files instead. See: Financial-Times/next-transformations#20
v3.3.0
Compare Source
This ensures it is sync'd at the end of the
.review-app
task.v3.2.0
Compare Source
v3.1.0
Compare Source
v3.0.0
Compare Source
where we do the whole heroku deploy thing
for a guide on how to migrate from
n-gage@v2
ton-gage@v3
, see Heroku review apps deployment.Renovate configuration
📅 Schedule: At any time (no schedule defined).
🚦 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.