Update gomod dependencies - #442
Conversation
|
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: red-hat-konflux-kflux-prd-rh02[bot] The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
1 similar comment
|
[APPROVALNOTIFIER] This PR is APPROVED Approval requirements bypassed by manually added approval. This pull-request has been approved by: red-hat-konflux-kflux-prd-rh02[bot] The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
66fa4cf to
cfa20e8
Compare
|
New changes are detected. LGTM label has been removed. |
3e2173c to
d9fadcb
Compare
d9fadcb to
20f827c
Compare
|
Important Review skippedBot user detected. To trigger a single review, invoke the ⚙️ Run configurationConfiguration used: Repository: openshift-online/coderabbit/.coderabbit.yaml Review profile: CHILL Plan: Advanced Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
Comment |
20f827c to
16aa91c
Compare
Signed-off-by: red-hat-konflux-kflux-prd-rh02 <190377777+red-hat-konflux-kflux-prd-rh02[bot]@users.noreply.github.com>
16aa91c to
d21c09b
Compare
|
@red-hat-konflux-kflux-prd-rh02[bot]: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
This PR contains the following updates:
v5.0.3→v5.2.0v1.4.3→v1.4.4v2.1.4+incompatible→v2.12.0v0.4.0→v0.5.0v2.38.0→v2.39.0v1.43.7→v1.47.0v1.32.38→v1.33.4v1.19.37→v1.20.4v1.20.62→v1.21.4v1.18.38→v1.20.0v1.4.38→v1.5.3v2.7.38→v2.8.3v1.4.39→v1.5.3v1.63.4→v1.68.0v1.36.7→v1.41.0v1.13.17→v1.13.19v1.12.15→v1.13.3v1.44.7→v1.49.0v1.5.7→v1.10.0v1.33.7→v1.38.0v1.38.7→v1.43.0v1.45.7→v1.50.0v1.45.7→v1.50.0v1.36.7→v1.41.0v1.27.9→v1.28.168fa937→6c9e17dv0.27.4→v0.28.0v2.7.1→v2.8.0v1.9.0→v1.10.1v1.10.0→v1.10.1v0.14.4→v0.15.0v1.0.0→v1.0.1v1.0.0→v1.0.2v0.29.1→v0.29.2v0.29.1→v0.29.2v0.29.1→v0.29.2v0.29.1→v0.29.2v0.29.1→v0.29.2v0.29.1→v0.29.2v0.29.1→v0.29.2v0.29.1→v0.29.2v0.29.1→v0.29.2v0.29.1→v0.29.2v0.29.1→v0.29.2v0.29.1→v0.29.2v2.13.1→v2.13.2d2031e3→241134d4d45320→6331bc6v5.10.0→v5.11.0v5.10.0→v5.11.0v0.0.28→v0.0.30v2.32.1→v2.32.2v0.0.0→v0.1.93c6b218→c1fd4253c6b218→c1fd425v0.6.2→v0.6.3v0.6.2→v0.6.3v0.70.1→v0.71.04b20672→f316d254b20672→f316d25v0.8.0→v0.9.0v0.10.0→v0.10.1e88cd73→85c1c22v0.40.0→v0.41.0v0.36.0→v0.37.0v0.34.0→v0.37.0v0.22.0→v0.23.0v0.47.0→v0.48.0v0.45.0→v0.46.0v0.41.0→v0.42.0v0.15.0→v0.16.0v0.49.0→v0.50.0v0.36.0→v0.37.0v0.36.1→v0.37.0v0.36.0→v0.37.0v0.35.1→v0.37.0v0.36.0→v0.37.0v0.36.0→v0.37.0v0.36.0→v0.37.0v0.36.1→v0.37.0v0.36.0→v0.37.0v0.36.3→v0.37.0v0.36.0→v0.37.0v0.36.1→v0.37.0v0.36.0→v0.37.0v0.11.0→v0.12.0v0.24.1→v0.25.0v0.24.1→v0.25.0v0.21.0→v0.22.02d32026→11ed52eWarning
Some dependencies could not be looked up. Check the warning logs for more information.
Release Notes
GaijinEntertainment/go-exhaustruct (dev.gaijin.team/go/exhaustruct/v5)
v5.2.0Compare Source
A minor release adding one option.
-allow-empty-blank-assignmentsexempts an empty struct literal the blank identifier receives, so a compile-time interface check such asvar _ Iface = T{}is no longer asked to fill fields nothing reads. The option is off by default; with it off, nothing changes.Added
-allow-empty-blank-assignments(#153).var _ Iface = T{}exists to prove thatTimplementsIface, and the analyzer required every field of a value that is discarded on the spot. The only allowance that reached the shape,-allow-empty-declarations, let every declared literal through with it. The new option keys on what receives the value: the blank identifier reads no field, so no field is required. It coversvar _ Iface = T{},var _ = T{}and_ = T{}, with&T{}and parentheses on either side, at package or function level.A value is matched to its name by position, so in the last line the literal bound to
sis still reported. A literal nested in the value (_ = []Server{{}}), a converted one (_ = Handler(Server{})) and a partial one stay reported: the blank identifier receives the slice, the conversion result, or a value with fields already named.The programmatic name is
Config.AllowEmptyBlankAssignments.Upgrading
CLI users reinstall and add the flag where they want it. Existing configuration is unchanged and no finding moves until the option is turned on.
golangci-lint users need a matching
allow-empty-blank-assignmentskey underexhaustruct_v5settings before they can turn it on. That key lives in the golangci-lint repository and is not part of this release.v5.1.0Compare Source
A release for Go 1.27 code. Literals that name promoted fields no longer crash the analyzer or get reported as incomplete,
-fixwrites source that compiles and keeps every field's optionality, and a set of resolution gaps that predate Go 1.27 are closed. The module now requires Go 1.26.Breaking changes
x/toolsv0.40.0 cannot read the export data Go 1.27 writes, so every run on that toolchain failed withinternal error: package "sync/atomic" without types. The v0.49.0 release that reads it needs go1.25; the floor goes to 1.26, which golangci-lint v2.13 already requires for this analyzer. Consumers on Go 1.24 or 1.25 cannot build this version.Fixes
makeslice: cap out of rangeon promoted keys (#168). Go 1.27 lets a composite literal name a promoted field in place of the embedded field carrying it (golang/go#77245). A literal naming more promoted fields than the struct has direct ones drove a capacity estimate negative and took golangci-lint down with it.Complete literals reported as incomplete (#161). Every promoted key counted as a key the struct did not have, so
A{b: "foo", a: 1, c: "f"}was reported as missing the embedded field it filled through. Promoted keys now resolve through the embedded field tree: a literal that names nothing under an embedded field is missing that field, one that fills it partly is missing the fields under it, each nameable from the same literal.The Go version of the file holding the literal decides whether promoted keys are possible, not the version the module declares, so a
//go:build go1.26file in a go1.27 module is read as the older one.Struct metadata cached by position. Export data drops the column and clamps lines past 64Ki to 1, so two types declared in one dependency file collapsed onto one cache entry and a literal was checked against another type's fields. The cache is keyed by the
go/typesobjects, which are unique per declaration, and each key is filled once across concurrently analysed packages.Pattern alternations that matched nothing. Go's regexp is leftmost-first, so
.*\.(Config|ConfigOption)committed toConfigagainstpkg.ConfigOption, stopped short of the end, and the pattern was silently ignored. Patterns now match leftmost-longest, compiled exactly as written.-fixoutput that did not compile or changed what is required. Migrating anexhaustruct:"optional"tag could comment out a single-line struct's closing brace, write a directive over one the author had already placed, or turn an enforced field optional. Tags are read and removed by the grammarreflect.StructTagreads, other entries in the tag survive, an interpreted-string tag migrates like a raw one, and the directive lands where the directive scanner resolves it to the field. Every deprecated tag is migrated, including one on a type the configuration excludes from checking.Directives in block comments and with trailing prose.
/*exhaustruct:optional*/now applies, which is the one form that annotates a field name inline, and prose after a directive is no longer reported as an unknown directive named"". A directive is matched to code by every line its comment covers, so a block comment reaches the code beside either end of it.Literal types that fell through. Map keys resolve against the key type rather than the value type,
[]PtrAlias{{...}}and[]PtrDefined{{...}}are checked, a literal of a type parameter is checked against the struct its constraint's terms share, and an alias to an anonymous struct carries its own directives.Directives above a statement reach the literals inside it, as they did in v4. A
//exhaustruct:ignoreabove a slice, map, call or return covers the literals nested in it, and redundant parentheses no longer end the walk.Diagnostics for a dependency's directives reach the package that owns the file, not the first importer to resolve a type from it.
Blank fields (
_) are never reported for a keyed literal, since no key can name them.Changed behaviour
A field no literal can write is required by nothing, whatever a directive or a pattern says about it: an unexported field of another package's struct, a promoted field a shallower one shadows, and a name two embedded fields promote at one depth.
A field marked
//exhaustruct:enforceunder an embedded field that the enclosing type left unrequired is still required. From Go 1.27 the enforced field itself is reported; below it the embedded field is, since that is the one key that reaches it.type P = *Configandtype Q *Configcarry their own type-level directives and patterns, and a literal eliding&Configunder one of them is reported as that type. A plain*Configstill answers asConfig.A field pattern (
Type#Field) is a rule for that field even when another pattern names the type holding it. Only a single pattern broad enough to match both names no field in particular.In either comment form the directive opens the comment, as
//go:builddoes:/* exhaustruct:optional */with a space is prose. A directive name written after a separator and a space, as in//exhaustruct:optional, enforce, is reported instead of being dropped in silence.Performance
Resolving a type opens each embedded struct once, at the depth it is first reached, where the walk previously cost one subtree per path through the embedding graph and twenty shared layers took 2.8 GB. A literal's keys are arranged once for the whole descent, instantiations of a generic type share their declaration's metadata, a constraint's interfaces are resolved once per walk, filled cache keys are answered under the read lock, and a file's directive scan builds only the lines a directive comment can share with code.
Internal
--issues-exit-code 0, so it could not fail. Lint now gates the build against a pinned golangci-lint, the suite runs under the race detector, and a dogfood job runs the analyzer built from the checkout over the checkout.IsAlias/IsDerivedresults nothing read, is gone.Upgrading
Toolchain 1.26 or newer, then reinstall. Configuration is unchanged. Findings move only where the analyzer was wrong before: promoted keys, blank fields, the newly resolved literal types, pattern alternations, use-site directive scope, and the enforced-under-optional case above.
4meepo/tagalign (github.com/4meepo/tagalign)
v1.4.4Compare Source
What's Changed
New Contributors
Full Changelog: 4meepo/tagalign@v1.4.3...v1.4.4
alecthomas/go-check-sumtype (github.com/alecthomas/go-check-sumtype)
v0.5.0Compare Source
Changelog
ab7a645update to 1.27, use analysis package's fact api. (#23)alicebob/miniredis (github.com/alicebob/miniredis/v2)
v2.39.0Compare Source
aws/aws-sdk-go-v2 (github.com/aws/aws-sdk-go-v2)
v1.47.0Compare Source
v1.46.0Compare Source
Module Highlights
github.com/aws/aws-sdk-go-v2/service/bedrockagentcore: v1.46.0github.com/aws/aws-sdk-go-v2/service/bedrockagentcorecontrol: v1.64.0github.com/aws/aws-sdk-go-v2/service/connect: v1.195.0github.com/aws/aws-sdk-go-v2/service/drs: v1.48.0github.com/aws/aws-sdk-go-v2/service/ecs: v1.95.0github.com/aws/aws-sdk-go-v2/service/eks: v1.97.0github.com/aws/aws-sdk-go-v2/service/elasticloadbalancingv2: v1.61.1github.com/aws/aws-sdk-go-v2/service/evs: v1.18.0github.com/aws/aws-sdk-go-v2/service/guardduty: v1.90.0github.com/aws/aws-sdk-go-v2/service/sfn: v1.48.1github.com/aws/aws-sdk-go-v2/service/socialmessaging: v1.18.0github.com/aws/aws-sdk-go-v2/service/transcribe: v1.63.0github.com/aws/aws-sdk-go-v2/service/transfer: v1.80.0v1.45.1Compare Source
General Highlights
Module Highlights
github.com/aws/aws-sdk-go-v2: v1.45.1github.com/aws/aws-sdk-go-v2/feature/s3/transfermanager: v0.4.1v1.45.0Compare Source
Module Highlights
github.com/aws/aws-sdk-go-v2/service/appintegrations: v1.44.0github.com/aws/aws-sdk-go-v2/service/bedrockagentcore: v1.45.0github.com/aws/aws-sdk-go-v2/service/ec2: v1.328.0github.com/aws/aws-sdk-go-v2/service/medialive: v1.108.0github.com/aws/aws-sdk-go-v2/service/mgn: v1.53.0github.com/aws/aws-sdk-go-v2/service/odb: v1.20.0github.com/aws/aws-sdk-go-v2/service/sagemaker: v1.273.0github.com/aws/aws-sdk-go-v2/service/sagemakerfeaturestoreruntime: v1.42.0v1.44.0Compare Source
General Highlights
Module Highlights
github.com/aws/aws-sdk-go-v2/service/accessanalyzer: v1.50.0github.com/aws/aws-sdk-go-v2/service/account: v1.33.0github.com/aws/aws-sdk-go-v2/service/acm: v1.42.0github.com/aws/aws-sdk-go-v2/service/acmpca: v1.48.0github.com/aws/aws-sdk-go-v2/service/aiops: v1.8.0github.com/aws/aws-sdk-go-v2/service/amp: v1.45.0github.com/aws/aws-sdk-go-v2/service/amplify: v1.40.0github.com/aws/aws-sdk-go-v2/service/amplifybackend: v1.34.0github.com/aws/aws-sdk-go-v2/service/amplifyuibuilder: v1.30.0github.com/aws/aws-sdk-go-v2/service/apigateway: v1.41.0github.com/aws/aws-sdk-go-v2/service/apigatewaymanagementapi: v1.31.0github.com/aws/aws-sdk-go-v2/service/apigatewayv2: v1.36.0github.com/aws/aws-sdk-go-v2/service/appconfig: v1.46.0github.com/aws/aws-sdk-go-v2/service/appconfigdata: v1.25.0github.com/aws/aws-sdk-go-v2/service/appfabric: [v1.18.0](service/appfabric/CHANGELOConfiguration
📅 Schedule: (in timezone UTC)
* 2-4 * * 1-5)🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
To execute skipped test pipelines write comment
/ok-to-test.Documentation
Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.