fix(deps): update vulnfeeds-go major (major)#4790
Open
renovate-bot wants to merge 1 commit intogoogle:masterfrom
Open
fix(deps): update vulnfeeds-go major (major)#4790renovate-bot wants to merge 1 commit intogoogle:masterfrom
renovate-bot wants to merge 1 commit intogoogle:masterfrom
Conversation
ℹ️ Artifact update noticeFile name: vulnfeeds/go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
ecaa3f3 to
534f6a3
Compare
edf1982 to
afca1f3
Compare
|
afca1f3 to
2c18a25
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
v1.1.0→v2.0.0v1.9.2→v2.3.3v2.4.0→v3.0.1Release Notes
charmbracelet/lipgloss (github.com/charmbracelet/lipgloss)
v2.0.0Compare Source
Do you think you can handle Lip Gloss v2?
We’re really excited for you to try Lip Gloss v2! Read on for new features and a guide to upgrading.
If you (or your LLM) just want the technical details, take a look at Upgrade Guide.
What’s new?
The big changes are that Styles are now deterministic (λipgloss!) and you can be much more intentional with your inputs and outputs. Why does this matter?
Playing nicely with others
v2 gives you precise control over I/O. One of the issues we saw with the Lip Gloss and Bubble Tea v1s is that they could fight over the same inputs and outputs, producing lock-ups. The v2s now operate in lockstep.
Querying the right inputs and outputs
In v1, Lip Gloss defaulted to looking at
stdinandstdoutwhen downsampling colors and querying for the background color. This was not always necessarily what you wanted. For example, if your application was writing tostderrwhile redirectingstdoutto a file, the program would erroneously think output was not a TTY and strip colors. Lip Gloss v2 gives you control over this.Going beyond localhost
Did you know TUIs and CLIs can be served over the network? For example, Wish allows you to serve Bubble Tea and Lip Gloss over SSH. In these cases, you need to work with the input and output of the connected clients as opposed to
stdinandstdout, which belong to the server. Lip Gloss v2 gives you flexibility around this in a more natural way.🧋 Using Lip Gloss with Bubble Tea?
Make sure you get all the latest v2s as they’ve been designed to work together.
# Collect the whole set. go get charm.land/bubbletea/v2 go get charm.land/bubbles/v2 go get charm.land/lipgloss/v2🐇 Quick upgrade
If you don't have time for changes and just want to upgrade to Lip Gloss v2 as fast as possible? Here’s a quick guide:
Use the
compatpackageThe
compatpackage provides adaptive colors, complete colors, and complete adaptive colors:compatworks by looking atstdinandstdouton a global basis. Want to change the inputs and outputs? Knock yourself out:Use the new Lip Gloss writer
If you’re using Bubble Tea with Lip Gloss you can skip this step. If you're using Lip Gloss in a standalone fashion, however, you'll want to use
lipgloss.Println(andlipgloss.Printfand so on) when printing your output:Why? Because
lipgloss.Printlnwill automatically downsample colors based on the environment.That’s it!
Yep, you’re done. All this said, we encourage you to read on to get the full benefit of v2.
👀 What’s changing?
Only a couple main things that are changing in Lip Gloss v2:
🪄 Downsampling colors with a writer
One of the best things about Lip Gloss is that it can automatically downsample colors to the best available profile, stripping colors (and ANSI) entirely when output is not a TTY.
If you're using Lip Gloss with Bubble Tea there's nothing to do here: downsampling is built into Bubble Tea v2. If you're not using Bubble Tea you now need to use a writer to downsample colors. Lip Gloss writers are a drop-in replacement for the usual functions found in the
fmtpackage:🌛 Background color detection and adaptive colors
Rendering different colors depending on whether the terminal has a light or dark background is an awesome power. Lip Gloss v2 gives you more control over this progress. This especially matters when input and output are not
stdinandstdout.If that doesn’t matter to you and you're only working with
stdoutyou skip this viacompatabove, though we encourage you to explore this new functionality.With Bubble Tea
In Bubble Tea, request the background color, listen for a
BackgroundColorMsgin your update, and respond accordingly.Standalone
If you're not using Bubble Tea you simply can perform the query manually:
🥕 Other stuff
Colors are now
color.Colorlipgloss.Color()now produces an idiomaticcolor.Color, whereas before colors were typelipgloss.TerminalColor. Generally speaking, this is more of an implementation detail, but it’s worth noting the structural differences.Changelog
New!
Fixed
Docs
Other stuff
🌈 Feedback
That's a wrap! Feel free to reach out, ask questions, and let us know how it's going. We'd love to know what you think.
Part of Charm.
Charm热爱开源 • Charm loves open source • نحنُ نحب المصادر المفتوحة
google/osv-scanner (github.com/google/osv-scanner)
v2.3.3Compare Source
Features:
--excludeflag to skip paths during scanning.pylockextractor.Misc:
v2.3.2Compare Source
This release includes performance improvements for local scanning, reducing memory usage and avoiding unnecessary advisory loading. It also fixes issues with MCP's get_vulnerability_details tool, git queries in
osv-scanner.json, and ignore entry tracking, along with documentation updates.Fixes:
Misc:
bun.lockas a supported lockfilev2.3.1Compare Source
Features:
packagedeprecationplugin via the new--experimental-flag-deprecated-packagesflag. The result is available in all output formats except SPDX.Fixes:
deps.devpackage names.Misc:
v2.3.0Compare Source
This release migrates to the new
osv.devandosv-schemaproto bindings for its internal data models (#2328). This is primarily an internal change and should not impact users.Features:
requirementsenhanceableextractor with transitive enricher.osduplicateannotators.Fixes:
--ignore-scriptsflag to npm lockfile generation.--all-packagesflag.v2.2.4Compare Source
Features:
osv-scanner experimental-mcp)osv-scalibrintegration, replacingbaseimagematchwith the base image enricher.Fixes:
.gitsuffix when checking if an advisory affects a git repository (fixes #2291).cmdloggerandosv-scalibrwhen set (fixes #2081).v2.2.3Compare Source
Features:
--experimental-pluginsflag additive by default, and introduce a new--experimental-no-default-pluginsflag.osv-scalibrto 0.3.4 for improved dependency extraction. See osv-scalibr changelog for additional information.Fixes:
input.Pathwas incorrectly constructed on Windows when using the-Lflag.v2.2.2Compare Source
Features:
osv-scanner-custom.jsonfiles asosv-scanner.jsoncustom lockfiles.Fixes:
v2.2.1Compare Source
Fixes
v2.2.0Compare Source
OSV-Scanner now supports all OSV-Scalibr features behind experimental flags (
--experimental-plugins, see details here)!Features:
Fixes:
API Changes:
v2.1.0Compare Source
Features:
--show-all-vulnsflag to show all.gems.lockedfiles used by Bundler.requirements.txtfiles.--sbomflag in favor of the existing-L/--lockfileflag for scanning SBOMs.Fixes:
:Pro,:LTS).v2.0.3Compare Source
Features:
osv-scanner ./scan-this-dir --format=vertical, by updating to cli/v3stabletag to container images for releases that follow semantic versioning.--experimental-extractorsand--experimental-disable-extractorsflags to allow for more granular control over which OSV-Scalibr dependency extractors are used.Fixes:
<dependency>elements.MatchVulnerabilitieswhen the API response is nil, particularly on timeout.Misc:
v2.0.2Compare Source
Fixes:
tooldirective (Go 1.24+) ingo.modfiles would fail. The scanner image has been updated to use a newer Go version.v2.0.1Compare Source
Features:
packages.configandpackages.lock.jsonfiles.Fixes:
Docs:
API Changes:
v2.0.0Compare Source
This release merges the improvements, features, and fixes from v2.0.0-rc1, v2.0.0-beta2, and v2.0.0-beta1.
Important: This release includes several breaking changes aimed at future-proofing OSV-Scanner. Please consult our comprehensive Migration Guide to ensure a smooth upgrade.
Features:
deps.dev.osv-scanner scan image <image-name>:<tag>osv-scanner scan --serve ...overrideremediation strategy.pom.xmland parent POM files.osv-scalibr:cabal.project.freeze,stack.yaml.lockdeps.jsonuv.locknode_modules, Python wheels, Java uber jars, Go binariesosv-scanner updatecommand for updating the local vulnerability database (formerly experimental).bun.locklockfiles.scan imagecommand.--serveusing the new--portflag.Breaking Changes:
--interactiveflag for interactive mode.--verbosity=verboseverbosity level.--licenseflag.reporterremoved; logging now usesslog, which can be overridden.lockfile(migrated toOSV-Scalibr).Improvements:
Fixes:
bom.xmlfilename.We encourage everyone to upgrade to OSV-Scanner v2.0.0 and experience these powerful new capabilities! As always, your feedback is invaluable, so please don't hesitate to share your thoughts and suggestions.
go-yaml/yaml (gopkg.in/yaml.v2)
v3.0.1Compare Source
v3.0.0Compare Source
Configuration
📅 Schedule: Branch creation - "before 6am on wednesday" in timezone Australia/Sydney, 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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.