Bumps standard from 0.6.2 to 0.7. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/testdouble/standard/blob/master/CHANGELOG.md">standard's changelog</a>.</em></p> <blockquote> <h2>0.7</h2> <ul> <li>Update rubocop from 0.91.1 to <a href="https://github.com/rubocop-hq/rubocop/releases/tag/v0.92">0.92</a></li> </ul> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/testdouble/standard/commit/c392b209d20aa77855e6df9f1e8c5d7b6fc85ede"><code>c392b20</code></a> 0.7</li> <li><a href="https://github.com/testdouble/standard/commit/9ae9dc4cb3e2bf0f67dc37a6d679bfd52b8b3d4d"><code>9ae9dc4</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/testdouble/standard/issues/204">#204</a> from testdouble/update-rubocop-fix-bug</li> <li><a href="https://github.com/testdouble/standard/commit/32490540743bc62b64113bb4a763f9ec7ea0690a"><code>3249054</code></a> update rubocop to 0.92 to fix infinite loop</li> <li>See full diff in <a href="https://github.com/testdouble/standard/compare/v0.6.2...v0.7">compare view</a></li> </ul> </details> <br />

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 it includes an out-of-range update to a development dependency.

<details> <summary>Dependabot commands and options</summary> <br />

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:

• 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)

</details>

I installed heya in a new project but ran rails g heya:campaign before rails g heya:install (so a campaign was created first). Subsequently running the install generator produced the following error:

λ  app heya ✓ rails g heya:install
/Users/josh/Code/hook-relay/app/app/campaigns/signup_onboarding_campaign.rb:1:in `<main>': uninitialized constant ApplicationCampaign
Did you mean?  ApplicationNotification (NameError)
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/bootsnap-1.4.8/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `require'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/bootsnap-1.4.8/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:23:in `block in require_with_bootsnap_lfi'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/bootsnap-1.4.8/lib/bootsnap/load_path_cache/loaded_features_index.rb:92:in `register'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/bootsnap-1.4.8/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:22:in `require_with_bootsnap_lfi'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/bootsnap-1.4.8/lib/bootsnap/load_path_cache/core_ext/kernel_require.rb:31:in `require'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/zeitwerk-2.4.0/lib/zeitwerk/kernel.rb:34:in `require'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/dependencies/zeitwerk_integration.rb:49:in `require_dependency'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/heya-0.3.0/lib/heya/engine.rb:15:in `block (2 levels) in <class:Engine>'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/heya-0.3.0/lib/heya/engine.rb:14:in `each'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/heya-0.3.0/lib/heya/engine.rb:14:in `block in <class:Engine>'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/callbacks.rb:428:in `instance_exec'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/callbacks.rb:428:in `block in make_lambda'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/callbacks.rb:200:in `block (2 levels) in halting'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/callbacks.rb:605:in `block (2 levels) in default_terminator'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/callbacks.rb:604:in `catch'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/callbacks.rb:604:in `block in default_terminator'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/callbacks.rb:201:in `block in halting'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/callbacks.rb:513:in `block in invoke_before'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/callbacks.rb:513:in `each'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/callbacks.rb:513:in `invoke_before'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/callbacks.rb:134:in `run_callbacks'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/reloader.rb:88:in `prepare!'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/reloader.rb:47:in `block in <class:Reloader>'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/callbacks.rb:428:in `instance_exec'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/callbacks.rb:428:in `block in make_lambda'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/callbacks.rb:273:in `block in simple'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/callbacks.rb:517:in `block in invoke_after'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/callbacks.rb:517:in `each'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/callbacks.rb:517:in `invoke_after'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/callbacks.rb:136:in `run_callbacks'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/execution_wrapper.rb:111:in `run!'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/reloader.rb:114:in `run!'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/reloader.rb:53:in `block (2 levels) in reload!'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/reloader.rb:52:in `tap'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/reloader.rb:52:in `block in reload!'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/execution_wrapper.rb:88:in `wrap'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/activesupport-6.0.3.3/lib/active_support/reloader.rb:51:in `reload!'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/spring-2.1.1/lib/spring/application.rb:168:in `serve'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/spring-2.1.1/lib/spring/application.rb:145:in `block in run'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/spring-2.1.1/lib/spring/application.rb:139:in `loop'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/spring-2.1.1/lib/spring/application.rb:139:in `run'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/gems/2.7.0/gems/spring-2.1.1/lib/spring/application/boot.rb:19:in `<top (required)>'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in `require'
	from /Users/josh/.asdf/installs/ruby/2.7.1/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:72:in `require'
	from -e:1:in `<main>'

