-
Notifications
You must be signed in to change notification settings - Fork 429
fix(deps): update osv-scanner minor (major) #1732
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.
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
Open
renovate-bot
wants to merge
1
commit into
google:main
Choose a base branch
from
renovate-bot:renovate/major-osv-scanner-minor
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
fix(deps): update osv-scanner minor (major) #1732
renovate-bot
wants to merge
1
commit into
google:main
from
renovate-bot:renovate/major-osv-scanner-minor
+7
−1
Conversation
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
b8e484a
to
ce07963
Compare
ce07963
to
0b0aeeb
Compare
0b0aeeb
to
ad6ce44
Compare
b0b1564
to
c83006a
Compare
c83006a
to
1610f93
Compare
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
1610f93
to
ed8c599
Compare
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #1732 +/- ##
==========================================
+ Coverage 65.39% 65.41% +0.01%
==========================================
Files 167 167
Lines 16060 16060
==========================================
+ Hits 10503 10506 +3
+ Misses 4886 4884 -2
+ Partials 671 670 -1 ☔ View full report in Codecov by Sentry. 🚀 New features to boost your workflow:
|
36ad311
to
720f77a
Compare
4476e17
to
eca0440
Compare
dd850e8
to
f6985ac
Compare
67d4c80
to
86429cc
Compare
4e6daa9
to
e65ab29
Compare
e65ab29
to
dbe60c1
Compare
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.1-0.20250404203927-76690c660834
->v2.0.0-beta.1
v2.3.3
->v3.1.4
Release Notes
charmbracelet/lipgloss (github.com/charmbracelet/lipgloss)
v2.0.0-beta.1
Compare Source
Who said a beta release can’t be exciting?
We're thrilled to announce the first beta release of Lip Gloss v2! This release builds on top of the last alpha 2 release. Very little has changed since the last alpha, which means we’re getting closer to a proper
v2.0.0
.The only change here is that you can no longer use hexadecimal and integer format when defining colors. We found there were just to many gotchas and this way the API remains backwards compatible.
🌈 More on Lip Gloss v2
Just getting into Lip Gloss v2? Check out the full v2 release notes and upgrade guide.
💝 How’s it going?
Feel free to reach out, ask questions, give feedback, and let us know how it's going. We’d love to know what you think.
Part of Charm.
Charm热爱开源 • Charm loves open source • نحنُ نحب المصادر المفتوحة
v2.0.0-alpha.2
Compare Source
Do you think you can handle Lip Gloss v2?
We’re really excited for you to try Lip Gloss v2! Keep in mind that this is an early alpha release and things may change.
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
stdin
andstdout
when downsampling colors and querying for the background color. This was not always necessarily what you wanted. For example, if your application was writing tostderr
while redirectingstdout
to a file, the program would erroneously think output was not a TTY and strip colors. Lip Gloss v2 gives you control and intentionality 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
stdin
andstdout
, 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.
🐇 Quick upgrade
If you don't have time for changes and just want to upgrade to Lip Gloss v2 as fast as possible, do the following:
Use the
compat
packageThe
compat
package provides adaptive colors, complete colors, and complete adaptive colors:compat
works by looking atstdin
andstdout
on 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, use
lipgloss.Println
(andlipgloss.Printf
and so on) when printing your output:That’s it!
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
fmt
package:🌛 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
stdin
andstdout
.If that doesn’t matter to you and you're only working with
stdout
you skip this viacompat
above, though encourage you to explore this new functionality.With Bubble Tea
In Bubble Tea, request the background color, listen for a
BackgroundColorMsg
in 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.Color
lipgloss.Color()
now produces an idomaticcolor.Color
, whereas before colors were typelipgloss.TerminalColor
. Generally speaking, this is more of an implementation detail, but it’s worth noting the structural differences.Quotes are now optional in colors
There are also some quality-of-life niceties around color UX:
Changelog
Full Changelog: charmbracelet/lipgloss@v1.0.0...v2.0.0-alpha.2
🌈 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 • نحنُ نحب المصادر المفتوحة
owenrumney/go-sarif (github.com/owenrumney/go-sarif/v2)
v3.1.4
Compare Source
What's Changed
Full Changelog: owenrumney/go-sarif@v3.1.3...v3.1.4
v3.1.3
Compare Source
What's Changed
Full Changelog: owenrumney/go-sarif@v3.1.2...v3.1.3
v3.1.2
Compare Source
What's Changed
Full Changelog: owenrumney/go-sarif@v3.1.1...v3.1.2
v3.1.1
Compare Source
What's Changed
New Contributors
Full Changelog: owenrumney/go-sarif@v3.1.0...v3.1.1
v3.1.0
Compare Source
What's Changed
New Contributors
Full Changelog: owenrumney/go-sarif@v3.0.2...v3.1.0
v3.0.2
Compare Source
What's Changed
Full Changelog: owenrumney/go-sarif@v3.0.1...v3.0.2
v3.0.1
Compare Source
What's Changed
Full Changelog: owenrumney/go-sarif@v3.0.0...v3.0.1
v3.0.0
Compare Source
What's Changed
Full Changelog: owenrumney/go-sarif@v2.3.3...v3.0.0
Configuration
📅 Schedule: Branch creation - "before 6am on monday" 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.