Jamie Tanna 4086667eba fix(manager/gomod): allow modules with an older go directive (#47317) ...

* fix(manager/gomod): allow modules with an older `go` directive

As noted in #47313, when using `constraintsFiltering=strict`, any Go
modules which declare a `go` directive on an /older/ minor version than
the repository's are filtered out, even though they would not require
bumping the repository's `go` directive.

This seems to have been documented as the intent in
0e5e384237 - hence the test added to note
the behaviour - but this leads to us not updating versions we should do.

We can instead convert it into the range `<=1.26.x`, which allows the
same or older minor versions, and continues to filter out newer ones,
which applies with the `semver-coerced` versioning scheme.

Co-authored-by: Claude Opus 5.5 <jamie.tanna+amp@mend.io>

* fixup! fix(manager/gomod): allow modules with an older `go` directive

---------

Co-authored-by: Claude Opus 5.5 <jamie.tanna+amp@mend.io>

2026-10-23 10:14:22 +00:00

..

datasource

fix(manager/gomod): allow modules with an older go directive (#47317)

2026-10-23 10:14:22 +00:00

manager

fix(manager/gomod): allow modules with an older go directive (#47317)

2026-10-23 10:14:22 +00:00

platform

fix(platform/azure): apply the repo's azureWorkItemType (#47158)

2026-10-19 12:32:56 +00:00

versioning

refactor(versioning/gomod): parse the commit of pseudo-versions (#47097)

2026-10-16 09:52:08 +00:00