Unable to deploy Greengrass V2 available component

Environment: Greengrass V2 Nucleus (2.9.1) running as Docker container.

We developed one aws.greengrass.generic component and have successfully published 4 versions (1.0.0, 1.0.1, 1.0.2 and 1.0.3). All three versions are published, displayed in Greengrass V2 console and artifacts correctly available in the S3 bucket.

[2022-11-26 17:32:54] INFO - Getting project configuration from gdk-config.json
[2022-11-26 17:32:54] INFO - Found component recipe file 'recipe.yaml' in the  project directory.
[2022-11-26 17:32:54] INFO - Found credentials in shared credentials file: ~/.aws/credentials
[2022-11-26 17:32:55] INFO - Using '1.0.3' as the next version of the component '<my-component>' to create.
[2022-11-26 17:32:55] INFO - Publishing the component '<my-component>' with the given project configuration.
[2022-11-26 17:32:55] INFO - Uploading the component built artifacts to s3 bucket.
[2022-11-26 17:32:55] INFO - Uploading component artifacts to S3 bucket: <my-bucket>. If this is your first time using this bucket, add the 's3:GetObject' permission to each core device's token exchange role to allow it to download the component artifacts. For more information, see https://docs.aws.amazon.com/greengrass/v2/developerguide/device-service-role.html.
[2022-11-26 17:32:56] INFO - Successfully created the artifacts bucket '<my-bucket>' in region 'us-east-1'
[2022-11-26 17:32:58] INFO - Updating the component recipe <my-component>-1.0.3.
[2022-11-26 17:32:58] INFO - Creating a new greengrass <my-component>-1.0.3
[2022-11-26 17:32:58] INFO - Created private version '1.0.3' of the component in the account.'<my-component>'.

However, we apparently can only deploy version 1.0.0 successfully. All other versions fail.

2022-11-26T20:19:01.427Z [INFO] (pool-2-thread-47) com.aws.greengrass.componentmanager.ComponentManager: prepare-package-start. {packageIdentifier=<my-component>-v1.0.0}

When we try to deploy ANY newer version (e.g. 1.0.3), we always get this error:

2022-11-26T20:36:10.987Z [ERROR] (pool-2-thread-51) com.aws.greengrass.deployment.DeploymentService: Error occurred while processing deployment. {deploymentId=3a4cb705-db16-4b5b-94b4-30e53f0edc9b, serviceName=DeploymentService, currentState=RUNNING}
java.util.concurrent.ExecutionException: com.aws.greengrass.componentmanager.exceptions.NoAvailableComponentVersionException: No local or cloud component version satisfies the requirements Check whether the version constraints conflict and that the component exists in your AWS account with a version that matches the version constraints. If the version constraints conflict, revise deployments to resolve the conflict. Component <my-component> version constraints: thing/<thing-name> requires =1.0.3.
...
2022-11-26T20:36:20.733Z [ERROR] (pool-2-thread-9) com.aws.greengrass.deployment.DeploymentService: Deployment task failed with following errors. {DeploymentId=arn:aws:greengrass:us-east-1:<account-id>:configuration:thing/<my-thing>:5, detailed-deployment-status=FAILED_NO_STATE_CHANGE, deployment-error-types=[REQUEST_ERROR], GreengrassDeploymentId=3a4cb705-db16-4b5b-94b4-30e53f0edc9b, serviceName=DeploymentService, currentState=RUNNING, deployment-error-stack=[DEPLOYMENT_FAILURE, NO_AVAILABLE_COMPONENT_VERSION, COMPONENT_VERSION_REQUIREMENTS_NOT_MET]}
com.aws.greengrass.componentmanager.exceptions.NoAvailableComponentVersionException: No local or cloud component version satisfies the requirements Check whether the version constraints conflict and that the component exists in your AWS account with a version that matches the version constraints. If the version constraints conflict, revise deployments to resolve the conflict. Component <my-component> version constraints: thing/<my-thing> requires =1.0.3.
        at com.aws.greengrass.componentmanager.ComponentManager.negotiateVersionWithCloud(ComponentManager.java:229)
        at com.aws.greengrass.componentmanager.ComponentManager.resolveComponentVersion(ComponentManager.java:164)
        at com.aws.greengrass.componentmanager.DependencyResolver.lambda$resolveDependencies$2(DependencyResolver.java:125)
        at com.aws.greengrass.componentmanager.DependencyResolver.resolveComponentDependencies(DependencyResolver.java:221)
        at com.aws.greengrass.componentmanager.DependencyResolver.resolveDependencies(DependencyResolver.java:123)
        at com.aws.greengrass.deployment.DefaultDeploymentTask.lambda$call$2(DefaultDeploymentTask.java:125)

As stated, the component is available in Greengrass V2 console and artifacts correctly published in S3.