Closed camfindlay closed 6 years ago
@anotheredward @ebuckley let's look to release a next SEMVER version number on this once we've cleared outstanding PRs etc. Would we consider any of the merged PRs as breaking changes to the public APIs?
@camfindlay I'd go with a breaking change, with this set of PRs we've enabled CSRF tokens in places they weren't being loaded before and changed which headers we read from. I'd prefer people explicitly choose to get these changes.
Release an appropriately SEMVER tagged next version based on merged PRs since last tagged version.