BranchMetrics / web-branch-deep-linking-attribution

The Branch Web SDK for deep linking and attribution. Once initialized, the Branch Web SDK allows you to create and share links with a banner (web only), over SMS, or your own methods by generating deep links. It also offers event tracking, access to referrals, and management of credits.
https://help.branch.io/developers-hub/docs/web-sdk-overview
MIT License
287 stars 100 forks source link

Bump jsdoc from 3.2.2 to 4.0.2 #872

Closed dependabot[bot] closed 8 months ago

dependabot[bot] commented 1 year ago

Bumps jsdoc from 3.2.2 to 4.0.2.

Release notes

Sourced from jsdoc's releases.

JSDoc 3.5.5

This version of JSDoc fixes an incompatibility with Node.js 8.5.0.

JSDoc 3.5.4

This version of JSDoc includes a variety of bug fixes.

For a complete list of changes, see the changelog on GitHub.

JSDoc 3.5.3

This version of JSDoc includes a variety of bug fixes, including the following:

  • Non-JSDoc comments (comments that do not begin with /**) are now ignored.
  • JSDoc no longer crashes when it parses a class property with no value assigned to it.
  • When there are JSDoc comments at the end of a source file that has a 'use strict'; directive, the comments are no longer ignored.
  • Namepaths that contain an @ sign (for example, module:@prefix/my-module~myCallback) are now parsed correctly.

For a complete list of changes, see the changelog on GitHub.

JSDoc 3.5.2

This version of JSDoc fixes an issue with using the @hideconstructor tag with the default template. It is also better at locating plugins and template resources.

For a complete list of changes, see the changelog on GitHub.

JSDoc 3.5.1

This version of JSDoc includes the following bug fixes:

  • Fixed an issue that prevented JSDoc from working on versions of Node.js prior to 5.10.0.
  • If the JSDoc configuration file does not have a file extension, JSDoc now assumes that the file is in JSON format.

JSDoc 3.5.0

This version of JSDoc includes the following major changes:

  • JSDoc now uses the Babylon JavaScript parser, which means that JSDoc can parse any JavaScript or JSX file that is supported by the Babel compiler.
  • You can now use a JavaScript file to configure JSDoc. See the documentation for details and examples.
  • Fixed multiple issues with documenting ES2015 classes and modules.
  • JSDoc now requires Node.js 4.2.0 or later.

For a complete list of changes, see the changelog on GitHub.

JSDoc 3.4.3

This version of JSDoc includes an updated LICENSE.md file. There are no other changes in this release.

JSDoc 3.4.2

This version of JSDoc fixes an issue with classes exported from an ES2015 module, along with other minor bugs.

For a complete list of changes, see the changelog on GitHub.

... (truncated)

Changelog

Sourced from jsdoc's changelog.

4.0.2 (February 2023)

Updates the Babel parser, and enables additional Babel plugins for ECMAScript proposals.

4.0.1 (February 2023)

If an inline link tag uses a pipe delimiter, and there are spaces around the pipe delimiter, then the HTML link no longer contains %20 at the end; also, the link text no longer contains extra spaces. For example, {@link https://example.com | link text} is now rendered as <a href="https://example.com/">link text</a> rather than <a href="https://example.com/%20"> link text</a>.

4.0.0 (November 2022)

3.6.11 (July 2022)

Updates dependency versions to make JSDoc compatible with Node.js 12.0.0 and later.

3.6.10 (January 2022)

Fixes an issue in JSDoc 3.6.9 that prevented JSDoc from being installed in some continuous integration (CI) environments.

3.6.9 (January 2022)

Fixes an issue in JSDoc 3.6.8 that prevented npm install jsdoc from working.

3.6.8 (January 2022)

Updates dependencies.

3.6.7 (May 2021)

Updates dependencies.

... (truncated)

Commits
  • 0b6193f 4.0.2
  • 9d88548 deps: update Babel; enable current Babel plugins in parser
  • c2dd210 4.0.1
  • 3d90c8a fix: in inline links, strip spaces around pipe character
  • 37fc8cd chore: tell Prettier not to format files
  • a5e4688 chore(deps): update deps
  • 0842185 4.0.0
  • b018408 chore!: replace taffydb package with @​jsdoc/salty
  • dc48aa6 3.6.11
  • cccfd3d chore(deps): resolve dependency vulnerability
  • Additional commits viewable in compare view


Dependabot compatibility score

You can trigger a rebase of this PR 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)
> **Note** > Automatic rebases have been disabled on this pull request as it has been open for over 30 days.
dependabot[bot] commented 8 months ago

OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version or @dependabot ignore this minor version. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore condition with the desired update_types to your config file.

If you change your mind, just re-open this PR and I'll resolve any conflicts on it.