fix(deps): update go deps to v2 (major) #628
Open
+10
−2
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.3v1.9.5->v2.2.4Release Notes
charmbracelet/lipgloss (github.com/charmbracelet/lipgloss)
v2.0.0-beta.3Compare Source
Padding, Schmadding
This new beta release reverts back to a major change when it comes to using regular spacing for padding. We found that using NBSP
\u00a0causes more problems than it solves. Things like simply copying the output from the terminal and then paste it back wouldn't work if NBSPs exist in a command.To solve this, we've added
style.PaddingChar(rune)andstyle.MarginChar(rune)to customize the characters used in padding and margins respectively.Changelog
New Features
d2233fa: feat: add padding and margin character support (@aymanbagabas)045a87b: feat: add padding and margin character support (#546) (@aymanbagabas)Bug fixes
99fc0ff: fix: correct nbsp codepoint (@aymanbagabas)8e1c474: fix: ensure we strip out \r\n from strings when getting lines (@aymanbagabas)4cb83b5: fix: make padding char a style prop (@caarlos0)07cadae: fix: revert back to regular space (@caarlos0)Thoughts? Questions? We love hearing from you. Feel free to reach out on Twitter, The Fediverse, or on Discord.
v2.0.0-beta.2Compare Source
So Hot Right Now: Lip Gloss v2 Beta 2
This release builds on top of the last beta 1 release. It includes a new API for compositing layers and views, table enhancements, and a bunch of bug fixes. Let's get into it!
Compositing
The big news in this release is compositing. Here's what it looks like:
Also note that layers can also be nested (see
Layer.AddLayers).Otherwise, that’s all there is to it!
For more info see
Layer,Canvas, and the compositing example.Table Enhancements
Tables are one of the most beloved Charm components, and we've been working to
make them as polished as possible. In this release several bugs were fixed,
and many other rendering enhancements were made. You can check most of the fixes
on #526.
We're also refactoring the Bubbles' table component to use the Lip Gloss' table package, and making their APIs similar, as before they were relatively different. This means that if you use Tables via Bubbles in your Bubble Tea app, you'll be able to reap the benefits soon too!
Changelog
New Features
BaseStyleto set background color for the whole table (#519) (@andreynering)GetHeaders,GetDataandDataToMatrix(@andreynering)Bug fixes
nil(#508) (@andreynering)Documentation updates
Other work
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-beta.1Compare 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.2Compare 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
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 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
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.
🐇 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
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, use
lipgloss.Println(andlipgloss.Printfand 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
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 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 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 • نحنُ نحب المصادر المفتوحة
pelletier/go-toml (github.com/pelletier/go-toml)
v2.2.4Compare Source
Highlight
In this release, @mikattack removed the last dependency of go-toml! 🎉 (#981)
What's Changed
Documentation
Other changes
stretchr/testifywith an internal test suite by @mikattack in #981New Contributors
Full Changelog: pelletier/go-toml@v2.2.3...v2.2.4
v2.2.3Compare Source
What's Changed
What's new
int,uint, andfloatas map keys by @daniel-weisse in #958Performance
Fixed bugs
Documentation
Other changes
New Contributors
Full Changelog: pelletier/go-toml@v2.2.2...v2.2.3
v2.2.2Compare Source
What's Changed
Fixed bugs
New Contributors
Full Changelog: pelletier/go-toml@v2.2.1...v2.2.2
v2.2.1Compare Source
What's Changed
Fixed bugs
New Contributors
Full Changelog: pelletier/go-toml@v2.2.0...v2.2.1
v2.2.0Compare Source
What's Changed
What's new
json.Numbertype by @dangra in #923Fixed bugs
Documentation
Other changes
New Contributors
Full Changelog: pelletier/go-toml@v2.1.1...v2.2.0
v2.1.1Compare Source
What's Changed
Fixed bugs
New Contributors
Full Changelog: pelletier/go-toml@v2.1.0...v2.1.1
v2.1.0Compare Source
This new minor release brings back the
commentedstruct field tag from go-toml v1. It makes it easier to generate default or example configuration files. For instance:generates this TOML document:
This feature was often mentioned as a blocker to upgrading from go-toml v1. Hopefully bringing it back in scope will help folks make the transition!
An other noteworthy improvement is on type mismatch errors. They now include the human-readable context, and include the struct field name of the faulty value if applicable.
Before:
After:
What's Changed
What's new
Fixed bugs
Other changes
Go 1.21by @michalbiesek in #885New Contributors
Full Changelog: pelletier/go-toml@v2.0.9...v2.1.0
v2.0.9Compare Source
What's Changed
Fixed bugs
Other changes
New Contributors
Full Changelog: pelletier/go-toml@v2.0.8...v2.0.9
v2.0.8Compare Source
What's Changed
What's new
Fixed bugs
Documentation
New Contributors
Full Changelog: pelletier/go-toml@v2.0.7...v2.0.8
v2.0.7Compare Source
What's Changed
Fixed bugs
Documentation
New Contributors
Full Changelog: pelletier/go-toml@v2.0.6...v2.0.7
v2.0.6Compare Source
What's Changed
What's new
Performance
Other changes
New Contributors
Full Changelog: pelletier/go-toml@v2.0.5...v2.0.6
v2.0.5Compare Source
What's Changed
Fixed bugs
Full Changelog: pelletier/go-toml@v2.0.4...v2.0.5
v2.0.4Compare Source
This version has compatibility issues with Go <= 1.17. Though go-toml doesn't officially support Go less than 2 versions old, a new version has been released with a backward-compatible fix: https://github.com/pelletier/go-toml/releases/tag/v2.0.5.
What's Changed
Fixed bugs
New Contributors
Full Changelog: pelletier/go-toml@v2.0.3...v2.0.4
v2.0.3Compare Source
What's Changed
Fixed bugs
Other changes
Full Changelog: pelletier/go-toml@v2.0.2...v2.0.3
v2.0.2Compare Source
What's Changed
Fixed bugs
Other changes
Full Changelog: pelletier/go-toml@v2.0.1...v2.0.2
v2.0.1Compare Source
What's Changed
Fixed bugs
Documentation
New Contributors
Full Changelog: pelletier/go-toml@v2.0.0...v2.0.1
v2.0.0Compare Source
It is finally here! go-toml v2 is now stable. 🎉
Only just over one year after I started working on it. This version of go-toml has been rebuilt from the ground up. It respects the latest TOML specification. Countless bugs have been fixed. It behaves more like the standard library. And it is much faster. Special attention was given to keeping the public API to a minimum. Continuing the strict policy of backward compatibility, the next breaking change will be in another 5 years!
Thank you to everybody who contributed to this new version, as well as folks willing to try out the intermediate beta versions. Shout out to @moorereason for reporting many issues during the development process using differential fuzzing, as well as @bep for running a beta on the popular Hugo project!
There is still some work that could be done to improve the performance of the library (#758 and #669 for instance). But I am confident that the library is in a good-enough place at the moment for folks to reap the benefits of the rewrite. The major feature removal is the sort-of-AST that v1 provided. It allowed manipulating an arbitrary document and writing it back out. This was done to cut down the scope of the project, removing a feature that had unclear use-cases. The v2 parser creates some intermediate AST so that if somebody is up to design a Document API the tools should be available to do so. Please reach out if you are interested!
The readme contains a list of differences between v1 and v2 to be aware of when upgrading. Please report any issue you may have with the new version in the bug tracker 🐞, provide feedback, and ask questions in Discussions 💬.
With this release, go-toml v1 will not be receiving any updates. This is required to keep maintenance of the project to a minimum.
Hopefully, this change doesn't break your thing!
Full commit log: pelletier/go-toml@c9a09d8...v2
Thank you contributors: @pelletier @oschwald @moorereason @xwjdsh @kkHAIKE @RiyaJohn @jidicula @zostay @mmorel-35.
Configuration
📅 Schedule: Branch creation - "before 6am on monday" (UTC), 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 these updates again.
This PR was generated by Mend Renovate. View the repository job log.