Skip to content
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.

Sign up for GitHub

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

Jump to bottom

chore(deps): update go major updates #215

Closed
wants to merge 1 commit into from
Closed

chore(deps): update go major updates #215

wants to merge 1 commit into from

Conversation

renovate[bot]
Copy link
Contributor

@renovate renovate bot commented May 23, 2024 •
edited by adrianriobo
Loading

Mend Renovate

This PR contains the following updates:

Package Change Age Adoption Passing Confidence
github.com/hashicorp/hcl v1.0.0 -> v2.20.1 age adoption passing confidence
github.com/matttproud/golang_protobuf_extensions v1.0.1 -> v2.0.0 age adoption passing confidence
github.com/pelletier/go-toml v1.9.5 -> v2.2.2 age adoption passing confidence
github.com/santhosh-tekuri/jsonschema/v5 v5.3.1 -> v6.0.1 age adoption passing confidence
github.com/santhosh-tekuri/jsonschema/v5 v5.0.0 -> v6.0.1 age adoption passing confidence
gopkg.in/yaml.v2 v2.4.0 -> v3.0.1 age adoption passing confidence

Release Notes

hashicorp/hcl (github.com/hashicorp/hcl)

v2.20.1

Compare Source

Bugs Fixed
  • Return ExprSyntaxError when an invalid namespaced function is encountered during parsing (#​668)
Internal
  • Standardize on only two value dumping/diffing libraries (#​669)

v2.20.0

Compare Source

Enhancements
  • Support for namespaced functions (#​639)
Bugs Fixed
  • ext/dynblock: if iterator is invalid return this error instead of consequential errors (#​656)

v2.19.1

Compare Source

What's Changed

Full Changelog: hashicorp/hcl@v2.19.0...v2.19.1

v2.19.0

Compare Source

Enhancements
  • ext/dynblock: dynblock.Expand now supports an optional hook for calling applications to check and potentially veto (by returning error diagnostics) particular for_each values. The behavior is unchanged for callers that don't set the new option. (#​634)
Bugs Fixed
  • hclsyntax: Further fixes for treatment of "marked" values in the conditional expression, and better tracking of refined values into the conditional expression results, building on the fixes from v2.18.1. (#​633)

v2.18.1

Compare Source

Bugs Fixed
  • hclsyntax: Conditional expressions will no longer panic when one or both of their results are "marked", as is the case for situations like how HashiCorp Terraform tracks its concept of "sensitive values". (#​630)

v2.18.0

Compare 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.1

Compare Source

Enhancements
  • hclsyntax: When evaluating string templates that have a long known constant prefix, HCL will truncate the known prefix to avoid creating excessively-large refinements. String prefix refinements are intended primarily for relatively-short fixed prefixes, such as https:// at the start of a URL known to use that scheme. (#​617)
  • ext/tryfunc: The "try" and "can" functions now handle unknown values slightly more precisely, and so can return known values in more situations when given expressions referring to unknown symbols. (#​622)
Bugs Fixed
  • ext/typeexpr: Will no longer try to refine unknown values of unknown type when dealing with a user-specified type constraint containing the any keyword, avoiding an incorrect panic at runtime. (#​625)
  • ext/typeexpr: Now correctly handles attempts to declare the same object type attribute multiple times by returning an error. Previously this could potentially panic by creating an incoherent internal state. (#​624)

v2.17.0

Compare Source

Enhancements

  • HCL now uses a newer version of the upstream cty library 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 using cty.Value.RawEquals in 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 cty refinements docs and update your expected results to match only if the reported refinements seem correct for the given situation. The RawEquals method is intended only for making exact value comparisons in test cases, so main application code should not use it; use Equals instead for real logic, which will take refinements into account automatically.

v2.16.2

Compare Source

Bugs Fixed
  • ext/typeexpr: Verify type assumptions when applying default values, and ignore input values that do not match type assumptions. (#​594)

v2.16.1

Compare Source

Bugs Fixed
  • hclsyntax: Report correct Range.End for FunctionCall with incomplete argument (#​588)

v2.16.0

Compare Source

Enhancements

  • ext/typeexpr: Modify the Defaults functionality 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
  • hclwrite: Fix data race in formatSpaces. (#​511)

v2.15.0

Compare Source

Bugs Fixed
  • ext/typeexpr: Skip null objects when applying defaults. This prevents crashes when null objects are creating inside collections, and stops incomplete objects being created with only optional attributes set. (#​567)
  • ext/typeexpr: Ensure default values do not have optional metadata attached. This prevents crashes when default values are inserted into concrete go-cty values that have also been stripped of their optional metadata. (#​568)
Enhancements
  • ext/typeexpr: With the go-cty upstream depenendency updated to v1.12.0, the Defaults struct 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)
  • ext/typeexpr: With the go-cty upstream depenendency updated to v1.12.0, users should now apply the go-cty convert functionality before setting defaults on a given cty.Value, rather than after, if they require a specific cty.Type. (#​564)

v2.14.1

Compare Source

Bugs Fixed
  • ext/typeexpr: Type convert defaults for optional object attributes when applying them. This prevents crashes in certain cases when the objects in question are part of a collection. (#​555)

v2.14.0

Compare Source

Enhancements
  • ext/typeexpr: Added support for optional object attributes to TypeConstraint. Attributes can be wrapped in the special optional(…) 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)
  • ext/typeexpr: New function: TypeConstraintWithDefaults. In this mode, the optional(…) modifier accepts a second argument which can be used as the default value for omitted object attributes. The function returns both a cty.Type and associated Defaults, the latter of which has an Apply method to apply defaults to a given value. (#​549)

v2.13.0

Compare Source

Enhancements
  • hcl: hcl.Diagnostic now has an additional field Extra which 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)
  • hclsyntax: When an error occurs during a function call, the returned diagnostics will include extra information (as described in the previous point) about which function was being called and, if the message is about an error returned by the function itself, that raw error value without any post-processing. (#​539)
Bugs Fixed
  • hclwrite: Fixed a potential data race for any situation where hclwrite.Format runs concurrently with itself. (#​534)

v2.12.0

Compare Source

Enhancements
  • hclsyntax: Evaluation of conditional expressions will now produce more precise error messages about inconsistencies between the types of the true and false result expressions, particularly in cases where both are of the same structural type kind but differ in their nested elements. (#​530)
  • hclsyntax: The lexer will no longer allocate a small object on the heap for each token. Instead, in that situation it will allocate only when needed to return a diagnostic message with source location information. (#​490)
  • hclwrite: New functions TokensForTuple, TokensForObject, and TokensForFunctionCall allow 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)
  • json: New functions IsJSONExpression and IsJSONBody to 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
  • gohcl: Fix docs about supported types for blocks. (#​507)

v2.11.1

Compare Source

Bugs Fixed
  • hclsyntax: The type for an upgraded unknown value with a splat expression cannot be known (#​495)

v2.11.0

Compare Source

Enhancements
  • hclsyntax: Various error messages related to unexpectedly reaching end of file while parsing a delimited subtree will now return specialized messages describing the opening tokens as "unclosed", instead of returning a generic diagnostic that just happens to refer to the empty source range at the end of the file. This gives better feedback when error messages are being presented alongside a source code snippet, as is common in HCL-based applications, because it shows which innermost container the parser was working on when it encountered the error. (#​492)
Bugs Fixed
  • hclsyntax: Upgrading an unknown single value to a list using a splat expression must return unknown (#​493)

v2.10.1

Compare Source

  • dynblock: Decode unknown dynamic blocks in order to obtain any diagnostics even though the decoded value is not used (#​476)
  • hclsyntax: Calling functions is now more robust in the face of an incorrectly-implemented function which returns a function.ArgError whose 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)
  • hclsyntax: Ensure marks on unknown values are maintained when processing string templates. (#​478)
  • hcl: Improved error messages for various common error situtions in hcl.Index and hcl.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.0

Compare Source

Enhancements
  • dynblock,hcldec: Using dynblock in conjunction with hcldec can now decode blocks with unknown dynamic for_each arguments as entirely unknown values (#​461)
  • hclsyntax: Some syntax errors during parsing of the inside of ${ ... } 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.1

Compare Source

Bugs Fixed
  • hclsyntax: Fix panic for marked index value. (#​451)

v2.9.0

Compare Source

Enhancements
  • HCL's native syntax and JSON scanners -- and thus all of the other parsing components that build on top of them -- are now using Unicode 13 rules for text segmentation when counting text characters for the purpose of reporting source location columns. Previously HCL was using Unicode 12. Unicode 13 still uses the same algorithm but includes some additions to the character tables the algorithm is defined in terms of, to properly categorize new characters defined in Unicode 13.

v2.8.2

Compare Source

Bugs Fixed
  • hclsyntax: Fix panic for marked collection splat. (#​436)
  • hclsyntax: Fix panic for marked template loops. (#​437)
  • hclsyntax: Fix for expression marked conditional. (#​438)
  • hclsyntax: Mark objects with keys that are sensitive. (#​440)

v2.8.1

Compare Source

Bugs Fixed
  • hclsyntax: Fix panic when expanding marked function arguments. (#​429)
  • hclsyntax: Error when attempting to use a marked value as an object key. (#​434)
  • hclsyntax: Error when attempting to use a marked value as an object key in expressions. (#​433)

v2.8.0

Compare Source

Enhancements
  • hclsyntax: Expression grouping parentheses will now be reflected by an explicit node in the AST, whereas before they were only considered during parsing. (#​426)
Bugs Fixed
  • hclwrite: The parser will now correctly include the ( 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)
  • hclwrite: The formatter will now remove (rather than insert) spaces between the ! (unary boolean "not") operator and its subsequent operand. (#​403)
  • hclsyntax: Unmark conditional values in expressions before checking their truthfulness (#​427)

v2.7.2

Compare Source

Bugs Fixed
  • gohcl: Fix panic when decoding into type containing value slices. (#​335)
  • hclsyntax: The unusual expression 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)
  • hclsyntax: Fix panic when traversing a list, tuple, or map with cty "marks" (#​424)

v2.7.1

Compare Source

Bugs Fixed
  • hclwrite: Correctly handle blank quoted string block labels, instead of dropping them (#​422)

v2.7.0

Compare Source

Enhancements
  • json: There is a new function 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 with encoding/json into a json.RawMessage. (#​389)
  • json: There is a new function 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)
  • hclwrite: Block type now supports SetType and SetLabels, allowing surgical changes to the type and labels of an existing block without having to reconstruct the entire block. (#​340)
Bugs Fixed
  • hclsyntax: Fix confusing error message for bitwise OR operator (#​380)
  • hclsyntax: Several bug fixes for using HCL with values containing cty "marks" (#​404, #​406, #​407)

v2.6.0

Compare Source

Enhancements
  • hcldec: Add a new Spec, ValidateSpec, which allows custom validation of values at decode-time. (#​387)
Bugs Fixed
  • hclsyntax: Fix panic with combination of sequences and null arguments (#​386)
  • hclsyntax: Fix handling of unknown values and sequences (#​386)

v2.5.1

Compare Source

Bugs Fixed
  • hclwrite: handle legacy dot access of numeric indexes. (#​369)
  • hclwrite: Fix panic for dotted full splat (foo.*) (#​374)

v2.5.0

Compare Source

Enhancements
  • hclwrite: Generate multi-line objects and maps. (#​372)

v2.4.0

Compare Source

Enhancements
  • The Unicode data tables that HCL uses to produce user-perceived "column" positions in diagnostics and other source ranges are now updated to Unicode 12.0.0, which will cause HCL to produce more accurate column numbers for combining characters introduced to Unicode since Unicode 9.0.0.
Bugs Fixed
  • json: Fix panic when parsing malformed JSON. (#​358)

v2.3.0

Compare Source

Enhancements
  • ext/tryfunc: Optional functions try and can to include in your hcl.EvalContext when evaluating expressions, which allow users to make decisions based on the success of expressions. (#​330)
  • ext/typeexpr: Now has an optional function convert which you can include in your hcl.EvalContext when evaluating expressions, allowing users to convert values to specific type constraints using the type constraint expression syntax. (#​330)
  • ext/typeexpr: A new cty capsule type typeexpr.TypeConstraintType which, when used as either a type constraint for a function parameter or as a type constraint for a hcldec attribute specification will cause the given expression to be interpreted as a type constraint expression rather than a value expression. (#​330)
  • ext/customdecode: An optional extension that allows overriding the static decoding behavior for expressions either in function arguments or hcldec attribute specifications. (#​330)
  • ext/customdecode: New cty capsuletypes customdecode.ExpressionType and customdecode.ExpressionClosureType which, when used as either a type constraint for a function parameter or as a type constraint for a hcldec attribute specification will cause the given expression (and, for the closure type, also the hcl.EvalContext it was evaluated in) to be captured for later analysis, rather than immediately evaluated. (#​330)

v2.2.0

Compare Source

Enhancements
  • hcldec: Attribute evaluation (as part of AttrSpec or BlockAttrsSpec) 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
  • hclsyntax: IndexExpr, SplatExpr, and RelativeTraversalExpr will 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)
  • hclwrite: Parser will no longer panic when the input includes index, splat, or relative traversal syntax. (#​328)

v2.1.0

Compare Source

Enhancements
  • gohcl: When decoding into a struct value with some fields already populated, those values will be retained if not explicitly overwritten in the given HCL body, with similar overriding/merging behavior as json.Unmarshal in the Go standard library.
  • hclwrite: New interface to set the expression for an attribute to be a raw token sequence, with no special processing. This has some caveats, so if you intend to use it please refer to the godoc comments. (#​320)
Bugs Fixed
  • hclwrite: The Body.Blocks method was returing the blocks in an indefined order, rather than preserving the order of declaration in the source input. (#​313)
  • hclwrite: The TokensForTraversal function (and thus in turn the Body.SetAttributeTraversal method) was not correctly handling index steps in traversals, and thus producing invalid results. (#​319)

v2.0.0

Compare 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:

import (
    hcl1 "github.com/hashicorp/hcl"
    hcl2 "github.com/hashicorp/hcl/v2"
)

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.0

Compare 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 Go
practices 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:

  1. The Protocol Buffer messages you provide to this API are from the
    google.golang.org/protobuf module. Take special care to audit any
    generated or checked-in Protocol Buffer message file assets. They may need
    to be regenerated.

  2. Your code should presumably use the google.golang.org/protobuf module for
    Protocol Buffers.

  3. This is a new major version of the module, so you will need to transition
    from module github.com/matttproud/golang_protobuf_extensions to
    github.com/matttproud/golang_protobuf_extensions/v2.

v1.0.4

Compare 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.3

Compare 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 Go
practices 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.2

Compare 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.2

Compare Source

What's Changed
Fixed bugs
New Contributors

Full Changelog: pelletier/go-toml@v2.2.1...v2.2.2

v2.2.1

Compare Source

What's Changed
Fixed bugs
New Contributors

Full Changelog: pelletier/go-toml@v2.2.0...v2.2.1

v2.2.0

Compare Source

What's Changed

What's new
Fixed bugs
Documentation
Other changes

New Contributors

Full Changelog: pelletier/go-toml@v2.1.1...v2.2.0

v2.1.1

Compare Source

What's Changed

Fixed bugs

New Contributors

Full Changelog: pelletier/go-toml@v2.1.0...v2.1.1

v2.1.0

Compare Source

This new minor release brings back the commented struct field tag from go-toml v1. It makes it easier to generate default or example configuration files. For instance:

type TLS struct {
	Cipher  string `toml:"cipher"`
	Version string `toml:"version"`
}
type Config struct {
	Host string `toml:"host" comment:"Host IP to connect to."`
	Port int    `toml:"port" comment:"Port of the remote server."`
	Tls  TLS    `toml:"TLS,commented" comment:"Encryption parameters (optional)"`
}
example := Config{
	Host: "127.0.0.1",
	Port: 4242,
	Tls: TLS{
		Cipher:  "AEAD-AES128-GCM-SHA256",
		Version: "TLS 1.3",
	},
}
out, err := toml.Marshal(example)

generates this TOML document:

### Host IP to connect to.
host = '127.0.0.1'

### Port of the remote server.
port = 4242

### Encryption parameters (optional)
### [TLS]

### cipher = 'AEAD-AES128-GCM-SHA256'
### version = 'TLS 1.3'

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:

toml: cannot store TOML string into a Go int

After:

1| [server]
2| path = "/my/path"
3| port = "bad"
 |        ~~~~~ cannot decode TOML string into struct field toml_test.Server.Port of type int

What's Changed

What's new
Fixed bugs
Other changes

New Contributors

Full Changelog: pelletier/go-toml@v2.0.9...v2.1.0

v2.0.9

Compare Source

What's Changed
Fixed bugs
Other changes
New Contributors

Full Changelog: pelletier/go-toml@v2.0.8...v2.0.9

v2.0.8

Compare 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.7

Compare Source

What's Changed

Fixed bugs
Documentation

New Contributors

Full Changelog: pelletier/go-toml@v2.0.6...v2.0.7

v2.0.6

Compare 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.5

Compare Source

What's Changed

Fixed bugs

Full Changelog: pelletier/go-toml@v2.0.4...v2.0.5

v2.0.4

Compare 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.3

Compare Source

What's Changed

Fixed bugs
Other changes

Full Changelog: pelletier/go-toml@v2.0.2...v2.0.3

[v2.0.2](https://togithub

Configuration

📅 Schedule: Branch creation - "before 4am 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.

👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

  • If you want to rebase/retry this PR, check this box

This PR has been generated by Mend Renovate. View repository job log here.

@renovate Renovate
Copy link
Contributor Author

renovate bot commented May 23, 2024 •
edited
Loading

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

  • any of the package files in this branch needs updating, or
  • the branch becomes conflicted, or
  • you click the rebase/retry checkbox if found above, or
  • you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: go.sum
Command failed: mod upgrade --mod-name=github.com/hashicorp/hcl -t=2
err: exit status 1: stderr: go: inconsistent vendoring in /tmp/renovate/repos/github/adrianriobo/qenvs:
	github.com/hashicorp/hcl/v2@v2.20.1: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
	github.com/santhosh-tekuri/jsonschema/v6@v6.0.1: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
	golang.org/x/mod@v0.14.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
	golang.org/x/tools@v0.17.0: is explicitly required in go.mod, but not marked as explicit in vendor/modules.txt
	github.com/hashicorp/hcl/v2@v2.19.1: is marked as explicit in vendor/modules.txt, but not explicitly required in go.mod

	To ignore the vendor directory, use -mod=readonly or -mod=mod.
	To sync the vendor directory, run:
		go mod vendor

could not load package
github.com/marwan-at-work/mod/major.Run
	/go/pkg/mod/github.com/marwan-at-work/mod@v0.7.1/major/major.go:47
main.upgrade
	/go/pkg/mod/github.com/marwan-at-work/mod@v0.7.1/cmd/mod/main.go:75
main.main.withExit.func1
	/go/pkg/mod/github.com/marwan-at-work/mod@v0.7.1/cmd/mod/main.go:88
github.com/urfave/cli/v2.(*Command).Run
	/go/pkg/mod/github.com/urfave/cli/v2@v2.25.1/command.go:274
github.com/urfave/cli/v2.(*Command).Run
	/go/pkg/mod/github.com/urfave/cli/v2@v2.25.1/command.go:267
github.com/urfave/cli/v2.(*App).RunContext
	/go/pkg/mod/github.com/urfave/cli/v2@v2.25.1/app.go:332
github.com/urfave/cli/v2.(*App).Run
	/go/pkg/mod/github.com/urfave/cli/v2@v2.25.1/app.go:309
main.main
	/go/pkg/mod/github.com/marwan-at-work/mod@v0.7.1/cmd/mod/main.go:71
runtime.main
	/opt/containerbase/tools/golang/1.22.4/src/runtime/proc.go:271
runtime.goexit
	/opt/containerbase/tools/golang/1.22.4/src/runtime/asm_amd64.s:1695

@renovate renovate bot force-pushed the renovate/go-major-updates branch 2 times, most recently from 08abdb9 to 3e83c32 Compare June 3, 2024 16:29
@renovate renovate bot force-pushed the renovate/go-major-updates branch from 3e83c32 to 1404fb7 Compare June 6, 2024 14:38
@renovate renovate bot force-pushed the renovate/go-major-updates branch from 1404fb7 to 53e342b Compare June 6, 2024 20:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Reviewers
No reviews
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging this pull request may close these issues.
1 participant
@adrianriobo