chore(deps): update dependency passport to v0.6.0

[renovate]

This PR contains the following updates:

Package	Change	Age	Adoption	Passing	Confidence
passport (source)	^0.4.0 || ^0.5.0 -> ^0.4.0 || ^0.5.0 || ^0.6.0
passport (source)	0.5.3 -> 0.6.0

---

Release Notes

jaredhanson/passport

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

---

Configuration

📅 Schedule: 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 these updates again.

---

• If you want to rebase/retry this PR, click this checkbox.

---

This PR has been generated by WhiteSource Renovate. View repository job log here.

[Shinigami92]

Oh hello 🙂 I just woke up and started working
Saw that passport v0.6.0 needs to be supported and checked this repo
Seems you merged it just 8min ago 🚀
Can I expect a release in next few minutes? If so, I will wait until that and update a whole bunch of deps in my project.
Thanks for your support ❤️

[Shinigami92]

Is there a target release date?

[Shinigami92]

@kamilmysliwiec Any reason why this was not released yet?

[drdreo]

Getting peer dependency issues when installing 8.2.1. Seems the 0.6.0 peer is still not out.

npm ERR! peer passport@"^0.4.0 || ^0.5.0" from @nestjs/passport@8.2.1

[orgads]

Please release.

[Shinigami92]

@kamilmysliwiec why is the release blocked? I can understand that questions like "any new updates" or similar are annoying.
But in this case, it is already merged and on the main branch, so we cant event open PRs to try to fix something ourself and help via OpenSource contribution.
So we depend on you to publish the release.