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

[NEUTRAL] Update dependency pusher-js to v8 #811

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

Conversation

mend-for-github-com[bot]
Copy link

@mend-for-github-com mend-for-github-com bot commented Dec 22, 2022

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
pusher-js ^5.1.1 -> ^8.0.0 age adoption passing confidence

Release Notes

pusher/pusher-js (pusher-js)

v8.3.0

Compare Source

  • [CHANGED] Update cached re-connect strategy to prioritize WebSocket

v8.2.0

Compare Source

  • [CHANGED] Remove WebSocket retry limit.

v8.1.0

Compare Source

  • [CHANGED] Move @​types dependencies to devDependencies
  • [CHANGED] Upgrade typescript to 5.1.3

v8.0.2

Compare Source

  • [CHANGED] Fix React Native support.

v8.0.1

Compare Source

  • [FIXED] Fix 'window is not defined' error in the worker context
  • [FIXED] Specify the right status when an error is thrown for the pusher worker instance

v8.0.0

Compare Source

  • [CHANGED] Specifying a cluster when instantiating the Pusher object is now mandatory. An exception is thrown if the cluster setting is missing.

v7.6.0

Compare Source

  • [ADDED] Introduce headersProvider and paramsProvider to channel authorization and user authentication in order to allow for changing header and param values after the Pusher object is initialized.

v7.5.0

Compare Source

  • [ADDED] Watchlist Online Status

v7.4.1

Compare Source

  • [CHANGED] Authorization error message.

v7.4.0

Compare Source

  • [CHANGED] Use secure random generator instead of pseudo-random generator
  • [CHANGED] Replace git protocol with HTTPS in gitsubmodules file
  • [ADDED] Allow presence channel authorization to depend on user authentication

v7.3.0

Compare Source

  • [FIXED] Restore previously exported types

v7.2.0

Compare Source

  • [ADDED] Add support for subscription_count event

v7.0.6

Compare Source

  • [FIXED] pusher-js/worker can now be bundled and used in a web worker context

v7.0.5

Compare Source

  • [FIXED] pusher-js/worker is now built by webpack with umd libraryTarget, which
    allows it to be bundled as described in the README

v7.0.4

Compare Source

  • [FIXED] References to nonexistent source map #​570

v7.0.3

Compare Source

[UPDATED] Bumped version of faye-websocket (used only by the node runtime) from
0.9.4 to 0.11.3. Thanks to @​Akhawais for the PR.

[UPDATED] Bumped version of @​react-native-community/netinfo (used only by the
react-native runtime) from 4.1.1 to 5.9.7. Thanks to @​Yinabled for the PR.

[ADDED] We were missing a react-native key in package.json. Thanks to @​giaset
for the PR

[ADDED] Support for importing the worker builds (solving issue #​499)

v7.0.2

Compare Source

[FIXED] Removes AuthInfo type from react-native and with-encryption builds.
This type was removed everywhere else in v7.0.0. See issue
512

v7.0.1

Compare Source

[FIXED] Channels no longer get stuck in the subscriptionPending state
after a failed request to an auth endpoint. Fixes Issue
255

v7.0.0

Compare Source

[UPDATED] Type signatures for authorizer callback. Previously the authorizer
callback had 2 arguments, the first was a boolean indicating that the second
was an error. Switched for a more conventional function(err, data) signature.
This is a breaking change, if you use a custom authorizer

[UPDATED] Types of errors emitted on pusher:subscription_error events.
Previously this event just contained the status code the auth endpoint
returned. This was replaced with a (hopefully) more error object with a message
and a status key.
This is a breaking change, if you depend on the status in the
pusher:subscription_error event

[FIXED] Stop wrapping websocket errors multiple times. Fixes issue
464

This might be a breaking change, if you depend on the structure of 'error' events
emitted by pusher.connection

[FIXED] Stop swallowing errors thrown by handlers on encrypted channels.
Previously errors thrown by handlers bound to encrypted channels were caught
and ignored. This was unintentional and undesirable. Fixes Issue
437

v6.0.3

Compare Source

[FIXED] Added typescript declarations for the pusher-js/with-encryption build

[REMOVED] Unnecessary dummy tweetnacl types for react-native (thanks to
@​dmitrybirin)

[UPDATED] Copyright years (thanks to @​annzenkina)

v6.0.2

Compare Source

[FIXED] React-native import broken in release 6.0.1

v6.0.1

Compare Source

[CHANGED] Moved tweetnacl from devDependencies to dependencies. No
additional code is included in the bundle, but this gives the typescript
compiler access to the tweetnacl types

[FIXED] Typescript declarations for react-native. These were supposed to be
included in 6.0.0 but the commit was missed

v6.0.0

Compare Source

[CHANGED] The default builds for web and worker no longer support encrypted
channels. To use encrypted channels in web/worker you must import
pusher-js/with-encryption or use the
pusher-with-encryption.js/pusher-with-encryption.min.js bundles

[CHANGED] forceTLS now defaults to true

[REMOVED] the encrypted option - this was deprecated in 4.3.0. The library
defaults to TLS anyway. Setting encrypted to false will NOT change
behaviour

[FIXED] activityTimeout and pongTimeout options now work as described in
the docs.

[NEW] Typescript declarations for react-native

[NEW] Support for encrypted-channels in react-native and workers


Configuration

📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.


  • If you want to rebase/retry this PR, check this box

@mend-for-github-com mend-for-github-com bot changed the title chore(deps): update dependency pusher-js to v8 chore(deps): update dependency pusher-js to v8 - autoclosed Jun 14, 2023
@mend-for-github-com mend-for-github-com bot deleted the whitesource-remediate/pusher-js-8.x branch June 14, 2023 14:47
@mend-for-github-com mend-for-github-com bot changed the title chore(deps): update dependency pusher-js to v8 - autoclosed chore(deps): update dependency pusher-js to v8 Jun 14, 2023
@mend-for-github-com mend-for-github-com bot reopened this Jun 14, 2023
@mend-for-github-com mend-for-github-com bot restored the whitesource-remediate/pusher-js-8.x branch June 14, 2023 22:42
@mend-for-github-com mend-for-github-com bot changed the title chore(deps): update dependency pusher-js to v8 fix(deps): update dependency pusher-js to v8 Jun 15, 2023
@mend-for-github-com mend-for-github-com bot changed the title fix(deps): update dependency pusher-js to v8 [NEUTRAL] Update dependency pusher-js to v8 Oct 30, 2023
@mend-for-github-com mend-for-github-com bot force-pushed the whitesource-remediate/pusher-js-8.x branch from 60a77bc to 39adca4 Compare November 2, 2023 02:09
Copy link
Author

⚠ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: package-lock.json
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR! 
npm ERR! While resolving: zenbot4@4.1.0
npm ERR! Found: webpack@4.47.0
npm ERR! node_modules/webpack
npm ERR!   webpack@"^4.44.1" from the root project
npm ERR! 
npm ERR! Could not resolve dependency:
npm ERR! peer webpack@"^5.0.0" from postcss-loader@5.3.0
npm ERR! node_modules/postcss-loader
npm ERR!   postcss-loader@"^5.0.0" from the root project
npm ERR! 
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR! 
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/renovate/cache/others/npm/_logs/2023-11-02T02_09_43_851Z-debug-0.log

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

0 participants