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
Chocolatey is listed as an official recommended method of installing Bruno. My company makes extensive use of Chocolatey scripts to manage the installation of software within our development department. The team now wants to evaluate moving away from Postman to Bruno.
When I went to test out the solution, I discovered that it was still installing a v1 binary, and that the auto-update feature doesn't bring the binary up to the latest v2+ version. This will block my company from adopting the software.
Investigating the choco side, I found that there were two submissions of v2 packages that had some fixes requested by the repo mods. It also appears that the package maintainer decided to apply those fixes to the 2nd submission and essentially abandoned the first submission. Thus, the mod is asking maintainer if the submission should be rejected:
TheCakeIsNaOH (reviewer)
on 03 May 2025 02:05:42 +00:00:
Should this version be rejected then?
To help speed along the process, I took on implementing all of the fixes requested by Choco for the 2.2.0 submission, as well as some other inconsistencies I noticed in the package, and submitted a PR to the bruno-chocolatey repo for your review. Assuming you approve it, you should be able to re-submit the exact same v2.2.0 version for final review.
I also updated all of the scripts I found so that future automated generation of the choco packages should contain these fixes, but I'm not able to fully test that out internally.
Uh oh!
There was an error while loading. Please reload this page.
Chocolatey is listed as an official recommended method of installing Bruno. My company makes extensive use of Chocolatey scripts to manage the installation of software within our development department. The team now wants to evaluate moving away from Postman to Bruno.
When I went to test out the solution, I discovered that it was still installing a v1 binary, and that the auto-update feature doesn't bring the binary up to the latest v2+ version. This will block my company from adopting the software.
Investigating the choco side, I found that there were two submissions of v2 packages that had some fixes requested by the repo mods. It also appears that the package maintainer decided to apply those fixes to the 2nd submission and essentially abandoned the first submission. Thus, the mod is asking maintainer if the submission should be rejected:
To help speed along the process, I took on implementing all of the fixes requested by Choco for the 2.2.0 submission, as well as some other inconsistencies I noticed in the package, and submitted a PR to the bruno-chocolatey repo for your review. Assuming you approve it, you should be able to re-submit the exact same v2.2.0 version for final review.
I also updated all of the scripts I found so that future automated generation of the choco packages should contain these fixes, but I'm not able to fully test that out internally.
I'm happy to make any other edits you request.
Link to PR details: usebruno/bruno-chocolatey#4 (comment)
JIRA
The text was updated successfully, but these errors were encountered: