Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bump node-fetch and zapier-platform-core #3

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

dependabot[bot]
Copy link

@dependabot dependabot bot commented on behalf of github Apr 29, 2023

Bumps node-fetch to 2.6.7 and updates ancestor dependency zapier-platform-core. These dependencies need to be updated together.

Updates node-fetch from 1.7.1 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: node-fetch/node-fetch@v2.6.6...v2.6.7

v2.6.6

What's Changed

Full Changelog: node-fetch/node-fetch@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.

v2.6.0

See CHANGELOG.

v2.5.0

See CHANGELOG.

v2.4.1

See CHANGELOG.

v2.4.0

See CHANGELOG.

v2.3.0

See CHANGELOG.

v2.2.1

See CHANGELOG.

Version 2.1.2

  • Fix: allow Body methods to work on ArrayBuffer-backed Body` objects
  • Fix: reject promise returned by Body methods when the accumulated Buffer exceeds the maximum size
  • Fix: support custom Host headers with any casing
  • Fix: support importing fetch() from TypeScript in browser.js
  • Fix: handle the redirect response body properly

... (truncated)

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.


Updates zapier-platform-core from 8.3.0 to 14.0.0

Changelog

Sourced from zapier-platform-core's changelog.

14.0.0

released 2023-03-21

Version 14.0.0 is a breaking change release that contains several important upgrades and deprecations. Here is a brief breakdown of the changes (❗ denotes a breaking change):

  1. altersDynamicFields no longer defaults to true when dynamic is set. You should now set the flag appropriately. If a dynamic dropdown (i.e. a field with dynamic set) should refresh other input fields, you must set altersDynamicFields to true on v14.

    inputFields: [
      {
        key: 'city',
        dynamic: 'city.id.name',
        altersDynamicFields: true  // <- set this appropriately on v14
      }
    ]
    
  2. ❗ Before v14, the Zap editor didn't really use canPaginate. Instead, it made two requests and compared them to determine if pagination is supported. Starting from v14, canPaginate is required for the Zap editor to show the Load More button for pagination.

    triggers: {
      contact: {
        operation: {
          canPaginate: true  // <- set this appropriately on v14
        }
      }
    }
    
  3. ❗ Now you are required to provide meta information about your app, such as your intended audience and app category (if that information isn't already provided). If you are missing this information, you will be blocked from making updates to your integration (zapier promote, zapier upload, zapier push). Use zapier register with [email protected] or go to https://developer.zapier.com/app/{app_id}/version/{version}/settings to fill it out.

  4. On v14, OAuth2 implementation now supports PKCE! See our documentation for details.

Read on for a detailed set of release notes. Again, ❗ are BREAKING CHANGEs.

cli

  • ❗ Implement individual field flags for register command (#618)
  • ❗ Block promote, upload, and push for missing required app info (#612)
  • 💅 Use uniform field names in check-missing-app-info util (#630)
  • 💅 Only require fields for private integrations via CLI (#628)
  • 💅 Implement --yes flag for register command (#627)
  • 📜 Improve documentation on throttling (#631)
  • 📜 Add documentation for PKCE OAuth2 (#629)
  • 📜 Add information about how to return line items (#620)
  • 📜 Fix 'integraiton' typo in CLI docs (#613)

core

... (truncated)

Commits
  • 917c824 Bump cli, core, schema 13.0.0 -> 14.0.0
  • 4ecc8ca Update CHANGELOG.md for v14.0.0
  • eeff26f Merge pull request #631 from zapier/throttling_edits
  • 9050c0d SUPPORTENG_560_throttling_edits
  • 38a6093 Use uniform field names in check-missing-app-info util (#630)
  • f8ade5f Merge pull request #629 from zapier/pde-3244/pkce-documentation
  • 3303885 Tag supporting version for PKCE
  • 80bc4ec Add documentation for PKCE OAuth2
  • 4c7a6dd PDE-3822 feat(cli): Only require fields for private integrations via CLI (#628)
  • 9dd951f PDE-3733 feat(cli): Implement --yes flag for register command (#627)
  • Additional commits viewable in compare view
Maintainer changes

This version was pushed to npm by greg-zapier, a new releaser for zapier-platform-core since your current version.


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)
    You can disable automated security fix PRs for this repo from the Security Alerts page.

Bumps [node-fetch](https://github.com/node-fetch/node-fetch) to 2.6.7 and updates ancestor dependency [zapier-platform-core](https://github.com/zapier/zapier-platform). These dependencies need to be updated together.


Updates `node-fetch` from 1.7.1 to 2.6.7
- [Release notes](https://github.com/node-fetch/node-fetch/releases)
- [Commits](node-fetch/node-fetch@v1.7.1...v2.6.7)

Updates `zapier-platform-core` from 8.3.0 to 14.0.0
- [Release notes](https://github.com/zapier/zapier-platform/releases)
- [Changelog](https://github.com/zapier/zapier-platform/blob/main/CHANGELOG.md)
- [Commits](https://github.com/zapier/zapier-platform/compare/[email protected]@14.0.0)

---
updated-dependencies:
- dependency-name: node-fetch
  dependency-type: indirect
- dependency-name: zapier-platform-core
  dependency-type: direct:production
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Apr 29, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

0 participants