v4.1.0 add support for Node 18

What's Changed

• Point to new APIG portal to generate Biz Ops key in README by @ivomurrell in #194
• Update to Node 18 by @ivomurrell in #195

Full Changelog: v4.0.0...v4.1.0

v4.0.0

This release is part of the Platforms and Reliability set of scheduled breaking change releases in April.

The breaking changes in this package release are:

• Dropping support for Node.js 14

This will not be a breaking change for your application if it:

• Already runs on Node.js 16

If this is a breaking change for your application because it does not yet run on Node 16 you can follow this guide to migrate from Node.js 14 to Node.js 16

patch: remove dependency on bizops client unless using it

What's Changed

• cpp-814 - bizops key should not be a prerequisite for running nori by @leannecornish-ft in #181
• Strip github domain when parsing files by @ivomurrell in #153

Full Changelog: v3.0.0...v3.0.1

v3.0.0 Support Node 14 + 16

What's Changed

• Add support for Node 14 and Node 16 by @ivomurrell in #173

Breaking Changes

• Dropped support for Node 12

Full Changelog: v2.2.3...v3.0.0

Use npm auth token from circleci context

Use npm auth token from circleci context instead of vault next/circleci/component folder

patch: update bizops graphql queries to use v2

Merge pull request #172 from Financial-Times/cpp-793-bizops-api-v2

cpp-793 update bizops graphql api queries to v2

v2.2.1 Bugfix on transitioning pending messages + Fix typo in preinstall script

This version includes the following backwards compatible bug fixes:

• Change status from pending to done to avoid hanging process when creating PRs with nori
• Fix typo in preinstall script dependency

v2.2.0 Implement mechanism to avoid secondary rate limit in creating PRs

Implement timeout, retryAfter and sequential request mechanism to avoid hitting the secondary rate limit, which blocks you from creating more PRs, and repeatedly hitting the rate might result in banning of your app.

Error: You have exceeded a secondary rate limit and have been temporarily blocked from content creation. Please retry your request again later.

The mechanism was built upon the best practice to avoid secondary rate limit

1. Sequential PR creation request - Make requests for a single user or client ID serially. Do not make requests for a single user or client ID concurrently.
2. Retry After - When you have been limited, use the Retry-After response header to slow down. This change allows for retries to handle the creation of the subsequent PRs
3. Time out - Please create this content at a reasonable pace to avoid further limiting

Without this mechanism, I was only able to create 10 PRs and then nori will error out with the secondary rate limit. With this mechanism, I was able to successfully create 61 PRs in one go with nori. We need this change as the GitHub API has recently changed to be more defensive with its secondary rate limit, as seen in other projects

v2.1.0 Gets a repo's central branch instead of assuming it's master

This version of nori does not assume that the central branch is master instead it will determine which branch is the default branch.

v2.0.0

-beta versions aren’t automatically tagged as latest on publish in recent versions of npm, this release includes the changes from v2.0.0-beta.13 – 2.0.0-beta.15