Bump follow-redirects from 1.13.1 to 1.14.8

[dependabot]

Bumps follow-redirects from 1.13.1 to 1.14.8.

Commits

• 3d81dc3 Release version 1.14.8 of the npm package.
• 62e546a Drop confidential headers across schemes.
• 2ede36d Release version 1.14.7 of the npm package.
• 8b347cb Drop Cookie header across domains.
• 6f5029a Release version 1.14.6 of the npm package.
• af706be Ignore null headers.
• d01ab7a Release version 1.14.5 of the npm package.
• 40052ea Make compatible with Node 17.
• 86f7572 Fix: clear internal timer on request abort to avoid leakage
• 2e1eaf0 Keep Authorization header on subdomain redirects.
• Additional commits viewable 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 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)
• @dependabot use these labels will set the current labels as the default for future PRs for this repo and language
• @dependabot use these reviewers will set the current reviewers as the default for future PRs for this repo and language
• @dependabot use these assignees will set the current assignees as the default for future PRs for this repo and language
• @dependabot use this milestone will set the current milestone as the default for future PRs for this repo and language

You can disable automated security fix PRs for this repo from the Security Alerts page.

[halkeye]

@MarkEWaite are we any closer to shutting this service down?

[MarkEWaite]

@halkeye the only use that I'm making of this service is to count the number of plugins that have completed the migration from wiki docs to GitHub based docs.

The developer guide for plugin docs and the Hacktoberfest docs suggest this as a location to find the list of plugins that still need to have their documentation converted.

Could we store (and periodically update) the list of plugins not yet converted in another location? I could count the items in the list for my monthly progress tracking and we could stop this service.

[zbynek]

Could we store (and periodically update) the list of plugins not yet converted in another location

it could be done as a part of the plugin website (so release cycle would be the same as plugins.jenkins.io)

[halkeye]

the plugin site doesn't have github credentials. It should move to reports.jenkins.io

lookx like its all docker, so it can easily run node

https://github.com/jenkins-infra/infra-reports/blob/master/Jenkinsfile

[zbynek]

well I thought we don't need any credentials? We just need to check which documentation URLs match github.com/jenkinsci in a similar way to the current progress table.

[halkeye]

Doesn't the progress table check to see how many PRs are in place, and which ones are connected to the project, and all the other things?

i guess where it goes depends on what actually is needed.

Right now the docs URLs are the old wiki link until jenkins-infra/update-center2#548 is merged.

[MarkEWaite]

Doesn't the progress table check to see how many PRs are in place, and which ones are connected to the project, and all the other things?

It does, but I don't need that information for my use case and I'm not aware of anyone else that needs it.

I need to know how many plugins have been converted to GitHub documentation and how many remain to be converted.

Contributors need to know which plugins have not yet been converted (preferably ordered by some interesting attribute like the number of installations)

[halkeye]

this should get updated back to https://community.jenkins.io/t/are-we-good-to-shutdown-wiki-exporter-now/447/11

I still think the best is to just run something on trusted to create a static .HTML file with the existing functionality.

[dependabot]

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.