pulumi
Reconsider available versions page in lieu of GitHub Releases
The Available Versions page provides only a subset of the information GitHub releases contain. As an example:
Compare to the GitHub Releases page, which since 3.0 has contained release notes, artifacts, checksums, and in future releases may additionally contain signature bundles (see: https://github.com/pulumi/pulumi/pull/11310).
We could either:
- Replace references to this page and its content with a pointer to https://github.com/pulumi/pulumi/releases. This would be in line with pulumi/pulumi#11325.
- Replace entries on this page with links to the tagged GitHub Releases
In the former case, it may make sense to maintain a history of pre-3.0 releases.
Replace entries on this page with links to the tagged GitHub Releases
I might have a slight preference for this one -- if only because it can be a little tricky digging through GH for older releases. It also keeps folks on pulumi. I don't feel strongly, though.
I think this could co-exist with a solution for https://github.com/pulumi/pulumi/issues/11325 with the addition of a latest tag. The docs can point to the latest release on GH, and that tag is bumped with each release. So the end result might be a table like
| Version | Date | Downloads |
|---|---|---|
| latest | xx | link to gh/releases/latest |
| 3.1 | xx | link to gh/releases/3.1 |
| ... | ||
| 2.x | xx | link to legacy get.pulumi.com |
(Or maybe we hide the latest column from the UI.)
Regardless of whether we keep the page or point to GitHub, we need to consider how our tools parse the underlying versions.json. The exist
- https://github.com/pulumi/actions/blob/06bc93fb6890a1d5bc8e4fab9a2354389011666b/src/libs/libs/get-version.ts#L22
- https://github.com/pulumi/setup-pulumi/blob/25745c3a35dd9b0db6b3b12d5fdde27cf84716ff/src/lib/get-version.ts#L24
I think an entry like
{
"version": "latest",
"date": "...",
"downloads": {
"linux-x64": "https://get.pulumi.com/releases/sdk/pulumi-latest-linux-x64.tar.gz",
...
},
"checksums": "https://get.pulumi.com/releases/sdk/pulumi-latest-checksums.txt",
"latest": true
},
would be backward-compatible with the existing page, while allowing tools to actually grab the latest release without being hindered by the docs publishing delay.
@AaronFriel im assuming you dont need a triage on this, so i dropped the label. pls let me know if you do, thank you!
Also noting here that the checksums for the Windows MSI package were added to the pulumi/pulumi-winget repository, not the core pulumi/pulumi one:
https://github.com/pulumi/pulumi-winget/releases
And with the work starting to sign our artifacts, this will lead to more metadata with each release:
https://github.com/pulumi/pulumi/pull/11310
