search

FGRibreau / mixpanel-cli

🎩 mixpanel-cli - A complete CLI to query Mixpanel API
https://twitter.com/FGRibreau
10 stars 1 forks source link

build(deps): bump mixpanel from 0.5.0 to 0.11.0 #18

Open dependabot-preview[bot] opened 4 years ago

dependabot-preview[bot] commented 4 years ago

Bumps mixpanel from 0.5.0 to 0.11.0.

Release notes *Sourced from [mixpanel's releases](https://github.com/mixpanel/mixpanel-node/releases).* > ## Support for Groups API > This release adds support for Mixpanel [Groups](https://help.mixpanel.com/hc/en-us/articles/360025333632), through the `mixpanel.groups` object, analogous to `mixpanel.people`. For projects which have groups support enabled, you can send group profile updates via calls such as: > ```js > mixpanel.groups.set('company', 'Acme Inc.', { > 'Industry': 'widgets', > '$name': 'Acme Inc.', > }); > > mixpanel.groups.remove('company', 'Acme Inc.', { > 'products': 'anvil', > 'customer segments': 'coyotes' > }); > > mixpanel.groups.delete_group('company', 'Acme Inc.'); > > // etc > ``` > > ## Support for configurable API path > Configure when initializing the instance with the `path` option: > ```js > const mixpanel = Mixpanel.init(`YOUR TOKEN`, { > host: `sweet-corporate-proxy:6000`, > path: `/mixpanel`, > }); > ``` > In the above example, tracking requests will go to `https://sweet-corporate-proxy:6000/mixpanel/track`. > > ## Dropped Node.js 4 support > No release notes provided. > > ## Add type declarations file > At https://github.com/mixpanel/mixpanel-node/blob/master/lib/mixpanel-node.d.ts > > ## https-proxy-agent upgraded to v2.2.1 for security fix > See https://snyk.io/vuln/npm:https-proxy-agent:20180402 > > ## Batch tracking and proxy support > - `track_batch` uses the track endpoint to record multiple events at once. These events must be more recent than 5 days old; for older events, use the existing `import_batch` method. > ```js > mixpanel.track_batch([ > {event: 'event 1', properties: {color: 'blue'}}, > {event: 'event 2'}, > ]); > ``` > - The address of an HTTP(S) proxy server can be specified in the environment variable `HTTPS_PROXY` or `HTTP_PROXY`; if present, the library will route requests through the proxy. > - Support has been dropped for Node.js v0.10 and v0.12. These versions reached the end of their maintenance periods in October and December 2016 respectively (see https://github.com/nodejs/LTS). > > ## Support for time prop with track endpoint > This allows you to specify the `time` property of an event when calling `mixpanel.track()` and still hit the `/track` endpoint (meaning that you only need the project's publishable Mixpanel token, not its private API key). > ... (truncated)
Changelog *Sourced from [mixpanel's changelog](https://github.com/mixpanel/mixpanel-node/blob/master/history.md).* > 0.10.3 / 2019-10-09 > ================== > * upgrade https-proxy-agent for security fix (thanks omrilotan) > > 0.10.2 / 2019-03-26 > ================== > * type definitions for people.unset (thanks bradleyayers) > > 0.10.1 / 2018-12-03 > ================== > * support configurable API path (thanks CameronDiver) > > 0.9.2 / 2018-05-22 > ================== > * add type declarations file (thanks mklopets) > > 0.9.1 / 2018-04-12 > ================== > * upgrade https-proxy-agent for security fix > > 0.9.0 / 2018-02-09 > ================== > * default to tracking over HTTPS (thanks jhermsmeier) > > 0.8.0 / 2017-11-28 > ================== > * upgraded node-https-proxy-agent to v2.1.1 for security patch (see > https://github-redirect.dependabot.com/TooTallNate/node-https-proxy-agent/issues/37) > > 0.7.0 / 2017-04-07 > =================== > * added `track_batch` for tracking multiple recent events per request (thanks cruzanmo) > * support for routing requests through proxy server specified in env var `HTTPS_PROXY` > or `HTTP_PROXY` (thanks colestrode) > * dropped support for node 0.10 and 0.12 > > 0.6.0 / 2017-01-03 > =================== > * support for `time` field in `mixpanel.track()` (thanks cruzanmo)
Commits - [`4c63934`](https://github.com/mixpanel/mixpanel-node/commit/4c639349fa635a79bad2ed0695d5c5b44897fdcc) 0.11.0 - [`b3065df`](https://github.com/mixpanel/mixpanel-node/commit/b3065df9a092e17e91443c53e8e4c255d13478ef) YayC example suggestions - [`393df95`](https://github.com/mixpanel/mixpanel-node/commit/393df9516ce8692ad43bc014ed27025aa4a2eb3a) missed a few deprecated comments - [`d791f2f`](https://github.com/mixpanel/mixpanel-node/commit/d791f2f3baf9b1870aef352df612ad6bec1dc312) remove create_config and fix set_config - [`b4234c5`](https://github.com/mixpanel/mixpanel-node/commit/b4234c527cc378cd4a1536b6d8a00a2704ebafa0) comments - [`74b07a4`](https://github.com/mixpanel/mixpanel-node/commit/74b07a461ffc9be7b07e3d1a6a2ea1e5fc2acbba) don't have to send endpoint param everywhere - [`610a2d7`](https://github.com/mixpanel/mixpanel-node/commit/610a2d750ce2f98e7c6ad0b81c6efa73e0528fc6) use mixin instead of profile_helpers factory - [`5c2a467`](https://github.com/mixpanel/mixpanel-node/commit/5c2a46786e0da4df41740c29c0f64d587c1b93b2) mp_instance -> mixpanel - [`fb99af4`](https://github.com/mixpanel/mixpanel-node/commit/fb99af494d8b3f8dd5b2743659c1ab5652002f3f) revert unnecessary send_request-factory - [`9d71057`](https://github.com/mixpanel/mixpanel-node/commit/9d71057dc7c1a98ba6ae80897d9abd216cb0edef) refactor 2: consistency between groups and people - Additional commits viewable in [compare view](https://github.com/mixpanel/mixpanel-node/compare/v0.5.0...v0.11.0)


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 will not automatically merge this PR because this dependency is pre-1.0.0.

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 - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Pull request limits (per update run and/or open at any time) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired)