fix(deps): update go updates #78
Open
+118
−118
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
|
redhat-renovate-bot
force-pushed
the
renovate/go-updates
branch
11 times, most recently
from
52f5a3d to
4f2dacb
Compare
redhat-renovate-bot
force-pushed
the
renovate/go-updates
branch
14 times, most recently
from
f7e5258 to
76c8d33
Compare
redhat-renovate-bot
force-pushed
the
renovate/go-updates
branch
4 times, most recently
from
cfe59db to
e14d165
Compare
redhat-renovate-bot
force-pushed
the
renovate/go-updates
branch
16 times, most recently
from
a8ea1aa to
b2fef2f
Compare
redhat-renovate-bot
force-pushed
the
renovate/go-updates
branch
12 times, most recently
from
a3ace71 to
b432869
Compare
Signed-off-by: redhat-renovate-bot <[email protected]>
redhat-renovate-bot
force-pushed
the
renovate/go-updates
branch
from
b432869 to
0695b05
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:
v0.3.1->v1.5.0v2.2.0->v2.3.0v5.3.0->v7.2.0v0.9.1->v0.19.0v1.0.3->v1.0.5v1.7.19->v1.9.0v0.1.0->v1.0.0v1.2.5->v1.2.7v0.2.4->v0.4.1v3.11.0->v3.12.2v2.0.0+incompatible->v3.0.0v5.6.0->v5.9.11v0.10.0->v0.13.0v0.5.1->v0.6.0v1.4.1->v1.4.3v1.2.6->v1.3.0v0.19.6->v0.21.1v0.20.2->v0.21.0v0.22.3->v0.23.1v5.0.6->v5.1.0v1.2.0->v1.2.5v0.50.0->v0.53.0v0.6.8->v0.7.0v0.6.0->v0.7.04bb14d4->6e76a2bv0.3.15->v1.0.2v0.0.9->v0.0.27v0.7.7->v0.9.0v1.0.4->v2.0.063d38b5->9ace650f784269->9b43ea0v0.2.0->v0.5.0v0.7.1->v0.7.2v2.11.0->v2.23.4v1.27.10->v1.37.0v1.1.13->v1.3.0v1.2.0->v1.2.1v1.10.0->v1.12.0ce21e3f->3333746v0.0.0->v3.9.0+incompatible3f1513d->396b36fv0.0.0-20190128024246-5eb7ae5bdb7a->v0.32.0v0.68.0->v0.84.0v1.16.0->v1.22.0v0.4.0->v0.6.2v0.44.0->v0.65.0v0.11.0->v0.17.0v0.10.0->v0.11.0v1.0.5->v1.0.7v1.9.0->v1.10.0v1.1.0->v1.3.1v0.0.4->v0.0.5v0.17.0->v0.26.0v0.26.0->v0.42.0v0.18.0->v0.30.0v0.21.0->v0.34.0v0.21.0->v0.33.0v0.16.0->v0.27.0v0.3.0->v0.12.0v0.21.1-0.20240508182429-e35e4ccd0d2d->v0.35.0v1.6.8->v2.0.6fc5f0ca->7130f93v1.64.1->v1.73.0v1.34.1->v1.36.6v2.4.0->v3.0.1v0.28.12->v0.33.3v0.28.12->v0.33.3v0.28.12->v0.33.3v0.28.3->v0.33.3v0.28.12->v0.33.3v0.28.12->v0.33.3v0.28.12->v0.33.3v0.28.12->v0.33.3v0.28.12->v0.33.3v8.0.0+incompatible->v11.0.0+incompatiblev0.28.12->v0.33.3v0.28.12->v0.33.3v0.28.12->v0.33.3v0.28.12->v0.33.3v0.28.12->v0.33.3v0.28.12->v0.33.3v0.28.12->v0.33.3v0.28.12->v0.33.3v0.28.12->v0.33.3v0.28.12->v0.33.3v0.28.12->v0.33.3v0.28.12->v0.33.3c0856e2->ddb642ev0.4.0->v2.130.1v2.100.1->v2.130.1v0.28.12->v0.33.3v0.28.12->v0.33.3v0.28.12->v0.33.32695361->f3f2b99v0.28.12->v0.33.3v0.28.12->v0.33.3v0.28.12->v0.33.3v0.28.12->v0.33.3v0.28.12->v0.33.3v1.28.12->v1.33.3v0.28.12->v0.30.14v0.28.12->v0.33.3v0.28.12->v0.33.3v0.28.12->v0.33.3v0.28.12->v0.33.3v0.28.12->v0.33.3v0.28.12->v0.33.33b25d92->4c0f3b2v1.2.0->v1.5.2v1.2.3->v1.4.0v1.57.0-alpha1->v1.62.0v0.2.6->v0.2.7v0.0.0-20220329064328-f3cc58c6ed90->v0.2.4v0.0.0-20220329064328-f3cc58c6ed90->v0.2.4v0.16.3->v0.21.0bc3834c->cfa47c3v4.3.0->v6.3.0v1.3.0->v1.5.0Warning
Some dependencies could not be looked up. Check the Dependency Dashboard for more information.
Release Notes
BurntSushi/toml (github.com/BurntSushi/toml)
v1.5.0Compare Source
Mostly some small bugfixes, with a few small new features:
Add Position.Col, to mark the column an error occurred (#410)
Print more detailed errors in the
tomlvCLI.Ensure ParseError.Message is always set (#411)
Allow custom string types as map keys (#414)
Mark meta keys as decoded when using Unmarshaler interface (#426)
Fix encoding when nested inline table ends with map (#438)
Fix encoding of several layers of embedded structs (#430)
Fix ErrorWithPosition panic when there is no newline in the TOML document (#433)
v1.4.0Compare Source
This version requires Go 1.18
Add toml.Marshal() (#405)
Require 2-digit hour (#320)
Wrap UnmarshalTOML() and UnmarshalText() return values in ParseError for position information (#398)
Fix inline tables with dotted keys inside inline arrays (e.g.
k=[{a.b=1}]) (#400)v1.3.2Compare Source
Fix reading
BURNTSUSHI_TOML_110again 😅 The fix for 1.3.1 caused a race issue with multiple decodes being run in parallel.v1.3.1Compare Source
This fixes two small bugs:
The
BURNTSUSHI_TOML_110environment variable would be checked on package import, rather than Decode().This meant that setting
os.Setenv("BURNTSUSHI_TOML_110", "")had no effect, as it happens after the import.Fix order of
Meta.Keys()for inline tables (this has been an issue since support for inline tables was added).v1.3.0Compare Source
New features:
Support upcoming TOML 1.1
While it looks like TOML 1.1 is mostly stable and I don't expect any further major changes, there are NO compatibility guarantees as it is NOT yet released and anything can still change.
To use it, set the
BURNTSUSHI_TOML_110environment variable to any value, which can be done either withos.SetEnv()or by the user running a program.A full list is changes is available in the TOML ChangeLog; the two most notable ones are that newlines and trailing commas are now allowed in inline tables, and Unicode in bare keys can now be used – this is now a valid document:
Allow MarshalTOML and MarshalText to be used on the document type itself, instead of only fields (#383).
Bufixes:
\escapes at the end of line weren't processed correctly in multiline strings (#372).Read over UTF-8 BOM (#381).
omitemptystruct tag did not work for pointer values (#371).Fix encoding anonymous structs on 32bit systems (#374).
v1.2.1Compare Source
This release fixes the
omitemptystruct tag on an uncomparable type panicking.v1.2.0Compare Source
This release adds a few additional features:
Support encoding and decoding json.Number, making interoperability with JSON when using json.Encoder.UseNumber() easier.
Support time.Duration string format; an integer will be interpreted as nanoseconds (like before), but a string like "5h" will be parsed. On encoding the string format is used.
The omitempty struct tag now also works for structs with all zero values, for example an empty time.Time. A struct is considered "empty" when all fields (exported and private) are the zero value.
Allow using interface{} (or any) as the map key when decoding.
And some fixes:
Fix encoding.TextUnmarshaler not working for map values.
Make encoding.TextUnmarshaler and toml.Unmarshaler work if MarshalText() or MarshalTOML() have a pointer receiver.
Error out on nil returns from MarshalTOML/MarshalText; before they would get encoded as invalid TOML (keyname =).
Fix a panic where it would try to encode array = [{}, 0] as:
Which isn't valid as 0 isn't a table.
Some better error reporting for some errors.
v1.1.0Compare Source
Just a few bugfixes:
Skip fields with
toml:"-"even when they're unsupported types. Previously something like this would fail to encode due tofuncbeing an unsupported type:Multiline strings can't end with
\. This is valid:Valid
Invalid
TOMLMarshaler. Previously they would always include quoting (e.g."value"), while the entire point of this interface is to bypass that.v1.0.0Compare Source
This release adds much more detailed errors, support for the
toml.Marshalerinterface, and several fixes.There is no special meaning in the jump to v1.0; the 0.x releases were always treated as if they're 1.x with regards to compatibility; the versioning scheme for this library predates the release of modules.
New features
Error reporting is much improved; the reported position of errors should now always be correct and the library can print more detailed errors (#299, #332)
Decode always return a
toml.ParseError, which has three methods:Error()behaves as before and shows a single concise line with the error.ErrorWithPosition()shows the same error, but also shows the line the error occurred at, similar to e.g. clang or the Rust compiler.ErrorWithUsage()is the same asErrorWithPosition(), but may also show a longer usage guidance message. This isn't always present (in which case it behaves identical toErrorWithPosition()), but it should be present for most common mistakes and sources of confusion.Which error the correct one to use is depends on your application and preferences; in general I would recommend using at least
ErrorWithPosition()for user-facing errors, as it's much more helpful for users of any skill level. If your users are likely to be non-technical thenErrorWithUsage()is probably a good idea; I did my best to avoid technical jargon such as "newline" and phrase things in a way that's understandable by most people not intimately familiar with these sort of things.Additionally, the TOML key that fialed should now always be reported in all errors.
Add
toml.Marshalerinterface. This can be used if you want full control over how something is marshalled as TOML, similar tojson.Marshaleretc. This takes precedence overencoding.TextMarshaler. (#327)Allow TOML integers to be decoded to a Go float (#325)
Previously
int = 42could only be decoded to anint*type; now this can also be decoded in afloattype as long as it can be represented without loss of data.Fixes
Key.String() is now quoted when needed (#333)
Fix decoding of nested structs on 32bit platforms (#314)
Empty slices are now always
[]T{}rather than nil, which was the behaviour in v0.3.1 and before. While they are identical for most purposes, encoding/json encodes them different ([]vs.null), making it an (accidentally) incompatible change (#339)v0.4.1Compare Source
This fixes a cyclic module dependency issue with github.com/BurntSushi/toml-test that prevented some people from updating. See #313 for some details.
v0.4.0Compare Source
After some time of inactivity this package is now maintained again.
This release should support alll of TOML 1.0 and has various bugfixes and a few small improvements.
This requires Go 1.13 or newer; older Go versions will no longer work.
TOML 1.0 support
Previously this library implemented TOML 0.3; now all of TOML 1.0 is supported:
Support dotted keys (
a.b = 1,a = {b.c = 2}).Mixed arrays: in previous TOML versions array values all had to be of the same type; you can now freely mix types, including inline tables.
Support hex (
0x2f9a), binary (0b0110), and octal (0o777) literals, and supportnanandinffor floats.Support local datetimes, dates, and times. These are dates and times without a timezone and are parsed in the local timezone.
Allow accidental whitespace between backslash and newline in the line continuation operator in multi-line basic strings.
There should be no incompatibilities as such; all existing valid TOML files should continue to work. However, the parser previously allowed the following invalid values:
It would allow literal control characters in strings.
It would allow leading zeroes in decimal ints and floats.
Neither of these was ever valid TOML, and are explicitly forbidden by the specification. But the library erroneously permitted them.
Other changes
Set up Go modules.
Allow escaping the
\, and allow triple-quotes strings to end with a quote (e.g.x="""x"""").All control characters inside strings are properly escaped when encoding.
Support encoding nested anonymous structs.
Encode toml.Primitive values.
You get a more helpful error on UTF-16 files (probably the most common non-UTF-8 compatible encoding). Also read over UTF-16 BOM in UTF-8 files.
Call
MarshalTextandUnmarshalTextconsistently on all types; before this didn't always happen in some cases.Allow empty quoted keys (
"" = 1); silly, but explicitly mentioned as valid.Don't panic in encoder on unsupported types; return an error instead.
Don't panic on unclosed inline arrays.
Add
Decoderand deprecateDecodeReader(); this is more consistent with how other decoders tend to work and allows adding decoding options.Add
DecodeFS()for Go 1.16 or newer.Avoid creating new functions/allocations in lexSkip; small performance improvement.
cespare/xxhash (github.com/cespare/xxhash/v2)
v2.3.0Compare Source
checkpoint-restore/go-criu (github.com/checkpoint-restore/go-criu/v5)
v7.2.0Compare Source
What's Changed
New Contributors
Full Changelog: checkpoint-restore/go-criu@v7.1.0...v7.2.0
v7.1.0Compare Source
What's Changed
protogetterby @snprajwal in https://github.com/checkpoint-restore/go-criu/pull/153crit exploreby @snprajwal in https://github.com/checkpoint-restore/go-criu/pull/158Full Changelog: checkpoint-restore/go-criu@v7.0.0...v7.1.0
v7.0.0Compare Source
What's Changed
stylecheckto golangci-lint by @snprajwal in https://github.com/checkpoint-restore/go-criu/pull/128pagesIDfield inMemoryReaderstruct by @behouba in https://github.com/checkpoint-restore/go-criu/pull/142FindPsmethod onPsTreeby @behouba in https://github.com/checkpoint-restore/go-criu/pull/145crit x skfor sockets by @snprajwal in https://github.com/checkpoint-restore/go-criu/pull/138New Contributors
Full Changelog: checkpoint-restore/go-criu@v6.3.0...v7.0.0
v6.3.0Compare Source
What's Changed
Full Changelog: checkpoint-restore/go-criu@v6.2.0...v6.3.0
v6.2.0Compare Source
What's Changed
Full Changelog: checkpoint-restore/go-criu@v6.1.0...v6.2.0
v6.1.0Compare Source
What's Changed
Full Changelog: checkpoint-restore/go-criu@v6.0.0...v6.1.0
v6.0.0Compare Source
What's Changed
unmarshalPagemap(), use stdout for CLI output by @snprajwal in https://github.com/checkpoint-restore/go-criu/pull/78Full Changelog: checkpoint-restore/go-criu@v5.3.0...v6.0.0
cilium/ebpf (github.com/cilium/ebpf)
v0.19.0Compare Source
Major Performance Improvements
This release includes significant performance optimizations across multiple areas:
Program.Stats()method allows querying runtime statistics without fetching full ProgramInfoCO-RE Improvements
Build System and Toolchain Updates
Enhanced Map Support
MapSpec.Tagsfield for readingbtf_decl_tagattributes set on mapsBPF_F_NO_PREALLOChints and warnings for map types that require this flagAssembly and Instruction Handling
Memory and Variable Access
VariableandMemorytypesWindows Support Improvements
Bug Fixes
BatchLookupandBatchLookupDelete(#1741)InvalidOpCodeforStoreImmwithDWordsize (#1767)WalkDirharder to misuse and added Windows support (#1652)structs.HostLayoutin GoFormatter (#1686)Compatibility Notes
What's Changed
Configuration
📅 Schedule: Branch creation - Between 12:00 AM and 03:59 AM, only on Monday ( * 0-3 * * 1 ) (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.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR has been generated by Renovate Bot.