Skip to content

Conversation

Copy link
Contributor

Copilot AI commented Nov 26, 2025

Automated version bump to 1.15.0 only updated the version number, not the source or cargo hashes. The package was converted from binary to source builds in #04ec296 but the custom update script was removed, leaving nix-update unable to handle the dual-hash FOD pattern.

Changes

  • Fix hashes for v1.15.0

    • Source hash: sha256-i9BMq9PPwTGfhSAbDrck+B74g14U+8uYOmpfN5xeyis=
    • cargoHash: sha256-V6Vf6YzCNDwMlLFHICianR6f6zz7fEbm7+1Qeel3GDI=
  • Add update.py using RustPackageUpdater - ensures future automated updates correctly handle both fetchFromGitHub hash and cargoHash

updater = RustPackageUpdater(
    package="goose-cli",
    version_fetcher=lambda: fetch_github_latest_release("block", "goose"),
    repo_owner="block",
    repo_name="goose",
    tag_template="v{version}",
)
Original prompt

This section details on the original issue you should resolve

<issue_title>Goose CLI build breaks due to hash mismatch</issue_title>
<issue_description>Attempting to install goose-cli fails due to hash mismatch (amd64/linux). Hash value in goose-cli/package.nix which is currently set to sha256-MEFHVuTejAn1vwTwaxM7XEBSCuFAwLwjptIhKHR6cMM= which is the hash for tag 1.14.0 and not the desired 1.15.0. See nix flake prefetch output:

❯ nix flake prefetch github:block/goose/v1.15.0 --json | jq .hash -r
sha256-i9BMq9PPwTGfhSAbDrck+B74g14U+8uYOmpfN5xeyis=
❯ nix flake prefetch github:block/goose/v1.14.0 --json | jq .hash -r
sha256-MEFHVuTejAn1vwTwaxM7XEBSCuFAwLwjptIhKHR6cMM=

My guess is the change introduced in 04ec296 has led to hash no longer being automatically updated by goose-cli/update.sh script, as per 77c5ab6 (I can see update.sh is no more, hence the guessing).

I believe updating the hash will suffice, but I'm hesitant to open a PR to do that manually as I see there's a number of automated processes around package updates already.

</issue_description>

<agent_instructions>Fix the update script to patch the hash correctly, if patching gets to complex, move stuff to json, where updating is trivial. </agent_instructions>

Comments on the Issue (you are @copilot in this section)

@Mic92 We really need better tests for these complex FODs.

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

Copilot AI changed the title [WIP] Fix hash mismatch for goose-cli version 1.15.0 goose-cli: fix hash mismatch and add update script Nov 26, 2025
Copilot AI requested a review from Mic92 November 26, 2025 19:07
Copilot finished work on behalf of Mic92 November 26, 2025 19:07
@Mic92 Mic92 force-pushed the copilot/update-goose-cli-hash branch from 562e442 to ecfd85c Compare November 27, 2025 12:36
@Mic92 Mic92 marked this pull request as ready for review November 27, 2025 12:36
@Mic92 Mic92 enabled auto-merge November 27, 2025 12:37
@Mic92 Mic92 added this pull request to the merge queue Nov 27, 2025
Merged via the queue into main with commit 4fc6701 Nov 27, 2025
3 checks passed
@Mic92 Mic92 deleted the copilot/update-goose-cli-hash branch November 27, 2025 13:14
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.

Goose CLI build breaks due to hash mismatch

2 participants