futurestudio/hapi-rate-limitor
### [`v3.1.1`](https://togithub.com/futurestudio/hapi-rate-limitor/blob/master/CHANGELOG.md#311-httpsgithubcomfuturestudiohapi-rate-limitorcomparev310v311---2020-08-05)
[Compare Source](https://togithub.com/futurestudio/hapi-rate-limitor/compare/v3.1.0...v3.1.1)
##### Updated
- bump dependencies
- minor code refinements
- replaced `request-ip` dependency with `@supercharge/request-ip` providing improved request IP detection
### [`v3.1.0`](https://togithub.com/futurestudio/hapi-rate-limitor/blob/master/CHANGELOG.md#310-httpsgithubcomfuturestudiohapi-rate-limitorcomparev300v310---2020-06-01)
[Compare Source](https://togithub.com/futurestudio/hapi-rate-limitor/compare/v3.0.0...v3.1.0)
##### Updated
- refined route-specific rate limit handling
- bump dependencies
##### Possible Breaking Changes
This release introduces an updated handling route-level max attempts.
**Previously**, the default (server-wide) rate limit affected route-level rate limits.
**Now**, the route-level rate limits are independend and not affected by the default rate limit.
Example: you have a `/login` route with `{ max: 10 }` configuration and your default configuration is `{ max: 60 }`. In the previous version, any request to other pages than `/login` would affect the max limit of 10 requests for the `/login` route. This behavior may have eaten all 10 requests already before even visiting the `/login` route. This new version handles the `/login` route independently from other pages because it has its own `max` configuration.
This changed handling may introduce a breaking change for your app if you previously worked around that issue. Sorry, if I’m causing you trouble. I’m releasing this version as a minor release in the `2.x` and `3.x` release lines. In case you’re using tilde (`~`) in your `package.json` file, you’re not directly updated to this version when running `npm install`.
### [`v3.0.0`](https://togithub.com/futurestudio/hapi-rate-limitor/blob/master/CHANGELOG.md#300-httpsgithubcomfuturestudiohapi-rate-limitorcomparev2120v300---2020-01-10)
[Compare Source](https://togithub.com/futurestudio/hapi-rate-limitor/compare/v2.13.0...v3.0.0)
##### Updated
- bump dependencies
- refined description in `package.json`
##### Breaking Changes
- require Node.js v12
- this change aligns with the hapi ecosystem requiring Node.js v12 with the release of hapi 19
Renovate configuration
:date: Schedule: "every 2 weeks on Monday before 7am" in timezone Europe/Berlin.
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
:no_bell: 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:
2.13.0->3.1.1Release Notes
futurestudio/hapi-rate-limitor
### [`v3.1.1`](https://togithub.com/futurestudio/hapi-rate-limitor/blob/master/CHANGELOG.md#311-httpsgithubcomfuturestudiohapi-rate-limitorcomparev310v311---2020-08-05) [Compare Source](https://togithub.com/futurestudio/hapi-rate-limitor/compare/v3.1.0...v3.1.1) ##### Updated - bump dependencies - minor code refinements - replaced `request-ip` dependency with `@supercharge/request-ip` providing improved request IP detection ### [`v3.1.0`](https://togithub.com/futurestudio/hapi-rate-limitor/blob/master/CHANGELOG.md#310-httpsgithubcomfuturestudiohapi-rate-limitorcomparev300v310---2020-06-01) [Compare Source](https://togithub.com/futurestudio/hapi-rate-limitor/compare/v3.0.0...v3.1.0) ##### Updated - refined route-specific rate limit handling - bump dependencies ##### Possible Breaking Changes This release introduces an updated handling route-level max attempts. **Previously**, the default (server-wide) rate limit affected route-level rate limits. **Now**, the route-level rate limits are independend and not affected by the default rate limit. Example: you have a `/login` route with `{ max: 10 }` configuration and your default configuration is `{ max: 60 }`. In the previous version, any request to other pages than `/login` would affect the max limit of 10 requests for the `/login` route. This behavior may have eaten all 10 requests already before even visiting the `/login` route. This new version handles the `/login` route independently from other pages because it has its own `max` configuration. This changed handling may introduce a breaking change for your app if you previously worked around that issue. Sorry, if I’m causing you trouble. I’m releasing this version as a minor release in the `2.x` and `3.x` release lines. In case you’re using tilde (`~`) in your `package.json` file, you’re not directly updated to this version when running `npm install`. ### [`v3.0.0`](https://togithub.com/futurestudio/hapi-rate-limitor/blob/master/CHANGELOG.md#300-httpsgithubcomfuturestudiohapi-rate-limitorcomparev2120v300---2020-01-10) [Compare Source](https://togithub.com/futurestudio/hapi-rate-limitor/compare/v2.13.0...v3.0.0) ##### Updated - bump dependencies - refined description in `package.json` ##### Breaking Changes - require Node.js v12 - this change aligns with the hapi ecosystem requiring Node.js v12 with the release of hapi 19Renovate configuration
:date: Schedule: "every 2 weeks on Monday before 7am" in timezone Europe/Berlin.
:vertical_traffic_light: Automerge: Disabled by config. Please merge this manually once you are satisfied.
:recycle: Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
:no_bell: 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.