Skip to content

chore(deps): bump debug and docusaurus in /website - #33

Open
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/website/debug-and-docusaurus-4.3.4
Open

chore(deps): bump debug and docusaurus in /website#33
dependabot[bot] wants to merge 1 commit into
masterfrom
dependabot/npm_and_yarn/website/debug-and-docusaurus-4.3.4

Conversation

@dependabot

@dependabotdependabotBot commented on behalf of githubDec 9, 2022

Copy link
Copy Markdown
Contributor

Bumps debug to 4.3.4 and updates ancestor dependency docusaurus. These dependencies need to be updated together.

Updates debug from 0.7.4 to 4.3.4

Release notes

Sourced from debug's releases.

4.3.4

What's Changed

New Contributors

Full Changelog: debug-js/debug@4.3.3...4.3.4

4.3.3

Patch Release 4.3.3

This is a documentation-only release. Further, the repository was transferred. Please see notes below.

Thank you to @​taylor1791 and @​kristofkalocsai for their contributions.

Repository Migration Information

I've formatted this as a FAQ, please feel free to open an issue for any additional question and I'll add the response here.

Q: What impact will this have on me?

In most cases, you shouldn't notice any change.

The only exception I can think of is if you pull code directly from https://github.com/visionmedia/debug, e.g. via a "debug": "visionmedia/debug"-type version entry in your package.json - in which case, you should still be fine due to the automatic redirection Github sets up, but you should also update any references as soon as possible.

Q: What are the security implications of this change?

If you pull code directly from the old URL, you should update the URL to https://github.com/debug-js/debug as soon as possible. The old organization has many approved owners and thus a new repository could (in theory) be created at the old URL, circumventing Github's automatic redirect that is in place now and serving malicious code. I (@​qix-) also wouldn't have access to that repository, so while I don't think it would happen, it's still something to consider.

Even in such a case, however, the officially released package on npm (debug) would not be affected. That package is still very much under control (even more than it used to be).

Q: What should I do if I encounter an issue related to the migration?

Search the issues first to see if someone has already reported it, and then open a new issue if someone has not.

Q: Why was this done as a 'patch' release? Isn't this breaking?

No, it shouldn't be breaking. The package on npm shouldn't be affected (aside from this patch release) and any references to the old repository should automatically redirect.

Thus, according to all of the "APIs" (loosely put) involved, nothing should have broken.

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by qix, a new releaser for debug since your current version.


Updates docusaurus from 1.9.0 to 1.14.7

Release notes

Sourced from docusaurus's releases.

v1.14.7

[1.14.7] - 2021-03-09

🏠 Internal

Committers: 1

v1.14.6

[1.14.6] - 2020-08-05

🐛 Bug Fix

  • docusaurus-1.x

📝 Documentation

Committers: 1

v1.14.5

[1.14.5] - 2020-08-01

🚀 New Feature

  • docusaurus-1.x
    • #2955 feat(v1): add deletedDocs config to fix unwanted versioning fallback (@​aldeed)
    • #3124 feat(v1): add 'slugPreprocessor' config option to allow users customize the hash links (@​Simek)

📝 Documentation

Committers: 6

... (truncated)

Changelog

Sourced from docusaurus's changelog.

[1.14.7] - 2021-03-09

🏠 Internal

Committers: 1

[1.14.6] - 2020-08-05

🐛 Bug Fix

  • docusaurus-1.x

📝 Documentation

Committers: 1

[1.14.5] - 2020-08-01

🚀 New Feature

  • docusaurus-1.x
    • #2955 feat(v1): add deletedDocs config to fix unwanted versioning fallback (@​aldeed)
    • #3124 feat(v1): add 'slugPreprocessor' config option to allow users customize the hash links (@​Simek)

📝 Documentation

Committers: 6

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by slorber, a new releaser for docusaurus since your current version.


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

You can disable automated security fix PRs for this repo from the Security Alerts page.

@dependabot
chore(deps): bump debug and docusaurus in /website
e065274
Bumps [debug](https://github.com/debug-js/debug) to 4.3.4 and updates ancestor dependency [docusaurus](https://github.com/facebook/docusaurus/tree/HEAD/packages/docusaurus-1.x). These dependencies need to be updated together.
Updates `debug` from 0.7.4 to 4.3.4
- [Release notes](https://github.com/debug-js/debug/releases)
- [Commits](debug-js/debug@0.7.4...4.3.4)
Updates `docusaurus` from 1.9.0 to 1.14.7
- [Release notes](https://github.com/facebook/docusaurus/releases)
- [Changelog](https://github.com/facebook/docusaurus/blob/v1.14.7/CHANGELOG.md)
- [Commits](https://github.com/facebook/docusaurus/commits/v1.14.7/packages/docusaurus-1.x)
---
updated-dependencies:
- dependency-name: debug
dependency-type: indirect
- dependency-name: docusaurus
dependency-type: direct:development
...
Signed-off-by: dependabot[bot] <support@github.com>
@dependabotdependabotBot added the dependencies Pull requests that update a dependency file label Dec 9, 2022
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

dependenciesPull requests that update a dependency file

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

0 participants