Bumps honeybadger-js from 2.3.0-beta.1 to 2.3.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/honeybadger-io/honeybadger-js/blob/master/CHANGELOG.md">honeybadger-js's changelog</a>.</em></p> <blockquote> <h2>[2.3.0] - 2020-09-24</h2> <h3>Added</h3> <ul> <li>Perform breadcrumbs instrumentation on first <code>Honeybadger.configure</code> call (<a href="https://github-redirect.dependabot.com/honeybadger-io/honeybadger-js/issues/406">#406</a>)</li> <li>Add config option to disable auto breadcrumbs by type</li> </ul> <h3>Fixed</h3> <ul> <li>Add <code>referrer</code> and <code>userAgent</code> to notice object to support filtering (<a href="https://github-redirect.dependabot.com/honeybadger-io/honeybadger-js/issues/418">#418</a>)</li> </ul> <h2>[2.2.2] - 2020-05-22</h2> <h3>Fixed</h3> <ul> <li>Replace use of <code>for...in</code> over <code>Array</code> w/ <code>Array.prototype.some()</code> (<a href="https://github-redirect.dependabot.com/honeybadger-io/honeybadger-js/issues/340">#340</a>)</li> <li>Add TypeScript definition for <code>Honeybadger.addBreadcrumb</code></li> </ul> <h2>[2.2.1] - 2020-04-12</h2> <h3>Fixed</h3> <ul> <li>Fix an issue where breadcrumbs metadata could incorrectly be marked recursive when sanitizing.</li> <li>(security) Send event target value for buttons and submit elements only in click events. Fixes an issue where input values could be leaked in breadcrumbs metadata.</li> </ul> <h2>[2.2.0] - 2020-03-16</h2> <h3>Added</h3> <ul> <li>Add <code>afterNotify</code> callback, similar to <code>beforeNotify</code>. PR <a href="https://github-redirect.dependabot.com/honeybadger-io/honeybadger-js/issues/314">#314</a> by <a href="https://github.com/anymaniax">@anymaniax</a></li> </ul> <h3>Changed</h3> <ul> <li><a href="https://docs.honeybadger.io/lib/javascript/guides/breadcrumbs.html">Breadcrumbs</a> are now enabled by default.</li> </ul> <h3>Fixed</h3> <ul> <li>Fix TypeScript definition for Config interface to include onunhandledrejection as boolean. <a href="https://github.com/tojofo">@tojofo</a></li> </ul> <h2>[2.1.3] - 2020-02-17</h2> <h3>Fixed</h3> <ul> <li>Fix TypeScript definition for <code>resetContext</code>. <a href="https://github.com/atshakil">@atshakil</a> (<a href="https://github-redirect.dependabot.com/honeybadger-io/honeybadger-js/issues/310">#310</a>)</li> </ul> <h2>[2.1.2] - 2020-02-13</h2> <h3>Fixed</h3> <ul> <li>Fix <code>n.match</code> is not a function error w/ ignorePatterns.</li> </ul> <h2>[2.1.1] - 2020-02-03</h2> <h3>Fixed</h3> <ul> <li>Add <code>breadcrumbsEnabled</code> to TypeScript definition (<a href="https://github-redirect.dependabot.com/honeybadger-io/honeybadger-js/issues/305">#305</a>)</li> </ul> <h2>[2.1.0] - 2020-01-28</h2> <h3>Added</h3> <ul> <li>Add Breadcrumbs (<a href="https://github-redirect.dependabot.com/honeybadger-io/honeybadger-js/issues/210">#210</a>). See <a href="https://docs.honeybadger.io/lib/javascript/guides/breadcrumbs.html">the docs</a> for more info.</li> </ul> <h3>Fixed</h3> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/honeybadger-io/honeybadger-js/commit/3ecd3bdf55b6a7e053590f34e2dd2559e3abebf8"><code>3ecd3bd</code></a> 2.3.0</li> <li><a href="https://github.com/honeybadger-io/honeybadger-js/commit/e7a0dbf1e206fa38117ca86178fbcceaf6d56fb2"><code>e7a0dbf</code></a> Prep CHANGELOG.md for release</li> <li><a href="https://github.com/honeybadger-io/honeybadger-js/commit/89a0da8dbb56a018120801c9f8f2560e79e23104"><code>89a0da8</code></a> Bump puppeteer from 5.3.0 to 5.3.1</li> <li><a href="https://github.com/honeybadger-io/honeybadger-js/commit/b035032b4b6e43ade36196bcc651898e1f281b2f"><code>b035032</code></a> Bump puppeteer from 5.2.1 to 5.3.0</li> <li><a href="https://github.com/honeybadger-io/honeybadger-js/commit/72acfba5548fc9ac5457b7761dbe3fa3c2df9bd5"><code>72acfba</code></a> Bump karma from 5.1.1 to 5.2.2</li> <li><a href="https://github.com/honeybadger-io/honeybadger-js/commit/8d90aff1123a48b1721dfabd5cf61b27a38f1850"><code>8d90aff</code></a> Bump whatwg-fetch from 3.4.0 to 3.4.1</li> <li><a href="https://github.com/honeybadger-io/honeybadger-js/commit/a41aaec4845884f65c02c37d6b1e45b8652383a5"><code>a41aaec</code></a> Bump eslint from 7.6.0 to 7.8.1</li> <li><a href="https://github.com/honeybadger-io/honeybadger-js/commit/5616afb057bcab76f933ab5c9970f077028176bf"><code>5616afb</code></a> Bump prettier from 2.0.5 to 2.1.1</li> <li><a href="https://github.com/honeybadger-io/honeybadger-js/commit/529ba3511849570fb66eea1a6d8cc7e5c269018b"><code>529ba35</code></a> Bump @babel/core from 7.10.5 to 7.11.4</li> <li><a href="https://github.com/honeybadger-io/honeybadger-js/commit/aa00217ba45d1ca74be14458fbc8ee090a0e2458"><code>aa00217</code></a> Update CHANGELOG.md</li> <li>See full diff in <a href="https://github.com/honeybadger-io/honeybadger-js/compare/v2.3.0-beta.1...v2.3.0">compare view</a></li> </ul> </details> <br />

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 it includes a non-semver update to a production dependency.

