Bump follow-redirects from 1.15.2 to 1.15.5

[dependabot]

Bumps follow-redirects from 1.15.2 to 1.15.5.

Commits

• b1677ce Release version 1.15.5 of the npm package.
• d8914f7 Preserve fragment in responseUrl.
• 6585820 Release version 1.15.4 of the npm package.
• 7a6567e Disallow bracketed hostnames.
• 05629af Prefer native URL instead of deprecated url.parse.
• 1cba8e8 Prefer native URL instead of legacy url.resolve.
• 72bc2a4 Simplify _processResponse error handling.
• 3d42aec Add bracket tests.
• bcbb096 Do not directly set Error properties.
• 192dbe7 Release version 1.15.3 of the npm package.
• Additional commits viewable in compare view

You can trigger a rebase of this PR by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)
  You can disable automated security fix PRs for this repo from the Security Alerts page.

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

[filip326]

Why is the package-lock even in the repo?

[filip326]

I taught we are using yarn, aren't we?

[chfuchte]

simply because it's not in the gitignore

[chfuchte]

no. we are using npm since we (you and me) started using yarn (the superior node package manager) in 2023 and the project started in 2022

[filip326]

no. we are using npm since we (you and me) started using yarn (the superior node package manager) in 2023 and the project started in 2022

In this project we always used yarn

[filip326]

I can prove it since the yarn.lock is mentioned by mickhat in the gitignore 2 year ago already

no. we are using npm since we (you and me) started using yarn (the superior node package manager) in 2023 and the project started in 2022

In this project we always used yarn

[chfuchte]

https://github.com/Mickhat/FloBot/blob/master/Dockerfile

take a closer look in the actions, the package.json and the Dockerfile ;)

[filip326]

Maybe we should "unignore" the yarn lock and ignore the package-lock, since we are using yarn

[chfuchte]

in any case. the package-lock.json is on github and is required for the actions to work properly

[filip326]

https://github.com/Mickhat/FloBot/blob/master/Dockerfile

take a closer look in the actions, the package.json and the Dockerfile ;)

I still think we should use yarn instead of npm, also in the Dockerfile.

Maybe a task for @oglimmer ?

[chfuchte]

still. that's a discussion for the issue not the PR of dependabot

[dependabot]

Superseded by #102.