Skip to content

fix: keep Homebrew callback setup with its declaration - #226

Merged
jacobcxdev merged 1 commit into
mainfrom
fix/preserve-cask-declaration-order
Oct 9, 2026
Merged

jacobcxdev merged 1 commit into
mainfrom
fix/preserve-cask-declaration-order

Conversation

@jacobcxdev

Copy link
Copy Markdown
Owner

Formatting a complete GoReleaser cask moved its uninstall declaration after callback setup. Loading the resulting package then failed because the uninstall artifact did not exist yet. Native package CI caught this before release tagging or publication.

Attach callback setup to the uninstall declaration with tap, so formatting preserves their evaluation order. Expand the native regression envelope to match GoReleaser's custom-block-first layout and full architecture/metadata stanzas. Keep the existing upgrade, reinstall and genuine uninstall assertions after saving and reloading Ruby metadata.

Validation: full downloaded cask formats cleanly and passes actual metadata save/reload and callback checks. Four native callback race tests, focused provenance race tests, build and vet pass. Rerun manual native package CI before release tagging.

@jacobcxdev jacobcxdev self-assigned this Oct 9, 2026
@jacobcxdev
jacobcxdev merged commit 2e7aaa8 into main Oct 9, 2026
5 of 7 checks passed
@jacobcxdev
jacobcxdev deleted the fix/preserve-cask-declaration-order branch October 9, 2026 13:07
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 participant