Repository navigation
fix: clear quarantine with postflight_steps - #2
Merged
Merged
Conversation
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.
Homebrew now flags
postflightblocks (Cask/InstallSteps):brew stylefails in this repo's CI, andbrew installprints a deprecation warning asking users to report it. This replaces the block with the structuredpostflight_stepsform, which runs the samexattrquarantine removal on macOS.Checked in a throwaway Homebrew prefix:
brew stylereports no offenses,brew installprints no deprecation warning, the installed binary carries nocom.apple.quarantine, andpgedge versionruns (0.5.0-beta.3).The next pgedge-cli release regenerates this file from its goreleaser config, which cannot yet emit this form; that is tracked in pgEdge/pgedge-cli#40.