<details> <summary>Dependabot commands and options</summary> <br />

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 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 the .dependabot/config.yml file in this repo:

• Update frequency
• 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)

</details>

Bumps honeybadger-js from 2.3.0-beta.0 to 2.3.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/honeybadger-io/honeybadger-js/blob/master/CHANGELOG.md">honeybadger-js's changelog</a>.</em></p> <blockquote> <h2>[2.3.0] - 2020-09-24</h2> <h3>Added</h3> <ul> <li>Perform breadcrumbs instrumentation on first <code>Honeybadger.configure</code> call (<a href="https://github-redirect.dependabot.com/honeybadger-io/honeybadger-js/issues/406">#406</a>)</li> <li>Add config option to disable auto breadcrumbs by type</li> </ul> <h3>Fixed</h3> <ul> <li>Add <code>referrer</code> and <code>userAgent</code> to notice object to support filtering (<a href="https://github-redirect.dependabot.com/honeybadger-io/honeybadger-js/issues/418">#418</a>)</li> </ul> <h2>[2.2.2] - 2020-05-22</h2> <h3>Fixed</h3> <ul> <li>Replace use of <code>for...in</code> over <code>Array</code> w/ <code>Array.prototype.some()</code> (<a href="https://github-redirect.dependabot.com/honeybadger-io/honeybadger-js/issues/340">#340</a>)</li> <li>Add TypeScript definition for <code>Honeybadger.addBreadcrumb</code></li> </ul> <h2>[2.2.1] - 2020-04-12</h2> <h3>Fixed</h3> <ul> <li>Fix an issue where breadcrumbs metadata could incorrectly be marked recursive when sanitizing.</li> <li>(security) Send event target value for buttons and submit elements only in click events. Fixes an issue where input values could be leaked in breadcrumbs metadata.</li> </ul> <h2>[2.2.0] - 2020-03-16</h2> <h3>Added</h3> <ul> <li>Add <code>afterNotify</code> callback, similar to <code>beforeNotify</code>. PR <a href="https://github-redirect.dependabot.com/honeybadger-io/honeybadger-js/issues/314">#314</a> by <a href="https://github.com/anymaniax">@anymaniax</a></li> </ul> <h3>Changed</h3> <ul> <li><a href="https://docs.honeybadger.io/lib/javascript/guides/breadcrumbs.html">Breadcrumbs</a> are now enabled by default.</li> </ul> <h3>Fixed</h3> <ul> <li>Fix TypeScript definition for Config interface to include onunhandledrejection as boolean. <a href="https://github.com/tojofo">@tojofo</a></li> </ul> <h2>[2.1.3] - 2020-02-17</h2> <h3>Fixed</h3> <ul> <li>Fix TypeScript definition for <code>resetContext</code>. <a href="https://github.com/atshakil">@atshakil</a> (<a href="https://github-redirect.dependabot.com/honeybadger-io/honeybadger-js/issues/310">#310</a>)</li> </ul> <h2>[2.1.2] - 2020-02-13</h2> <h3>Fixed</h3> <ul> <li>Fix <code>n.match</code> is not a function error w/ ignorePatterns.</li> </ul> <h2>[2.1.1] - 2020-02-03</h2> <h3>Fixed</h3> <ul> <li>Add <code>breadcrumbsEnabled</code> to TypeScript definition (<a href="https://github-redirect.dependabot.com/honeybadger-io/honeybadger-js/issues/305">#305</a>)</li> </ul> <h2>[2.1.0] - 2020-01-28</h2> <h3>Added</h3> <ul> <li>Add Breadcrumbs (<a href="https://github-redirect.dependabot.com/honeybadger-io/honeybadger-js/issues/210">#210</a>). See <a href="https://docs.honeybadger.io/lib/javascript/guides/breadcrumbs.html">the docs</a> for more info.</li> </ul> <h3>Fixed</h3> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/honeybadger-io/honeybadger-js/commit/3ecd3bdf55b6a7e053590f34e2dd2559e3abebf8"><code>3ecd3bd</code></a> 2.3.0</li> <li><a href="https://github.com/honeybadger-io/honeybadger-js/commit/e7a0dbf1e206fa38117ca86178fbcceaf6d56fb2"><code>e7a0dbf</code></a> Prep CHANGELOG.md for release</li> <li><a href="https://github.com/honeybadger-io/honeybadger-js/commit/89a0da8dbb56a018120801c9f8f2560e79e23104"><code>89a0da8</code></a> Bump puppeteer from 5.3.0 to 5.3.1</li> <li><a href="https://github.com/honeybadger-io/honeybadger-js/commit/b035032b4b6e43ade36196bcc651898e1f281b2f"><code>b035032</code></a> Bump puppeteer from 5.2.1 to 5.3.0</li> <li><a href="https://github.com/honeybadger-io/honeybadger-js/commit/72acfba5548fc9ac5457b7761dbe3fa3c2df9bd5"><code>72acfba</code></a> Bump karma from 5.1.1 to 5.2.2</li> <li><a href="https://github.com/honeybadger-io/honeybadger-js/commit/8d90aff1123a48b1721dfabd5cf61b27a38f1850"><code>8d90aff</code></a> Bump whatwg-fetch from 3.4.0 to 3.4.1</li> <li><a href="https://github.com/honeybadger-io/honeybadger-js/commit/a41aaec4845884f65c02c37d6b1e45b8652383a5"><code>a41aaec</code></a> Bump eslint from 7.6.0 to 7.8.1</li> <li><a href="https://github.com/honeybadger-io/honeybadger-js/commit/5616afb057bcab76f933ab5c9970f077028176bf"><code>5616afb</code></a> Bump prettier from 2.0.5 to 2.1.1</li> <li><a href="https://github.com/honeybadger-io/honeybadger-js/commit/529ba3511849570fb66eea1a6d8cc7e5c269018b"><code>529ba35</code></a> Bump @babel/core from 7.10.5 to 7.11.4</li> <li><a href="https://github.com/honeybadger-io/honeybadger-js/commit/aa00217ba45d1ca74be14458fbc8ee090a0e2458"><code>aa00217</code></a> Update CHANGELOG.md</li> <li>Additional commits viewable in <a href="https://github.com/honeybadger-io/honeybadger-js/compare/v2.3.0-beta.0...v2.3.0">compare view</a></li> </ul> </details> <br />

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 it includes a non-semver update to a production dependency.

