Closed qwerty287 closed 1 week ago
Worth inspecting the renovate logs? See also the note in the dependency dashboard
DEBUG: Go module: codeberg.org/mvdkleijn/forgejo-sdk/forgejo lookup import url https://codeberg.org/mvdkleijn/forgejo-sdk.git
DEBUG: Found no satisfying versions with 'loose' versioning
DEBUG: Go lookup source url _ for module codeberg.org/mvdkleijn/forgejo-sdk/forgejo
DEBUG: Go module: codeberg.org/mvdkleijn/forgejo-sdk/forgejo lookup import url https://codeberg.org/mvdkleijn/forgejo-sdk.git
DEBUG: Could not determine new digest for update.
{
"packageName": "codeberg.org/mvdkleijn/forgejo-sdk/forgejo"
"currentValue": "v0.0.0-20240607215151-168c988b82c1"
"datasource": "go"
"newValue": "v1.1.0"
"bucket": "major"
}
Does not say something new…
And has somebody an idea why mysql tests time out?
either rerun when less resources are used or we have to deploy agents on VMs that have more ram ...
Digests are always a bit problematic. Maybe it works better now with a semver version!
Tearing down https://woodpecker-ci-woodpecker-pr-3840.surge.sh
It looks like renovate is unable to do this automatically?