Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Bump debug, grunt-contrib-watch, sails and mocha in /tests/dummy #73

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
Open

Bump debug, grunt-contrib-watch, sails and mocha in /tests/dummy #73

wants to merge 1 commit into from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Jan 11, 2023

Bumps debug to 4.3.4 and updates ancestor dependencies debug, grunt-contrib-watch, sails and mocha. 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
  • da66c86 4.3.4
  • 9b33412 replace deprecated String.prototype.substr() (#876)
  • c0805cc add section about configuring JS console to show debug messages (#866)
  • 043d3cd 4.3.3
  • 4079aae update license and more maintainership information
  • 19b36c0 update repository location + maintainership information
  • f851b00 adds README section regarding usage in child procs (#850)
  • d177f2b Remove accidental epizeuxis
  • e47f96d 4.3.2
  • 1e9d38c cache enabled status per-logger (#799)
  • Additional commits viewable in compare view
Maintainer changes

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


Updates grunt-contrib-watch from 0.5.3 to 1.1.0

Changelog

Sourced from grunt-contrib-watch's changelog.

v1.1.0: date: 2018-05-12 changes: - Update to [email protected], [email protected], [email protected] v1.0.1: date: 2018-04-20 changes: - Update to [email protected], lodash@4 v1.0.0: date: 2016-03-12 changes: - Updated tiny-lr, gaze, async and lodash dependencies. - Fix endless loop issue with atBegin/nospawn. - Expose hostname parameter of tiny-lr. - Support cwd.event to emit events relative to path. - Removed peerDependencies setting. v0.6.1: date: 2014-03-19 changes: - Fix for watch targets named "default". v0.6.0: date: 2014-03-11 changes: - Clear changed files after triggering live reload to ensure they're only triggered once. - 'cwd option now accepts separate settings for files and spawn.' - Fix to make interrupt work more than once. - Enable live reload over HTTPS. - Print newline after initial 'Waiting...'. - Remove deprecated grunt.util libs. - Add reload option to specify files other than Gruntfile files to reload. - Update to [email protected]. - Use a fork of tiny-lr (which has quiter operation, support for HTTPS and Windows path fixes). - Add livereloadOnError, which if set to false will not trigger live reload if there is an error.

Commits

Updates sails from 0.12.14 to 1.5.3

Release notes

Sourced from sails's releases.

v1.4.0

  • Support sameSite:none in cookie options (thanks @​pixnlove!)

v1.3.1

  • Updated the machine-as-action dependency to include a reminder about escaping strings with dynamic data when they're injected (Thanks @​dusterherz for letting us know about this)

v1.2.5

  • Added more info to the error message shown when an app fails to lift
  • Updated the sails-generate dependency

v1.2.4

  • Fix resourceful PubSub for the update blueprint action, resolving #6824 (thanks @​Tarrask!)
  • Re-enable afterDestroy lifecycle callback for the destroy blueprint action, fixing #5630
  • Update CSRF hook to fix an issue with disabling CSRF for routes defined using regular expression syntax, resolving #6838
  • Update session hook to fix an issue with double-prefixes, resolving #6541 (thanks @​travispwingo!)
  • Update minimist dependency to resolve potential vulnerabilities
  • Update various comments, error messages, and logs for clarity/consistency

v1.2.3

1.2.3

  • Update eslint dev depdendency to get rid of vulnerability warnings
  • Minor formatting/verbiage fixes

v1.2.2

• Update merge-defaults dependency to resolve potential vulnerabilities • Update sails-stringfile dependency to resolve potential vulnerabilities • Update sort-route-addresses dependency to resolve potential vulnerabilities

v1.2.1

  • Added sails migrate for quickly running auto-migrations by hand
  • The output of sails inspect no longer includes controller information
  • When loading user hooks, if sails.config.loadHooks is specified, skip hooks whose names aren't explicitly included
  • Increased time to display warning message in config/bootstrap.js from 5 seconds to 30 seconds
  • Switched to using updateOne in the "update" blueprint
  • Blueprint queries no longer include fetch: true by default, to avoid warnings from updateOne
  • Update error mesage in default serverError response to use flaverr
  • In lib/router/res.js, instead of always setting 'content-type' to 'application/json', only set it if res.get('content-type') is falsy
  • Update flaverr dependency
  • Update i18n-2 dependency to resolve deprecation warning
  • Update rc dependency to address potential vulnerabilities
  • Update machinepack-process dependency to address potential vulnerabilities
  • Update machinepack-redis dependency to address potential vulnerabilities

v0.9.13: 0.9.13

No release notes provided.

v0.9.12: 0.9.12

No release notes provided.

Changelog

Sourced from sails's changelog.

Sails Changelog

1.2.0

  • Added sails migrate for quickly running auto-migrations by hand
  • The output of sails inspect no longer includes controller information
  • When loading user hooks, if sails.config.loadHooks is specified, skip hooks whose names aren't explicitly included
  • Increased time to display warning message in config/bootstrap.js from 5 seconds to 30 seconds
  • Switched to using updateOne in the "update" blueprint
  • Blueprint queries no longer include fetch: true by default, to avoid warnings from updateOne
  • Update error mesage in default serverError response to use flaverr
  • In lib/router/res.js, instead of always setting 'content-type' to 'application/json', only set it if res.get('content-type') is falsy
  • Update flaverr dependency
  • Update i18n-2 dependency to resolve deprecation warning
  • Update rc dependency to address potential vulnerabilities
  • Update machinepack-process dependency to address potential vulnerabilities
  • Update machinepack-redis dependency to address potential vulnerabilities

1.1.0

As always, we owe a debt of gratitude to our contributors-- we mentioned you below next to the features/enhancements/fixes you contributed to. (Apologies to anyone we missed, there was a lot in this release! Let us know and we'll add you to the list.)

We especially want to thank those contributors who helped out with the documentation:

... (truncated)

Commits
Maintainer changes

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


Updates mocha from 2.4.5 to 10.2.0

Release notes

Sourced from mocha's releases.

v10.2.0

10.2.0 / 2022-12-11

🎉 Enhancements

  • #4945: API: add possibility to decorate ESM name before import (@​j0tunn)

🐛 Fixes

📖 Documentation

v10.1.0

10.1.0 / 2022-10-16

🎉 Enhancements

🔩 Other

v10.0.0

10.0.0 / 2022-05-01

💥 Breaking Changes

🔩 Other

... (truncated)

Changelog

Sourced from mocha's changelog.

10.2.0 / 2022-12-11

🎉 Enhancements

  • #4945: API: add possibility to decorate ESM name before import (@​j0tunn)

🐛 Fixes

📖 Documentation

10.1.0 / 2022-10-16

🎉 Enhancements

🔩 Other

10.0.0 / 2022-05-01

💥 Breaking Changes

🔩 Other

... (truncated)

Commits
Maintainer changes

This version was pushed to npm by juergba, a new releaser for mocha 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
Bump debug, grunt-contrib-watch, sails and mocha in /tests/dummy
981d0d6 
Bumps [debug](https://github.com/debug-js/debug) to 4.3.4 and updates ancestor dependencies [debug](https://github.com/debug-js/debug), [grunt-contrib-watch](https://github.com/gruntjs/grunt-contrib-watch), [sails](https://github.com/balderdashy/sails) and [mocha](https://github.com/mochajs/mocha). 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 `grunt-contrib-watch` from 0.5.3 to 1.1.0
- [Release notes](https://github.com/gruntjs/grunt-contrib-watch/releases)
- [Changelog](https://github.com/gruntjs/grunt-contrib-watch/blob/main/CHANGELOG)
- [Commits](gruntjs/grunt-contrib-watch@v0.5.3...v1.1.0)

Updates `sails` from 0.12.14 to 1.5.3
- [Release notes](https://github.com/balderdashy/sails/releases)
- [Changelog](https://github.com/balderdashy/sails/blob/master/CHANGELOG.md)
- [Commits](balderdashy/sails@v0.12.14...v1.5.3)

Updates `mocha` from 2.4.5 to 10.2.0
- [Release notes](https://github.com/mochajs/mocha/releases)
- [Changelog](https://github.com/mochajs/mocha/blob/master/CHANGELOG.md)
- [Commits](mochajs/mocha@v2.4.5...v10.2.0)

---
updated-dependencies:
- dependency-name: debug
  dependency-type: indirect
- dependency-name: grunt-contrib-watch
  dependency-type: direct:production
- dependency-name: sails
  dependency-type: direct:production
- dependency-name: mocha
  dependency-type: direct:development
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Jan 11, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
0 participants