Update dependency loglevel to v1.9.2 #34
Conversation
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=80&v=4){kind=small}
|
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/loglevel-1.x-lockfile
branch
from
8a3ca71 to
1a7e857
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/loglevel-1.x-lockfile
branch
2 times, most recently
from
2a8c96d to
7184691
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/loglevel-1.x-lockfile
branch
from
7184691 to
7502c91
Compare
renovate
bot
changed the title
|
Important Review skippedBot user detected. To trigger a single review, invoke the You can disable this status message by setting the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
renovate
bot
changed the title
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/loglevel-1.x-lockfile
branch
from
e4001ce to
7502c91
Compare
|
🚨 Potential security issues detected. Learn more about Socket for GitHub ↗︎ To accept the risk, merge this PR and you will not be notified again.
Next stepsWhat is a critical CVE?Contains a Critical Common Vulnerability and Exposure (CVE). Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Take a deeper look at the dependencyTake a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support [AT] socket [DOT] dev. Remove the packageIf you happen to install a dependency that Socket reports as Known Malware you should immediately remove it and select a different dependency. For other alert types, you may may wish to investigate alternative packages or consider if there are other ways to mitigate the specific risk posed by the dependency. Mark a package as acceptable riskTo ignore an alert, reply with a comment starting with
|
|
🚨 gitStream Monthly Automation Limit Reached 🚨 Your organization has exceeded the number of pull requests allowed for automation with gitStream. To continue automating your PR workflows and unlock additional features, please contact LinearB. |
This PR contains the following updates:
1.4.1->1.9.2Release Notes
pimterry/loglevel (loglevel)
v1.9.2Compare Source
v1.9.1Compare Source
v1.9.0Compare Source
v1.8.1Compare Source
v1.8.0Compare Source
v1.7.1Compare Source
v1.7.0Compare Source
v1.6.8Compare Source
v1.6.7Compare Source
v1.6.6Compare Source
Fix bugs in v1.6.5, which caused issues in node.js & IE < 9
v1.6.4Compare Source
Ensure package.json's 'main' is a fully qualified path, to fix webpack issues
v1.6.3Compare Source
Avoid TypeScript type conflicts with other global
logtypes (e.g. core-js)v1.6.2Compare Source
Include TypeScript type definitions in the package itself
v1.6.1Compare Source
Various small documentation & test updates
v1.6.0Compare Source
Add a name property to loggers and add log.getLoggers() (#114), and recommend unpkg as CDN instead of CDNJS.
v1.5.1Compare Source
Fix bug (#112) in level-persistence cookie fallback, which failed if it wasn't the first cookie present
v1.5.0Compare Source
Fix log.debug (#111) after V8 changes deprecating console.debug, check for 'window' upfront (#104), and add '.log' alias for '.debug' (#64)
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.