Publish Homebrew cask, add landing page, release from the changelog - #2
Merged
Merged
Conversation
Add a homebrew_casks section so each release updates Casks/pdfunlock.rb in fadeltd/homebrew-tap over SSH with a deploy key. The cask removes the quarantine attribute with postflight_steps, since the binary is not notarized. Add a static landing page in docs/ for GitHub Pages.
…o changelog Ignore tmp/ for scratch files.
Merging to main now cuts the next version from [Unreleased] in CHANGELOG.md (Breaking -> major, Added -> minor, otherwise patch), commits the dated section, tags it and dispatches Publish. Publish (the old tag-triggered release workflow) runs GoReleaser on that tag with the changelog section as the release notes. CI requires a changelog entry on PRs that change the tool and runs gofmt, vet, tests, build and goreleaser check.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Casks/pdfunlock.rbto fadeltd/homebrew-tap, so macOS users can runbrew install --cask fadeltd/tap/pdfunlock.HOMEBREW_TAP_DEPLOY_KEY, already configured). Prereleases are skipped.com.apple.quarantineafter install.postflight_stepsthroughcustom_block, because Homebrew 7 deprecates thepostflightblock GoReleaser'shooksgenerate. GoReleaser putscustom_blockfirst, sobrew stylereportsCask/StanzaOrder; this is cosmetic.release.ymlnow runs on merge tomain. It picks the next version from## [Unreleased]: Breaking → major, Added → minor, anything else → patch.Release vX.Y.Z [skip ci], pushes the tag, and dispatchespublish.yml.publish.ymlis the old tag-triggered workflow, now dispatch-only. It runs GoReleaser on the tag, with that version's changelog section as the release notes.GORELEASER_PREVIOUS_TAGexplicitly, because the existing tags aren't ancestors ofmain.scripts/release, a port of xiaomi-debloater's script with tests. It reads the current version from the newest changelog section.make release VERSION=…now pushes the tag and dispatches Publish, for hand-made prerelease tags.ci.yml):*.md,.github/,scripts/,Makefileandenv.sampleare exempt, and theskip-changeloglabel skips the check.goreleaser check.docs/for GitHub Pages at https://fadeltd.github.io/pdfunlock/..go-version.tmp/.Merging this releases v1.1.0, because
[Unreleased]has an### Addedsection.Testing
go test ./...passes (release script). actionlint andgoreleaser checkare clean.go run ./scripts/release -dry-runon the real changelog. It givesminor,1.0.1 -> 1.1.0, with the expected notes.v1.1.0;--skip=publishand the same notes and previous-tag handling as Publish;previous=v1.0.1 current=v1.1.0, and the cask came out at 1.1.0.sha256for each OS and architecture.postflight_steps, the quarantine attribute is removed andpdfunlock --versionruns.