Bump follow-redirects from 1.15.4 to 1.15.6

[dependabot[bot]]

Bumps follow-redirects from 1.15.4 to 1.15.6.

Commits

• 35a517c Release version 1.15.6 of the npm package.
• c4f847f Drop Proxy-Authorization across hosts.
• 8526b4a Use GitHub for disclosure.
• b1677ce Release version 1.15.5 of the npm package.
• d8914f7 Preserve fragment in responseUrl.
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually 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 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](https://github.com/privacy-tech-lab/privacy-pioneer/network/alerts).

[SebastianZimmeck]

Not sure if this is again the GitHub Action failing here, @natelevinson10 and @JoeChampeau.

[JoeChampeau]

It looks like the access issue for the API token is fixed, but now it's throwing the error: SyntaxError: /home/runner/work/privacy-pioneer/privacy-pioneer/src/libs/holdAPI.js: Identifier directly after number. (1:28) @SebastianZimmeck Do you know if the value for APIIPTOKEN was wrapped in quotes? I don't actually know whether or not that's necessary, but it's possible that without them the value is not being properly interpreted as a string.

[SebastianZimmeck]

@JoeChampeau, yes, I have it in double quotes. For me, the holdAPI.js has one line of code as follows:

export const apiIPToken = "replace with token";

But who knows, maybe some formatting change there may do the trick.

[JoeChampeau]

To clarify @SebastianZimmeck, I'm referring to the value held under the APIIPTOKEN secret stored in Settings > Secrets and variables > Depandabot > Repository secrets > APIIPTOKEN. Do you know if that one was submitted in double quotes?

[SebastianZimmeck]

Ah, OK! I do not recall. I just checked, but GitHub does not show the value. So, I just updated it including the quotes.

Let me know, @JoeChampeau, if I should update it without the quotes.

[JoeChampeau]

@dependabot recreate

[JoeChampeau]

@SebastianZimmeck That seems to have fixed it!