chore(deps): update all dependencies (major) #172
Conversation
This file contains 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
![renovate[bot]](https://avatars.githubusercontent.com/in/2740?s=60&v=4){kind=small}
renovate
bot
added
dependencies
ℹ Artifact update noticeFile name: go.modIn order to perform the update(s) described in the table above, Renovate ran the
Details:
|
renovate
bot
force-pushed
the
renovate/major-all-dependencies
branch
from
1e95112 to
a129cd6
Compare
renovate
bot
changed the title
renovate
bot
force-pushed
the
renovate/major-all-dependencies
branch
from
a129cd6 to
e72a0e0
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.6.0->v2.1.0v1.2.0->v2.0.1v1.64.6->v2.0.2v1.0.0->v2.23.0v1.0.1->v2.0.0v1.9.5->v2.2.4v2.4.0->v3.0.1Release Notes
ashanbrown/forbidigo (github.com/ashanbrown/forbidigo)
v2.1.0Compare Source
What's Changed
Full Changelog: ashanbrown/forbidigo@v2.0.1...v2.1.0
v2.0.1: Drop golang < 1.18Compare Source
v2.0.0: Upgrade x/toolsCompare Source
Upgrades x-tools to fix go 1.23, drops support for go < 1.18
ashanbrown/makezero (github.com/ashanbrown/makezero)
v2.0.1Compare Source
Fix v2 release following https://go.dev/wiki/Modules#releasing-modules-v2-or-higher
v2.0.0: Bump minimum required go version to 1.18 and upgrade depsCompare Source
What's Changed
New Contributors
Full Changelog: ashanbrown/makezero@v1.2.0...v2.0.0
golangci/golangci-lint (github.com/golangci/golangci-lint)
v2.0.2Compare Source
sourceoptionv2.0.1Compare Source
golines: fix settings during linter loadversionfield before the configurationforbidigo: fix migrationv2.0.0Compare Source
golangci-lint fmtcommand with dedicated formatter configurationgolangci-lint migratecommand to help migration from v1 to v2 (cf. Migration guide)run.relative-path-mode(cf. Migration guide)--fast-onlyflag (cf. Migration guide)linters.exclusions.warn-unusedto log a warning if an exclusion rule is unused.golinesformatter https://github.com/segmentio/golinesstaticcheck,stylecheck,gosimpleinto one linter (staticcheck) (cf. Migration guide)go-critic: from 0.12.0 to 0.13.0gomodguard: from 1.3.5 to 1.4.1 (block explicit indirect dependencies)nilnil: from 1.0.1 to 1.1.0 (new option:only-two)perfsprint: from 0.8.2 to 0.9.1 (checker name in the diagnostic message)staticcheck: newquickfixset of rulestestifylint: from 1.5.2 to 1.6.0 (new options:equal-values,suite-method-signature,require-string-msg)wsl: from 4.5.0 to 4.6.0 (new option:allow-cuddle-used-in-block)bidichk: from 0.3.2 to 0.3.3errchkjson: from 0.4.0 to 0.4.1errname: from 1.0.0 to 1.1.0funlen: fixignore-commentsoptiongci: from 0.13.5 to 0.13.6gosmopolitan: from 1.2.2 to 1.3.0inamedparam: from 0.1.3 to 0.2.0intrange: from 0.3.0 to 0.3.1protogetter: from 0.3.9 to 0.3.12unparam: from8a5130cto0df0534golangci-lint config path --jsongolangci-lint help linters --jsongolangci-lint help formatters --jsongolangci-lint linters --jsongolangci-lint formatters --jsongolangci-lint version --jsonv1.64.8Compare Source
v1.64.7Compare Source
depguard: from 2.2.0 to 2.2.1dupl: from3e9179atof665c8dgosec: from 2.22.1 to 2.22.2staticcheck: from 0.6.0 to 0.6.1hashicorp/hcl (github.com/hashicorp/hcl)
v2.23.0Compare Source
Bugs Fixed
v2.22.0Compare Source
Enhancements
v2.21.0Compare Source
Enhancements
ParseTraversalPartial, which allows traversals that include the splat ([*]) index operator. (#673)for_each, and will transfer those marks (as much as technically possible) to values in the generated blocks. (#679)Bugs Fixed
v2.20.1Compare Source
Bugs Fixed
ExprSyntaxErrorwhen an invalid namespaced function is encountered during parsing (#668)Internal
v2.20.0Compare Source
Enhancements
Bugs Fixed
iteratoris invalid return this error instead of consequential errors (#656)v2.19.1Compare Source
What's Changed
Full Changelog: hashicorp/hcl@v2.19.0...v2.19.1
v2.19.0Compare Source
Enhancements
dynblock.Expandnow supports an optional hook for calling applications to check and potentially veto (by returning error diagnostics) particularfor_eachvalues. The behavior is unchanged for callers that don't set the new option. (#634)Bugs Fixed
v2.18.1Compare Source
Bugs Fixed
v2.18.0Compare Source
Enhancements
HCL now uses the tables from Unicode 15 when performing string normalization and character segmentation. HCL was previously using the Unicode 13 tables.
For calling applications where consistent Unicode support is important, consider also upgrading to Go 1.21 at the same time as adopting HCL v2.18.0 so that the standard library unicode tables (used for case folding, etc) will also be from Unicode 15.
v2.17.1Compare Source
Enhancements
https://at the start of a URL known to use that scheme. (#617)Bugs Fixed
anykeyword, avoiding an incorrect panic at runtime. (#625)v2.17.0Compare Source
Enhancements
HCL now uses a newer version of the upstream
ctylibrary which has improved treatment of unknown values: it can now track additional optional information that reduces the range of an unknown value, which allows some operations against unknown values to return known or partially-known results. (#590)Note: This change effectively passes on
cty's notion of backward compatibility whereby unknown values can become "more known" in later releases. In particular, if your caller is usingcty.Value.RawEqualsin its tests against the results of operations with unknown values then you may see those tests begin failing after upgrading, due to the values now being more "refined".If so, you should review the refinements with consideration to the
ctyrefinements docs and update your expected results to match only if the reported refinements seem correct for the given situation. TheRawEqualsmethod is intended only for making exact value comparisons in test cases, so main application code should not use it; useEqualsinstead for real logic, which will take refinements into account automatically.v2.16.2Compare Source
Bugs Fixed
v2.16.1Compare Source
Bugs Fixed
Range.EndforFunctionCallwith incomplete argument (#588)v2.16.0Compare Source
Enhancements
ext/typeexpr: Modify the
Defaultsfunctionality to implement additional flexibility. HCL will now upcast lists and sets into tuples, and maps into objects, when applying default values if the applied defaults cause the elements within a target collection to have differing types. Previously, this would have resulted in a panic, now HCL will return a modified overall type. (#574)Users should return to the advice provided by v2.14.0, and apply the go-cty convert functionality after setting defaults on a given
cty.Value, rather than before.hclfmt: Avoid rewriting unchanged files. (#576)
hclsyntax: Simplify the AST for certain string expressions. (#584)
Bugs Fixed
formatSpaces. (#511)v2.15.0Compare Source
Bugs Fixed
Enhancements
Defaultsstruct and associated functions can apply additional and more flexible 'unsafe' conversions (examples include tuples into collections such as lists and sets, and additional safety around null and dynamic values). (#564)cty.Value, rather than after, if they require a specificcty.Type. (#564)v2.14.1Compare Source
Bugs Fixed
v2.14.0Compare Source
Enhancements
TypeConstraint. Attributes can be wrapped in the specialoptional(…)modifier, allowing the attribute to be omitted while still meeting the type constraint. For more information, cty's documentation on conversion between object types. (#549)TypeConstraintWithDefaults. In this mode, theoptional(…)modifier accepts a second argument which can be used as the default value for omitted object attributes. The function returns both acty.Typeand associatedDefaults, the latter of which has anApplymethod to apply defaults to a given value. (#549)v2.13.0Compare Source
Enhancements
hcl.Diagnosticnow has an additional fieldExtrawhich is intended for carrying arbitrary supporting data ("extra information") related to the diagnostic message, intended to allow diagnostic renderers to optionally tailor the presentation of messages for particular situations. (#539)errorvalue without any post-processing. (#539)Bugs Fixed
hclwrite.Formatruns concurrently with itself. (#534)v2.12.0Compare Source
Enhancements
TokensForTuple,TokensForObject, andTokensForFunctionCallallow for more easily constructing the three constructs which are supported for static analysis and which HCL-based languages typically use in contexts where an expression is used only for its syntax, and not evaluated to produce a real value. For example, these new functions together are sufficient to construct all valid type constraint expressions from the Type Expressions Extension, which is the basis of variable type constraints in the Terraform language at the time of writing. (#502)IsJSONExpressionandIsJSONBodyto determine if a given expression or body was created by the JSON syntax parser. In normal situations it's better not to worry about what syntax a particular expression/body originated in, but this can be useful in some trickier cases where an application needs to shim for backwards-compatibility or for static analysis that needs to have special handling of the JSON syntax's embedded expression/template conventions. (#524)Bugs Fixed
v2.11.1Compare Source
Bugs Fixed
v2.11.0Compare Source
Enhancements
Bugs Fixed
v2.10.1Compare Source
function.ArgErrorwhose argument index is out of range for the length of the arguments. Previously this would often lead to a panic, but now it'll return a less-precice error message instead. Functions that return out-of-bounds argument indices still ought to be fixed so that the resulting error diagnostics can be as precise as possible. (#472)hcl.Indexandhcl.GetAttr. These are part of the implementation of indexing and attribute lookup in the native syntax expression language too, so the new error messages will apply to problems using those operators. (#474)v2.10.0Compare Source
Enhancements
${...}template interpolation sequences will now produce an extra hint message about the need to escape as$${when trying to include interpolation syntax for other languages like shell scripting, AWS IAM policies, etc. (#462)v2.9.1Compare Source
Bugs Fixed
v2.9.0Compare Source
Enhancements
v2.8.2Compare Source
Bugs Fixed
forexpression marked conditional. (#438)v2.8.1Compare Source
Bugs Fixed
v2.8.0Compare Source
Enhancements
Bugs Fixed
(and)tokens when an expression is surrounded by parentheses. Previously it would incorrectly recognize those tokens as being extraneous tokens outside of the expression. (#426)!(unary boolean "not") operator and its subsequent operand. (#403)v2.7.2Compare Source
Bugs Fixed
null[*]was previously always returning an unknown value, even though the rules for[*]normally call for it to return an empty tuple when applied to a null. As well as being a surprising result, it was particularly problematic because it violated the rule that a calling application may assume that an expression result will always be known unless the application itself introduces unknown values via the evaluation context.null[*]will now produce an empty tuple. (#416)v2.7.1Compare Source
Bugs Fixed
v2.7.0Compare Source
Enhancements
ParseWithStartPos, which allows overriding the starting position for parsing in case the given JSON bytes are a fragment of a larger document, such as might happen when decoding withencoding/jsoninto ajson.RawMessage. (#389)ParseExpression, which allows parsing a JSON string directly in expression mode, whereas previously it was only possible to parse a JSON string in body mode. (#381)Blocktype now supportsSetTypeandSetLabels, allowing surgical changes to the type and labels of an existing block without having to reconstruct the entire block. (#340)Bugs Fixed
v2.6.0Compare Source
Enhancements
Spec,ValidateSpec, which allows custom validation of values at decode-time. (#387)Bugs Fixed
v2.5.1Compare Source
Bugs Fixed
foo.*) (#374)v2.5.0Compare Source
Enhancements
v2.4.0Compare Source
Enhancements
Bugs Fixed
v2.3.0Compare Source
Enhancements
tryandcanto include in yourhcl.EvalContextwhen evaluating expressions, which allow users to make decisions based on the success of expressions. (#330)convertwhich you can include in yourhcl.EvalContextwhen evaluating expressions, allowing users to convert values to specific type constraints using the type constraint expression syntax. (#330)ctycapsule typetypeexpr.TypeConstraintTypewhich, when used as either a type constraint for a function parameter or as a type constraint for ahcldecattribute specification will cause the given expression to be interpreted as a type constraint expression rather than a value expression. (#330)hcldecattribute specifications. (#330)ctycapsuletypescustomdecode.ExpressionTypeandcustomdecode.ExpressionClosureTypewhich, when used as either a type constraint for a function parameter or as a type constraint for ahcldecattribute specification will cause the given expression (and, for the closure type, also thehcl.EvalContextit was evaluated in) to be captured for later analysis, rather than immediately evaluated. (#330)v2.2.0Compare Source
Enhancements
AttrSpecorBlockAttrsSpec) now captures expression evaluation metadata in any errors it produces during type conversions, allowing for better feedback in calling applications that are able to make use of this metadata when printing diagnostic messages. (#329)Bugs Fixed
IndexExpr,SplatExpr, andRelativeTraversalExprwill now report a source range that covers all of their child expression nodes. Previously they would report only the operator part, such as["foo"],[*], or.foo, which was problematic for callers using source ranges for code analysis. (#328)v2.1.0Compare Source
Enhancements
json.Unmarshalin the Go standard library.Bugs Fixed
Body.Blocksmethod was returing the blocks in an indefined order, rather than preserving the order of declaration in the source input. (#313)TokensForTraversalfunction (and thus in turn theBody.SetAttributeTraversalmethod) was not correctly handling index steps in traversals, and thus producing invalid results. (#319)v2.0.0Compare Source
Initial release of HCL 2, which is a new implementating combining the HCL 1
language with the HIL expression language to produce a single language
supporting both nested configuration structures and arbitrary expressions.
HCL 2 has an entirely new Go library API and so is not a drop-in upgrade
relative to HCL 1. It's possible to import both versions of HCL into a single
program using Go's semantic import versioning mechanism:
Prior to v2.0.0 there was not a curated changelog. Consult the git history
from the latest v1.x.x tag for information on the changes to HCL 1.
matttproud/golang_protobuf_extensions (github.com/matttproud/golang_protobuf_extensions)
v2.0.0Compare Source
Summary: Modernization of this package to Go standards in 2022, mostly
through internal cleanups.
New Features: None
The last time this package was significantly modified was 2016, which predates
cmp, subtests, the modern Protocol Buffer implementation, and numerous Gopractices that emerged in the intervening years. The new release is tested
against Go 1.19, though I expect it would work with Go 1.13 just fine.
Finally, I declared bankruptcy on the vendored test fixtures and opted for
creating my own. This is due to the underlying implementation of the generated
code in conjunction with working with a moving target that is an external data
model representation.
Upgrade Notes: This is the aborted v1.0.3 release repackaged as a new
major version 2. To use this, you will need to do or check the following:
The Protocol Buffer messages you provide to this API are from the
google.golang.org/protobufmodule. Take special care to audit anygenerated or checked-in Protocol Buffer message file assets. They may need
to be regenerated.
Your code should presumably use the
google.golang.org/protobufmodule forProtocol Buffers.
This is a new major version of the module, so you will need to transition
from module
github.com/matttproud/golang_protobuf_extensionstogithub.com/matttproud/golang_protobuf_extensions/v2.v1.0.4Compare Source
Summary: This is an emergency re-tag of v1.0.2 since v1.0.3 broke API
compatibility for legacy users. See the description of v1.0.2 for details.
v1.0.3Compare Source
DO NOT USE: Use v1.0.4 instead. What is described in v1.0.3 will be
transitioned to a new major version.
Summary: Modernization of this package to Go standards in 2022, mostly
through internal cleanups.
New Features: None
The last time this package was significantly modified was 2016, which predates
cmp, subtests, the modern Protocol Buffer implementation, and numerous Gopractices that emerged in the intervening years. The new release is tested
against Go 1.19, though I expect it would work with Go 1.13 just fine.
Finally, I declared bankruptcy on the vendored test fixtures and opted for
creating my own. This is due to the underlying implementation of the generated
code in conjunction with working with a moving target that is an external data
model representation.
v1.0.2Compare Source
Summary: Tagged version with Go module support.
New Features: None
End-users wanted a tagged release that includes Go module support.
pelletier/go-toml (github.com/pelletier/go-toml)
v2.2.4Compare Source
Highlight
In this release, @mikattack removed the last dependency of go-toml! 🎉 (https://github.com/pelletier/go-toml/pull/981)
What's Changed
Documentation
Other changes
stretchr/testifywith an internal test suite by @mikattack in https://github.com/pelletier/go-toml/pull/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 https://github.com/pelletier/go-toml/pull/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 https://github.com/pelletier/go-toml/pull/923Fixed bugs
Documentation
Other changes
New Contributors
Configuration
📅 Schedule: Branch creation - "every weekend" (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 was generated by Mend Renovate. View the repository job log.