Prevent java template from using 6.0 alpha versions

[mnlumi]

No description provided.

[mnlumi]

Related to pulumi/pulumi-aws#2658

[mnlumi]

The latest version of aws is 5.4. I've validated that this works as expected.

Do you want to perform this update? details
+ pulumi:pulumi:Stack: (create)
    [urn=urn:pulumi:dev::aws-java-2::pulumi:pulumi:Stack::aws-java-2-dev]
    + aws:s3/bucket:Bucket: (create)
        [urn=urn:pulumi:dev::aws-java-2::aws:s3/bucket:Bucket::my-bucket]
        [provider=urn:pulumi:dev::aws-java-2::pulumi:providers:aws::default_5_4_0::......]
        acl         : "private"
        bucket      : "my-bucket-f3a10fd"
        forceDestroy: false
    --outputs:--
    bucketName: "my-bucket-f3a10fd"

[mnlumi]

Alpha versions are considered less than the numeric version so even with <version>[5.0.0,6.0.0]</version>, the 6.0.0-alpha will be selected.

@cnunciato This should be looked at for all java programs to avoid pulling in alpha releases prior to the next major release.

[t0yv0]

This look's good 🙏

It doesn't shield users from versions such as https://repo1.maven.org/maven2/com/pulumi/aws/5.43.0-alpha.1689671883+f787a47a/ but those are not currently known to be affected.

[mnlumi]

This look's good 🙏

It doesn't shield users from versions such as https://repo1.maven.org/maven2/com/pulumi/aws/5.43.0-alpha.1689671883+f787a47a/ but those are not currently known to be affected.

True, I could set it to 5.43 explicitly, but didn't want to eliminate 5.5* from being used in case there was some other emergent release. My goal is to prevent the next major version's alpha releases from being consumed.

[mnlumi]

@cnunciato I'm not sure why this test is failing. Could you help take a look please?

  error: error: no changes were expected but changes were proposed

Also, note the scaleway update due to failing tests around go being 1.18 max expected but 1.20 in the actual program.

[cnunciato]

@mnlumi It looks like the aws-java test passed for your first commit, but started failing with the second. From the output, it looks like follow-up updates to the templated program produce a diff, which they shouldn't:

The checkpoint suggests the version that failed (producing the diff) was 5.4.0.

[ringods]

I would use 5.99. Current AWS provider release is already at 5.42.0.

[mnlumi]

Thanks @ringods for catching this!