Aws Machine Image Datasource no longer updating

[michael-graves-dojo]

What would you like help with?

None

How are you running Renovate?

Self-hosted

If you're self-hosting Renovate, tell us which platform (GitHub, GitLab, etc) and which version of Renovate.

GitHub v40.1.12

Please tell us more about your question or problem

The action worked the first time around but is not working in subsequent runs. Am now getting this warning on every run "Unexpected downgrade detected" and no PR is being created to update the AMI even though a new version is available and seems to get detected (see debug logs below)

Original terraform file (when update worked)

# amiFilter=[{"Name":"owner-id","Values":["591542846629"]},{"Name":"name","Values":["amzn2-ami-ecs-hvm-2.0.*-arm64-ebs"]},{"region":"us-east-1"}]
# currentImageName=amzn2-ami-ecs-hvm-2.0.20240604-arm64-ebs
image_id = "ami-007fe6f100765dc49",

Terraform file after it was updated from the initial renovate action (update no longer works)

# amiFilter=[{"Name":"owner-id","Values":["591542846629"]},{"Name":"name","Values":["amzn2-ami-ecs-hvm-2.0.*-arm64-ebs"]},{"region":"us-east-1"}]
# currentImageName=amzn2-ami-ecs-hvm-2.0.20240611-arm64-ebs
image_id = "ami-047cd859b5926d952",

Logs (if relevant)

DEBUG: Found no satisfying versions with 'aws-machine-image' versioning (repository=*)
 WARN: Unexpected downgrade detected: skipping (repository=*)
       "packageName": "[{\"Name\":\"owner-id\",\"Values\":[\"591542846629\"]},{\"Name\":\"name\",\"Values\":[\"amzn2-ami-ecs-hvm-2.0.*-arm64-ebs\"]},{\"region\":\"us-east-1\"}]",
       "currentValue": "ami-047cd859b5926d952",
       "compareValue": "ami-047cd859b5926d952",
       "currentVersion": undefined,
       "update": {
         "bucket": "non-major",
         "newVersion": "ami-0fb54a4ca8445b4df",
         "newValue": "ami-0fb54a4ca8445b4df",
         "newDigest": "amzn2-ami-ecs-hvm-2.0.20240625-arm64-ebs",
         "releaseTimestamp": "2024-06-26T00:38:15.000Z",
         "newMajor": 1,
         "newMinor": 0,
         "newPatch": 0,
         "updateType": "patch"
       },
       "allVersionsLength": 1,
       "filteredReleaseVersions": ["ami-0fb54a4ca8445b4df"]

[github-actions[bot]]

Hi there,

Get your discussion fixed faster by creating a minimal reproduction. This means a repository dedicated to reproducing this issue with the minimal dependencies and config possible.

Before we start working on your issue we need to know exactly what's causing the current behavior. A minimal reproduction helps us with this. Discussions without reproductions are less likely to be converted to Issues.

Please follow these steps:

1. Read our guide on creating a minimal reproduction.
2. Go to our minimal reproduction template repository.
3. Select the Use this template button to create a new repository based on the template.
4. Work on the minimal reproduction in your own repository.
5. Fill out the information in your repository's README.md.
6. Add the link to your reproduction to the first post of your Discussion. If you are not the original author, you can post a new comment with the link.

Good luck,

The Renovate team

[michael-graves-dojo]

This has started working again on the latest AMI with no changes made to renovate configs or the terraform files.

So going to close for now as it seems like it might have been a fluke with a specific AMI version