Skip to content

[1.132.0] Draft Release (redo -- update hash to reflect updated binaries)#87

Merged
DeeDeeG merged 1 commit into
mainfrom
release-1.132.0
May 18, 2026
Merged

[1.132.0] Draft Release (redo -- update hash to reflect updated binaries)#87
DeeDeeG merged 1 commit into
mainfrom
release-1.132.0

Conversation

@DeeDeeG

@DeeDeeG DeeDeeG commented May 18, 2026

Copy link
Copy Markdown
Member

Automated Draft of new Pulsar Chocolatey Release
Will close #86

See also #85

@DeeDeeG DeeDeeG left a comment

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This just updates the hash.

As such, LGTM.

SHA256 sum matches the latest one the GitHub.com UI and our own SHA256SUMS.txt show for Windows.Pulsar.Setup.1.132.0.exe at https://github.com/pulsar-edit/pulsar/releases/tag/v1.132.0.

sha256:95f8d86be13a858fe182857f26314e10c287a12f3a2c23467c2e439ceaa7f0e1


From the CI logs of this PR:

Downloading pulsar
from 'https://github.com/pulsar-edit/pulsar/releases/download/v1.132.0/Windows.Pulsar.Setup.1.132.0.exe'

[ . . . ]

Progress: 100% - Completed download of C:\Users\runneradmin\AppData\Local\Temp\chocolatey\pulsar\1.132.0\Windows.Pulsar.Setup.1.132.0.exe (174.69 MB).
Download of Windows.Pulsar.Setup.1.132.0.exe (174.69 MB) completed.
Hashes match.

"Hashes match" is a good thing!

As a sanity check, the output from the tests summary (CI run for this PR) looks correct (correct version string):

Pulsar 1.132.0

This is indicating the app installed and was functional enough to handle pulsar --version being run and output to the terminal.

@DeeDeeG DeeDeeG changed the title [1.132.0] Draft Release [1.132.0] Draft Release (redo -- update hash to reflect updated binaries) May 18, 2026
@Daeraxa

Daeraxa commented May 18, 2026

Copy link
Copy Markdown
Member

I can't give a hard approve on this repo but if we think this will work to republish then go for it, I couldn't find any obvious docs on updating stuff like this if the package exists.

@DeeDeeG

DeeDeeG commented May 18, 2026

Copy link
Copy Markdown
Member Author

Thanks for the approval, merging, will attempt to publish again as 1.132.0. Frankly, going to find out if that is disallowed by Chocolatey or not. If it hadn't been through approval already I'm sure it would work, since we've had to in the past.

@DeeDeeG
DeeDeeG merged commit fe6f0ee into main May 18, 2026
1 check passed
@DeeDeeG

DeeDeeG commented May 18, 2026

Copy link
Copy Markdown
Member Author

Update: It did not allow re-publishing as the same version.

Publishing D:\a\pulsar-chocolatey\pulsar-chocolatey\pulsar\pulsar.1.132.0.nupkg to Chocolatey
Chocolatey v2.7.1
Attempting to push pulsar.1.132.0.nupkg to https://push.chocolatey.org/
An error has occurred. It's possible the package version already exists on the repository or a nuspec element is invalid. See error below...
Response status code does not indicate success: 409 (Conflict).

From: https://github.com/pulsar-edit/pulsar-chocolatey/actions/runs/26048398334/job/76578521240

We will likely have to do a patch release.

I'll move further discussion to #85.

@DeeDeeG DeeDeeG mentioned this pull request May 18, 2026
5 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1.132.0 (redo -- update hash to reflect updated binaries)

2 participants