Open renovate[bot] opened 3 months ago
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
The artifact failure details are included below:
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: eslint-config-airbnb@15.1.0
npm error Found: eslint-plugin-jsx-a11y@6.0.2
npm error node_modules/eslint-plugin-jsx-a11y
npm error dev eslint-plugin-jsx-a11y@"6.0.2" from the root project
npm error
npm error Could not resolve dependency:
npm error peer eslint-plugin-jsx-a11y@"^5.1.1" from eslint-config-airbnb@15.1.0
npm error node_modules/eslint-config-airbnb
npm error dev eslint-config-airbnb@"15.1.0" from the root project
npm error
npm error Conflicting peer dependency: eslint-plugin-jsx-a11y@5.1.1
npm error node_modules/eslint-plugin-jsx-a11y
npm error peer eslint-plugin-jsx-a11y@"^5.1.1" from eslint-config-airbnb@15.1.0
npm error node_modules/eslint-config-airbnb
npm error dev eslint-config-airbnb@"15.1.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /tmp/renovate/cache/others/npm/_logs/2024-08-06T10_43_32_854Z-eresolve-report.txt
npm error A complete log of this run can be found in: /tmp/renovate/cache/others/npm/_logs/2024-08-06T10_43_32_854Z-debug-0.log
Cross-site scripting vulnerabilities occur when unescaped input is rendered into a page displayed to the user. When HTML or script is included in the input, it will be processed by a user's browser as HTML or script and can alter the appearance of the page or execute malicious scripts in their user context.
A race condition is a flaw that produces an unexpected result when the timing of actions impact other actions.
[!WARNING]
Rate limit exceeded
@renovate[bot] has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 21 minutes and 20 seconds before requesting another review.
How to resolve this issue?
After the wait time has elapsed, a review can be triggered using the `@coderabbitai review` command as a PR comment. Alternatively, push new commits to this PR. We recommend that you space out your commits to avoid hitting the rate limit.How do rate limits work?
CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our [FAQ](https://coderabbit.ai/docs/faq) for further information.Commits
Files that changed from the base of the PR and between c8019ab50b50d0ee7a5a09e9baec39440d21c9fc and 4e39b37ce51585dd4653f3b87b493822fab43021.
Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?
This PR contains the following updates:
0.4.0
->0.6.0
GitHub Vulnerability Alerts
CVE-2022-25896
This affects the package passport before 0.6.0. When a user logs in or logs out, the session is regenerated instead of being closed.
Release Notes
jaredhanson/passport (passport)
### [`v0.6.0`](https://redirect.github.com/jaredhanson/passport/blob/HEAD/CHANGELOG.md#060---2022-05-20) [Compare Source](https://redirect.github.com/jaredhanson/passport/compare/v0.5.3...v0.6.0) ##### Added - `authenticate()`, `req#login`, and `req#logout` accept a `keepSessionInfo: true` option to keep session information after regenerating the session. ##### Changed - `req#login()` and `req#logout()` regenerate the the session and clear session information by default. - `req#logout()` is now an asynchronous function and requires a callback function as the last argument. ##### Security - Improved robustness against session fixation attacks in cases where there is physical access to the same system or the application is susceptible to cross-site scripting (XSS). ### [`v0.5.3`](https://redirect.github.com/jaredhanson/passport/blob/HEAD/CHANGELOG.md#053---2022-05-16) [Compare Source](https://redirect.github.com/jaredhanson/passport/compare/v0.5.2...v0.5.3) ##### Fixed - `initialize()` middleware extends request with `login()`, `logIn()`, `logout()`, `logOut()`, `isAuthenticated()`, and `isUnauthenticated()` functions again, reverting change from 0.5.1. ### [`v0.5.2`](https://redirect.github.com/jaredhanson/passport/blob/HEAD/CHANGELOG.md#052---2021-12-16) [Compare Source](https://redirect.github.com/jaredhanson/passport/compare/v0.5.1...v0.5.2) ##### Fixed - Introduced a compatibility layer for strategies that depend directly on `passport@0.4.x` or earlier (such as `passport-azure-ad`), which were broken by the removal of private variables in `passport@0.5.1`. ### [`v0.5.1`](https://redirect.github.com/jaredhanson/passport/blob/HEAD/CHANGELOG.md#051---2021-12-15) [Compare Source](https://redirect.github.com/jaredhanson/passport/compare/v0.5.0...v0.5.1) ##### Added - Informative error message in session strategy if session support is not available. ##### Changed - `authenticate()` middleware, rather than `initialize()` middleware, extends request with `login()`, `logIn()`, `logout()`, `logOut()`, `isAuthenticated()`, and `isUnauthenticated()` functions. ### [`v0.5.0`](https://redirect.github.com/jaredhanson/passport/blob/HEAD/CHANGELOG.md#050---2021-09-23) [Compare Source](https://redirect.github.com/jaredhanson/passport/compare/v0.4.1...v0.5.0) ##### Changed - `initialize()` middleware extends request with `login()`, `logIn()`, `logout()`, `logOut()`, `isAuthenticated()`, and `isUnauthenticated()` functions. ##### Removed - `login()`, `logIn()`, `logout()`, `logOut()`, `isAuthenticated()`, and `isUnauthenticated()` functions no longer added to `http.IncomingMessage.prototype`. ##### Fixed - `userProperty` option to `initialize()` middleware only affects the current request, rather than all requests processed via singleton Passport instance, eliminating a race condition in situations where `initialize()` middleware is used multiple times in an application with `userProperty` set to different values. [Unreleased]: https://redirect.github.com/jaredhanson/passport/compare/v0.6.0...HEAD [0.6.0]: https://redirect.github.com/jaredhanson/passport/compare/v0.5.3...v0.6.0 [0.5.3]: https://redirect.github.com/jaredhanson/passport/compare/v0.5.2...v0.5.3 [0.5.2]: https://redirect.github.com/jaredhanson/passport/compare/v0.5.1...v0.5.2 [0.5.1]: https://redirect.github.com/jaredhanson/passport/compare/v0.5.0...v0.5.1 ### [`v0.4.1`](https://redirect.github.com/jaredhanson/passport/compare/v0.4.0...v0.4.1) [Compare Source](https://redirect.github.com/jaredhanson/passport/compare/v0.4.0...v0.4.1)Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - 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 was generated by Mend Renovate. View the repository job log.