Update dependency passport to ^0.7.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
passport (source)	^0.4.1 → ^0.7.0

---

Release Notes

jaredhanson/passport (passport)

v0.7.0

Compare Source

Changed

• Set req.authInfo by default when using the assignProperty option to
  authenticate() middleware. This makes the behavior the same as when not using
  the option, and can be disabled by setting authInfo option to false.

v0.6.0

Compare Source

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

Compare Source

Fixed

• initialize() middleware extends request with login(), logIn(),
  logout(), logOut(), isAuthenticated(), and isUnauthenticated() functions
  again, reverting change from 0.5.1.

v0.5.2

Compare Source

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

Compare Source

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.0

Compare Source

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.

---

Configuration

📅 Schedule: Branch creation - "on friday and saturday" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 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 was generated by Mend Renovate. View the repository job log.

[renovate]

⚠ Artifact update problem

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:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/passport@7.1.5
npm ERR! Found: passport@0.7.0
npm ERR! node_modules/passport
npm ERR!   passport@"^0.7.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer passport@"^0.4.0" from @nestjs/passport@7.1.5
npm ERR! node_modules/@nestjs/passport
npm ERR!   @nestjs/passport@"^7.1.5" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: passport@0.4.1
npm ERR! node_modules/passport
npm ERR!   peer passport@"^0.4.0" from @nestjs/passport@7.1.5
npm ERR!   node_modules/@nestjs/passport
npm ERR!     @nestjs/passport@"^7.1.5" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! 
npm ERR! For a full report see:
npm ERR! /tmp/worker/2d1a63/28f681/cache/others/npm/_logs/2023-11-28T01_13_54_466Z-eresolve-report.txt

npm ERR! A complete log of this run can be found in: /tmp/worker/2d1a63/28f681/cache/others/npm/_logs/2023-11-28T01_13_54_466Z-debug-0.log

[renovate]

⚠️ Artifact update problem

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:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json

npm ERR! code ERESOLVE
npm ERR! ERESOLVE could not resolve
npm ERR! 
npm ERR! While resolving: @nestjs/passport@7.1.5
npm ERR! Found: passport@0.7.0
npm ERR! node_modules/passport
npm ERR!   passport@"^0.7.0" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer passport@"^0.4.0" from @nestjs/passport@7.1.5
npm ERR! node_modules/@nestjs/passport
npm ERR!   @nestjs/passport@"^7.1.5" from the root project
npm ERR! 
npm ERR! Conflicting peer dependency: passport@0.4.1
npm ERR! node_modules/passport
npm ERR!   peer passport@"^0.4.0" from @nestjs/passport@7.1.5
npm ERR!   node_modules/@nestjs/passport
npm ERR!     @nestjs/passport@"^7.1.5" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /runner/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /runner/cache/others/npm/_logs/2026-06-11T11_47_44_910Z-debug-0.log