<details> <summary>Dependabot commands and options</summary> <br />

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 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 the .dependabot/config.yml file in this repo:

• Update frequency
• 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)

</details>

Is something missing to publish the new release with Fingerprint option?

Hi @brunozrk, I've released the changes in 0.15.0. Awesome PR, thank you for contributing!

Changelog: https://github.com/honeybadger-io/honeybadger-elixir/blob/master/CHANGELOG.md

@odarriba I think what you want is to be able to override the "component" (also sometimes called "controller") via Honeybadger.notify/2 and/or Honeybadger.context/1. I'm looking and there is not a way to do this via context, but I think this would work:

Honeybadger.notify(exception, %{component: "custom"})

Is that an option, or do you need to be able to set a custom component for the automatic logging integration?

Bumps standard from 0.4.7 to 0.6.0. <details> <summary>Changelog</summary> <p><em>Sourced from <a href="https://github.com/testdouble/standard/blob/master/CHANGELOG.md">standard's changelog</a>.</em></p> <blockquote> <h2>0.6.0</h2> <ul> <li>Update Rubocop from <a href="https://github.com/rubocop-hq/rubocop/releases/tag/v0.89.1">0.89.1</a> to <a href="https://github.com/rubocop-hq/rubocop/releases/tag/v0.90.0">0.90</a>, enabling: <ul> <li><a href="https://github-redirect.dependabot.com/rubocop-hq/rubocop/pull/8563"><code>Style/KeywordParametersOrder</code></a></li> <li><a href="https://github-redirect.dependabot.com/rubocop-hq/rubocop/pull/8474"><code>Lint/DuplicateRequire</code></a></li> <li><a href="https://github-redirect.dependabot.com/rubocop-hq/rubocop/pull/8549"><code>Lint/TrailingCommaInAttributeDeclaration</code></a></li> </ul> </li> <li>Update <a href="https://github-redirect.dependabot.com/testdouble/standard/pull/196"><code>Style/Alias</code> to prefer <code>alias_method</code></a></li> <li>Update rubocop-performance from 1.7.1 to 1.8.0: <ul> <li>Plan to enable <a href="https://github-redirect.dependabot.com/rubocop-hq/rubocop-performance/pull/137"><code>Performance/Sum</code></a> in the future, but there is currently a bug in the implementation</li> </ul> </li> <li>Add <code>ruby-2.3.yml</code> to add support for 2.3.</li> </ul> <h2>0.5.2</h2> <ul> <li>Turned off <code>Lint/MissingSuper</code>, because it effectively bans a common idiom in Sorbet (<a href="https://github-redirect.dependabot.com/testdouble/standard/issues/195">#195</a>) and might be a bit too heavy-handed/opinionated for cases where a class is designed intentionally to not run its parent's initializer (like abstract superclasses more generally)</li> </ul> <h2>0.5.1</h2> <ul> <li>Enabled <code>Style/MultilineWhenThen</code></li> </ul> <h2>0.5.0</h2> <ul> <li>Update Rubocop from <a href="https://github.com/rubocop-hq/rubocop/blob/master/CHANGELOG.md#0850-2020-06-01">0.85.0</a> to <a href="https://github.com/rubocop-hq/rubocop/releases/tag/v0.89.1">0.89.1</a>, enabling: <ul> <li><code>Lint/BinaryOperatorWithIdenticalOperands</code></li> <li><code>Lint/DuplicateElsifCondition</code></li> <li><code>Lint/DuplicateRescueException</code></li> <li><code>Lint/FloatComparison</code></li> <li><code>Lint/MissingSuper</code></li> <li><code>Lint/OutOfRangeRegexpRef</code></li> <li><code>Lint/RedundantRequireStatement</code></li> <li><code>Lint/RedundantSplatExpansion</code></li> <li><code>Lint/SafeNavigationWithEmpty</code></li> <li><code>Lint/SelfAssignment</code></li> <li><code>Lint/TopLevelReturnWithArgument</code></li> <li><code>Style/GlobalStdStream</code></li> <li><code>Style/RedundantAssignment</code></li> <li><code>Style/RedundantFetchBlock</code></li> <li><code>Style/RedundantFileExtensionInRequire</code></li> </ul> </li> <li>Update rubocop-performance from 1.6.0 to 1.7.1, enabling:</li> </ul> <!-- raw HTML omitted --> </blockquote> </details> <details> <summary>Commits</summary> <ul> <li><a href="https://github.com/testdouble/standard/commit/c821c121e2dafde7ee6c041f204289effb4be77b"><code>c821c12</code></a> 0.6.0</li> <li><a href="https://github.com/testdouble/standard/commit/eea9e7d115c1700139bde5ea9657cdfeffe7609d"><code>eea9e7d</code></a> Document release steps</li> <li><a href="https://github.com/testdouble/standard/commit/c7b92cfae386b6a6dcdb2d91f790c20761e1d0d6"><code>c7b92cf</code></a> unversion changelog</li> <li><a href="https://github.com/testdouble/standard/commit/2e6f39b8369bbc9683eac06e03b3db5ef2e858c1"><code>2e6f39b</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/testdouble/standard/issues/198">#198</a> from jmkoni/update-rubocop-to-0.9</li> <li><a href="https://github.com/testdouble/standard/commit/067575f9735b0313b4bb84dbffbd642cc1187075"><code>067575f</code></a> Upgraded rubocop-performance to 1.8.0</li> <li><a href="https://github.com/testdouble/standard/commit/817039ddee571e207ff5a01aec25299cbb2bedd5"><code>817039d</code></a> Update rubocop to 0.90</li> <li><a href="https://github.com/testdouble/standard/commit/c8fba579479e70c824628192a37a17cce443a1f3"><code>c8fba57</code></a> Merge pull request <a href="https://github-redirect.dependabot.com/testdouble/standard/issues/196">#196</a> from jmkoni/Issue-185_prefer-alias_method</li> <li><a href="https://github.com/testdouble/standard/commit/898163055fd3c16e4438c89a2100fe2e4fd02658"><code>8981630</code></a> Updates Style/Alias to prefer alias_method</li> <li><a href="https://github.com/testdouble/standard/commit/aba3fa4b4f3b727a5e8050ad733051ef9912d91d"><code>aba3fa4</code></a> 0.5.2</li> <li><a href="https://github.com/testdouble/standard/commit/ae65e06cf3b761d6bf14c721e37b020a3aadc864"><code>ae65e06</code></a> 0.5.1</li> <li>Additional commits viewable in <a href="https://github.com/testdouble/standard/compare/v0.4.7...v0.6.0">compare view</a></li> </ul> </details> <br />

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 it includes an out-of-range update to a development dependency.

