Releasing #356 caused an outage.

There's a newer package available from Sentry that we should put time into upgrading to instead.

npm install @sentry/node

https://docs.sentry.io/quickstart/?platform=node#pick-a-client-integration

this package has been renamed to @quarterto/git-version-infer. i can't remember if it's backwards-compatible 😬

#326 (comment)

So we should pull in the renamed package.

https://app.getsentry.com/nextftcom/amp/issues/112662932/

Error: lol
  File "/Users/matthew.brennan/Documents/google-amp/app.js", line 16, in null.<anonymous>
    app.get('/lolthrow', function() {throw new Error('lol')});
...
(35 additional frame(s) were not displayed)

• mock access configuration and the old barrier implementation (Accounts team?)
• analytics.log
• vanity URL handling
• slideshow transforms

This issue provides visibility into Renovate updates and their statuses. Learn more

Pending Approval

These branches will be created by Renovate only once you click their checkbox below.

• Update dependency @financial-times/n-gage to v9
• Update dependency @financial-times/n-heroku-tools to v14
• Update dependency @financial-times/n-test to v4
• Update dependency chai to v4
• Update dependency chalk to v5
• Update dependency dirty-chai to v2
• Update dependency mocha to v10
• Update dependency mocha-junit-reporter to v2
• Update dependency nock to v13
• Update dependency nodemon to v2
• Update dependency proxyquire to v2
• Update dependency sinon to v14

Rate Limited

These updates are currently rate limited. Click on a checkbox below to force their creation now.

• Update Node.js to v16
• Update Node.js to v17
• Update dependency @financial-times/fastly-tools to v4
• Update dependency @financial-times/n-es-client to v4
• Update dependency csso to v5
• Update dependency glob to v8
• Update dependency http-errors to v2

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency express-handlebars to v5 [SECURITY]
• Update dependency node-sass to v7 [SECURITY]
• Update dependency @financial-times/n-es-client to v3.0.2
• Update dependency @quarterto/promise-deps-parallel to v1.8.0
• Update dependency fs-promise to ^0.5.0
• Update npm to v6.14.17
• Update dependency autoprefixer to v10
• Update dependency fs-promise to v2
• Update dependency html-entities to v2
• Update dependency mkdirp to v1
• Update dependency node-fetch to v3
• Update dependency raven to v2
• Update dependency supertest to v6
• Update npm to v8
• Update postcss packages (major) (postcss, postcss-csso, postcss-discard-empty, postcss-inline-svg)
• Click on this checkbox to rebase all open PRs at once

• Check this box to trigger a request for Renovate to run again on this repository

This master issue contains a list of Renovate updates and their statuses.

Pending Approval

These PRs will be created by Renovate only once you click their checkbox below.

• Update dependency lintspaces-cli to ^0.7.0
• Update dependency ansi-escapes to v4
• Update dependency chai to v4
• Update dependency chalk to v2
• Update dependency dirty-chai to v2
• Update dependency mocha to v6
• Update dependency nock to v10
• Update dependency proxyquire to v2
• Update dependency sinon to v7
• Update linters (major) (eslint, eslint-config-airbnb-base)

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

• Update dependency dotenv to v8

Closed/Ignored

These updates were closed unmerged and will not be recreated unless you click a checkbox below.

• Update dependency @quarterto/promise-deps-parallel to v1.8.0
• Update dependency fs-promise to ^0.5.0
• Update dependency @quarterto/heroku-version-infer to v4
• Update dependency autoprefixer to v9
• Update dependency fs-promise to v2
• Update dependency raven to v2

On registry https://registry.npmjs.org/, the "latest" version (v1.1.1) of dependency @financial-times/change-request has the following deprecation notice:

Module has been renamed to @financial-times/release-log

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Affected package file(s): package.json

If you don't care about this, you can close this issue and not be warned about @financial-times/change-request's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:

"suppressNotifications": ["deprecationWarningIssues"]

On registry https://registry.npmjs.org/, the "latest" version (v2.0.3) of dependency fs-promise has the following deprecation notice:

Use mz or fs-extra^3.0 with Promise Support

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Affected package file(s): package.json

If you don't care about this, you can close this issue and not be warned about fs-promise's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:

"suppressNotifications": ["deprecationWarningIssues"]

We need to add and configure the Fastly WAF to this project's Fastly service.

The service ID is 4g6XuZYa26LQSfxdzhXXMu.

Fastly have published some documentation on how to configure their WAF on a service.

We'll need to work with the Fastly support team to get this setup, you can raise an issue with them by posting in the #fastly-support Slack channel and adding a 🔑 emoji to the message.

We should first ensure that we are logging from Fastly to Splunk.

We should configure a custom response that is a valid AMP page and matches this products design.

There is a command line tool Fastly are currently working on to configure a services WAF.

See #299 (comment).

Removes a dependency and automates keeping on top of performance.

Probably an easy fix this one.

On registry https://registry.npmjs.org/, the "latest" version (v4.0.1) of dependency @quarterto/heroku-version-infer has the following deprecation notice:

heroku-version-infer has been renamed to @quarterto/git-version-infer

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Affected package file(s): package.json

If you don't care about this, you can close this issue and not be warned about @quarterto/heroku-version-infer's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:

"suppressNotifications": ["deprecationWarningIssues"]

See #338 and #352.

Not sure what or where.

See #322 (comment).

https://github.com/kevinbeaty/fs-promise

fs-promise is now deprecated. Use mz/fs fs-extra^3.0.

On registry https://registry.npmjs.org/, the "latest" version (v1.8.4) of dependency bower has the following deprecation notice:

We don't recommend using Bower for new projects. Please consider Yarn and Webpack or Parcel. You can read how to migrate legacy project here: https://bower.io/blog/2017/how-to-migrate-away-from-bower/

Marking the latest version of an npm package as deprecated results in the entire package being considered deprecated, so contact the package author you think this is a mistake.

Affected package file(s): package.json

If you don't care about this, you can close this issue and not be warned about bower's deprecation again. If you would like to completely disable all future deprecation warnings then add the following to your config:

"suppressNotifications": ["deprecationWarningIssues"]

broken https redirects, poisons local.ft.com with HSTS. should always run in HTTPS mode (add make certs to run after install) and not set HSTS in development mode

Google AMP is one of very few systems left which is using Konstructor's Change Request API (CRAPI) to create release log into RemedyForce. Since CRAPI is hosted on-prem and is a really old and unmanaged java app, we plan to decommission it by the end of this quarter.

To replace it, we have created a brand new and much nicer Change API which is much more simpler and reliable. More info here.

Please try it out ! ( ideally before the end of Q3)