search

Shopify / koa-shopify-auth

DEPRECATED Middleware to authenticate a Koa application with Shopify
MIT License
80 stars 63 forks source link

Bump node-fetch from 2.6.0 to 2.6.7 #146

Closed dependabot[bot] closed 1 year ago

dependabot[bot] commented 2 years ago

Bumps node-fetch from 2.6.0 to 2.6.7.

Release notes

Sourced from node-fetch's releases.

v2.6.7

Security patch release

Recommended to upgrade, to not leak sensitive cookie and authentication header information to 3th party host while a redirect occurred

What's Changed

Full Changelog: https://github.com/node-fetch/node-fetch/compare/v2.6.6...v2.6.7

v2.6.6

What's Changed

Full Changelog: https://github.com/node-fetch/node-fetch/compare/v2.6.5...v2.6.6

v2.6.2

fixed main path in package.json

v2.6.1

This is an important security release. It is strongly recommended to update as soon as possible.

See CHANGELOG for details.

Commits
  • 1ef4b56 backport of #1449 (#1453)
  • 8fe5c4e 2.x: Specify encoding as an optional peer dependency in package.json (#1310)
  • f56b0c6 fix(URL): prefer built in URL version when available and fallback to whatwg (...
  • b5417ae fix: import whatwg-url in a way compatible with ESM Node (#1303)
  • 18193c5 fix v2.6.3 that did not sending query params (#1301)
  • ace7536 fix: properly encode url with unicode characters (#1291)
  • 152214c Fix(package.json): Corrected main file path in package.json (#1274)
  • b5e2e41 update version number
  • 2358a6c Honor the size option after following a redirect and revert data uri support
  • 8c197f8 docs: Fix typos and grammatical errors in README.md (#686)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by endless, a new releaser for node-fetch since your current version.


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) - `@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](https://github.com/Shopify/koa-shopify-auth/network/alerts).
dependabot[bot] commented 1 year ago

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.

shopify-shipitnext[bot] commented 1 year ago

Shopify Merge Queue takes care of merging pull requests in this repository. Once you are ready to ship this PR, comment /shipit to enqueue this PR for merging.

If /shipit does not work, you can also ship PRs by going to your Shipit Next PR page and clicking on the Ship It button in the corner.

### Command Comments - `/shipit`: Enqueue the PR for merging - `/cancel`: Cancel an enqueued merge - `/shipit --emergency`: Skip the queue and merge directly ### Merge process Shopify Merge Queue will follow these steps to get a PR merged: 1. It will check whether this pull request follows our process and best practices. CI should be green, and the PR should have at least one approved review. 2. It places the PR in the queue. Other PRs that have been enqueued before will have priority. 3. Once it is this PR's turn, it will create merge commits of what `main` could look like after this PR is merged in combination with a batch of other PRs that are queued up. 4. It will then wait for CI to run on those merge commits. Once one of them comes back green, it will fast-forward the `main` branch to point to that commit. Your PR will be marked as merged. 5. Because CI already successfully ran on this merge commit, main is always green and the PR will be ready to be deployed right away. This process will make sure that all PRs are treated equally when many are ready to be merged around the same time, and will make sure the CI status of the main branch is always green. #### Notes - Shopify Merge Queue publishes a CI status on your PR to keep you up to date with what is going on during the process. - If anything goes wrong in this process, Shopify Merge Queue will leave a comment on the PR. - Comment `/cancel` if you change your mind and want to stop the PR from being merged. ### Emergency merging If, **in case of emergency**, you want to bypass the queue and get a PR merged as quickly as possible, `/shipit --emergency` instead. Shopify Merge Queue will ignore CI and reviews for the PR, and merge it directly to the main branch. Afterwards, somebody may ask you why this was an emergency that warranted skipping the queue. Note that an emergency merge invalidates all merge commits that the merge queue created for other PRs, because they are based on a specific main SHA. Shopify Merge Queue will have to create new merge commits for those PRs based on the new main SHA, and restart CI on all of them. This reduces throughput significantly, so please only use the emergency procedure for real emergencies. ### Questions or feedback? If you have any questions or feedback, please visit the [#help-eng-infrastructure](https://shopify.slack.com/archives/C01MXHNTT4Z) in Slack.

View more details at https://shipit-next.shopifycloud.com/Shopify/koa-shopify-auth/pull/146.