<details> <summary>Dependabot commands and options</summary> <br />

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:

• 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)

</details>

I guess this may be a bit more involved than updating tested versions. @sixlive can you take a look when you get the chance?

We had a customer ask if we support Laravel 8 yet. I'm thinking this might tell me the answer. :)

Here's a sample test that the customer sent:

self.app.test_request_context(path='/test', base_url='http://server:1234/path', method='POST', data={'request': json.dumps({'thing': {'password': 'xxx'}})}):`

For future reference, this was released in 0.3.0.

@bompus yes, I believe it can! Would you like to submit a PR?

@sobrinho would you mind updating to 0.0.12-beta.1 and tell me if you see the same error? I fixed a different TypeScript problem in that version, and I'm wondering if this is related.

What are the steps to reproduce this issue?

1. Setup a simple Vue app with typescript
2. Try to add honeybadger-vue to vue app
3. Try & run vue-cli-service serve ( npm run serve )

What happens?

Unfound Type: Honeybadger

What were you expecting to happen?

a successful build

Any other comments?

honestly just type Honeybadger = any at the top of the file would go a long way

What versions are you using?

.0.0.11

This was fixed in https://github.com/honeybadger-io/honeybadger-vue/commit/13040274ab1e921d2253099441ddb785e195a7ff and is currently released in 0.0.12-beta.1.

Ignoring the error in the Honeybadger UI doesn't prevent the error from consuming your quota correct?

Correct, they do not consume quota!

In any case, I think this is a feature we want to eventually add, so I'll leave this open to track it.

A customer mentioned that the following params are not being filtered:

My flask app receives some sensitive information in request's form data:

{"thing": {"password": "xxx"}}

@demsullivan could we support this?

This allows the referrer and userAgent strings to be filtered in beforeNotify handlers:

https://docs.honeybadger.io/lib/javascript/guides/filtering-sensitive-data.html

@rabidpraxis fixed, thanks!

Ah, good catch. Yes it should. :)

This allows the referrer and userAgent strings to be filtered in beforeNotify handlers:

https://docs.honeybadger.io/lib/javascript/guides/filtering-sensitive-data.html

Currently the Honeybadger documentation recommends directly reporting CSP error to the https://api.honeybadger.io/v1/browser/csp endpoint. In our application we currently have our own controller in place that implements some additional logging for CSP errors and then submits the CSP error via a normal Honeybadger.notify call.

It would be nice to have the ability to submit CSP errors via the Honeybadger ruby gem for such cases rather than having to either call the https://api.honeybadger.io/v1/browser/csp endpoint manually of issuing calls to Honeybadger.notify which will show up differently on the UI.

Current documentation: https://docs.honeybadger.io/guides/errors.html#content-security-policy-reports

For the most part our CSP endpoint just converts a CSP report into a Honeybadger error (similar to what Honeybadger.notify sends), so in this case I think it's better to just use Honeybadger.notify like you are already doing. You could make the class_name of the notification "CSP Report" (or something like that). If you need to add additional data to the report, you could use the context option.

Thanks for the suggestion @Jcambass!

@rabidpraxis oh OK, so our docs are actually valid? Is there a method you prefer?

@kennethito you can ignore the error in the Honeybadger UI and we'll stop alerting you about it, but I don't think we have a way to completely ignore the error in the client, which would be better (since then it wouldn't be sent to our servers at all). @sorentwo we don't currently have a solution for this that I am missing, do we?

Are these comments accurate? I probably added them, but based on your PR description, I'm doubting myself. :)