You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
However, on maven central the stable version 6.41.0, and 6.42.0 is available as alpha that were published on 18-june-2024
Sample program
N/A
Log output
No response
Affected Resource(s)
No response
Output of pulumi about
CLI
Version 3.125.0
Go Version go1.22.5
Go Compiler gc
Host
OS darwin
Version 14.1
Arch arm64
Backend
Name Gigis-MacBook-Pro.local
URL s3://invisible-pulumi/aws?profile=ProdRW
User gigi
Organizations
Token type personal
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered:
I am sorry you are experiencing this. We were working through a key rotation initiated by the OSSRH repository transition, and several releases were indeed affected. The issue should be resolved in release https://github.com/pulumi/pulumi-aws/releases/tag/v6.45.2 and onwards. Is it acceptable for your use case to upgrade to 6.45.2?
t0yv0
added
p1
A bug severe enough to be the next item assigned to an engineer
and removed
awaiting-feedback
Blocked on input from the author
labels
Jul 25, 2024
Checking up on this today, it looks like the latest release didn't make it to Central either. We're troubleshooting the publishing process one more time, apologies for the disruption.
Describe what happened
The current latest release 22-july-2024 is 6.45.0. See https://github.com/pulumi/pulumi-aws/releases/tag/v6.45.0
However, on maven central the stable version 6.41.0, and 6.42.0 is available as alpha that were published on 18-june-2024
Sample program
N/A
Log output
No response
Affected Resource(s)
No response
Output of
pulumi about
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: