github-starred/awesome-docker
2
0
Fork 0
mirror of https://github.com/veggiemonk/awesome-docker.git synced 2026-03-09 07:25:57 -05:00
Code Issues 5 Packages Projects Releases 1 Wiki Activity

[PR #1014] [MERGED] Bump node-fetch from 3.2.8 to 3.2.9 #1025

New Issue
Closed
opened 2025-11-06 12:13:09 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-06 12:13:09 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/veggiemonk/awesome-docker/pull/1014
Author: @dependabot[bot]
Created: 7/19/2022
Status: ✅ Merged
Merged: 7/19/2022
Merged by: @agebhar1

Base: master ← Head: dependabot/npm_and_yarn/node-fetch-3.2.9

📝 Commits (1)

  • 45331ba Bump node-fetch from 3.2.8 to 3.2.9

📊 Changes

2 files changed (+8 additions, -8 deletions)

View changed files

📝 package-lock.json (+7 -7)
📝 package.json (+1 -1)

📄 Description

Bumps node-fetch from 3.2.8 to 3.2.9.

Release notes

Sourced from node-fetch's releases.

v3.2.9

3.2.9 (2022-07-18)

Bug Fixes

  • Headers: don't forward secure headers on protocol change (#1599) (e87b093)
Commits

Dependabot compatibility score

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)

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/veggiemonk/awesome-docker/pull/1014 **Author:** [@dependabot[bot]](https://github.com/apps/dependabot) **Created:** 7/19/2022 **Status:** ✅ Merged **Merged:** 7/19/2022 **Merged by:** [@agebhar1](https://github.com/agebhar1) **Base:** `master` ← **Head:** `dependabot/npm_and_yarn/node-fetch-3.2.9` --- ### 📝 Commits (1) - [`45331ba`](https://github.com/veggiemonk/awesome-docker/commit/45331ba031c44c967a58b88d753ce7603ac8dc31) Bump node-fetch from 3.2.8 to 3.2.9 ### 📊 Changes **2 files changed** (+8 additions, -8 deletions) <details> <summary>View changed files</summary> 📝 `package-lock.json` (+7 -7) 📝 `package.json` (+1 -1) </details> ### 📄 Description Bumps [node-fetch](https://github.com/node-fetch/node-fetch) from 3.2.8 to 3.2.9. <details> <summary>Release notes</summary> <p><em>Sourced from <a href="https://github.com/node-fetch/node-fetch/releases">node-fetch's releases</a>.</em></p> <blockquote> <h2>v3.2.9</h2> <h2><a href="https://github.com/node-fetch/node-fetch/compare/v3.2.8...v3.2.9">3.2.9</a> (2022-07-18)</h2> <h3>Bug Fixes</h3> <ul> <li><strong>Headers:</strong> don't forward secure headers on protocol change (<a href="https://github-redirect.dependabot.com/node-fetch/node-fetch/issues/1599">#1599</a>) (<a href="https://github.com/node-fetch/node-fetch/commit/e87b093fd678a9ea39c5b17b2a1bdfc4691eedc7">e87b093</a>)</li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/node-fetch/node-fetch/commit/e87b093fd678a9ea39c5b17b2a1bdfc4691eedc7"><code>e87b093</code></a> fix(Headers): don't forward secure headers on protocol change (<a href="https://github-redirect.dependabot.com/node-fetch/node-fetch/issues/1599">#1599</a>)</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/bcfb71c7d10da252280d13818daab6925e12c368"><code>bcfb71c</code></a> chore: remove triple-slash directives from typings (<a href="https://github-redirect.dependabot.com/node-fetch/node-fetch/issues/1285">#1285</a>) (<a href="https://github-redirect.dependabot.com/node-fetch/node-fetch/issues/1287">#1287</a>)</li> <li><a href="https://github.com/node-fetch/node-fetch/commit/95165d5480ea0552858679a96c7f4ef001412c1b"><code>95165d5</code></a> fix spelling (<a href="https://github-redirect.dependabot.com/node-fetch/node-fetch/issues/1602">#1602</a>)</li> <li>See full diff in <a href="https://github.com/node-fetch/node-fetch/compare/v3.2.8...v3.2.9">compare view</a></li> </ul> </details> <br /> [![Dependabot compatibility score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=node-fetch&package-manager=npm_and_yarn&previous-version=3.2.8&new-version=3.2.9)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores) 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-automerge-start) [//]: # (dependabot-automerge-end) --- <details> <summary>Dependabot commands and options</summary> <br /> 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) </details> --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-11-06 12:13:09 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
broken-links
bug
cannot be evaluated
enhancement
health-report
help wanted
maintenance
pending-evaluation
pull-request
Mirrored from GitHub Pull Request
 question
team discussion
weekly-digest
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/awesome-docker#1025
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?