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.10.3 #10

Closed dependabot-preview[bot] closed 4 years ago

dependabot-preview[bot] commented 4 years ago

Bumps mixpanel from 0.5.0 to 0.10.3.

Release notes *Sourced from [mixpanel's releases](https://github.com/mixpanel/mixpanel-node/releases).* > ## 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). > > This update comes with one minor breaking change: `mixpanel.track()` used to choose automatically between the `/import` and `/track` endpoints based on the presence or absence of the `time` property. Now it will always hit `/track`, and will throw an exception if the time is out of bounds (more than 5 days ago). For older events, of course, you can continue to use `mixpanel.import()`.
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 - [`a894a59`](https://github.com/mixpanel/mixpanel-node/commit/a894a5907fc8bd8b371706eac83f4a1ee2f1fc51) 0.10.3 - [`fb13fa9`](https://github.com/mixpanel/mixpanel-node/commit/fb13fa9a926d2f0a300ef87367381e20d26dff2c) changelog for 0.10.3 - [`81f19c2`](https://github.com/mixpanel/mixpanel-node/commit/81f19c27e5881a5bf1a3465d6180e1748371a44f) Upgrade to version 3 - [`c3a491b`](https://github.com/mixpanel/mixpanel-node/commit/c3a491bb2ea952ea95364e0a645102bb31397d67) Apply MitM security patch for https-proxy-agent - [`c9b776d`](https://github.com/mixpanel/mixpanel-node/commit/c9b776d55c3f14ca61269b96a16768e20d8ebe7e) 0.10.2 - [`4a4918c`](https://github.com/mixpanel/mixpanel-node/commit/4a4918c0540e2de211de75ed0cf6192aeca36ac1) https registry - [`69b62ff`](https://github.com/mixpanel/mixpanel-node/commit/69b62ff52746565bcc954bf6915938d8c8caebcd) add types for people.unset ([#151](https://github-redirect.dependabot.com/mixpanel/mixpanel-node/issues/151)) - [`5342966`](https://github.com/mixpanel/mixpanel-node/commit/5342966ac57c8563ddcc62a624f46eb3e3ead3e7) 0.10.1 - [`dda5f08`](https://github.com/mixpanel/mixpanel-node/commit/dda5f08b8f817a4974c9184316844003b64f58be) 0.10.1 changelog - [`468ceb3`](https://github.com/mixpanel/mixpanel-node/commit/468ceb39b3b42e9777060032400f78538712681f) custom path tests - Additional commits viewable in [compare view](https://github.com/mixpanel/mixpanel-node/compare/v0.5.0...v0.10.3)


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)
dependabot-preview[bot] commented 4 years ago

Superseded by #18.