Seems like there are 2 issues:

• Non-executables were installed to "/usr/local/opt/swiftgen/bin".
  The offending files are:
  /usr/local/opt/swiftgen/bin/SwiftGen_SwiftGenCLI.bundle
• Unexpected universal binaries were found.
  The offending files are:
  /usr/local/Cellar/swiftgen/6.5.0/bin/swiftgen

The second one is kinda minor, it's weird that only 11 is complaining and not 11-arm64 or any of the other tests, because we now always build universal binaries. I can change our build script to only build the active architecture if needed.

The first one is a much bigger issue. This is how SPM binaries with resources work, we're not allowed to move those bundles to another place, it'll break the path of Bundle.module. And there's no way for us to check if Bundle.module will work, it'll just crash. Is there a way to silence this error in Homebrew?

it's weird that only 11 is complaining and not 11-arm64

ARM was being skipped, I've added the CI-force-arm label to correct that

The second one is kinda minor

We can try the following:

diff --git a/Formula/swiftgen.rb b/Formula/swiftgen.rb
index 7f200071516..d8ec22ade49 100644
--- a/Formula/swiftgen.rb
+++ b/Formula/swiftgen.rb
@@ -53,6 +53,9 @@ class Swiftgen < Formula
       "#{fixtures}/Generated/XCAssets/swift5/all.swift"                   => "xcassets.swift",
       "#{fixtures}/Generated/YAML/inline-swift5/all.swift"                => "yaml.swift",
     })
+
+    # Replace universal binaries with their native slices
+    deuniversalize_machos
   end
 
   test do

The first one is a much bigger issue. [...] Is there a way to silence this error in Homebrew?

Sorry, I'm honestly not sure. I'll let others chime in here.

Passing a flag to the build to build only native binaries would be preferable to using deuniversalize_machos. (Though this should work too.)

Re the location of SwiftGen_SwiftGenCLI.bundle: let's install everything into libexec and then just symlink what we want to expose to users into bin, lib, etc.

I've updated the formula to install in libexec as suggested.

For now I'm also using deuniversalize_machos. It isn't ideal, but I'm working on an update to our build scripts, should be implemented in the next SwiftGen version.

Nice the checks pass now 🎉

Any thoughts on the HEAD: Use branch: "stable" to specify the default branch issue mentioned in the first comment?

The default branch is stable, if that is not the branch that people should regard as the default branch when checking out the project I would recommend changing the default branch to develop.

The homebrew documentation mentions that head is for "the development cutting edge". Our stable branch only contains our releases, so head should point to develop.

My issue is that brew audit --strict --online swiftgen keeps complaining about this:

• HEAD: Use branch: "stable" to specify the default branch

Note: homebrew version info

Homebrew 3.2.14-51-g1909d89
Homebrew/homebrew-core (git revision 6e1f8e9; last commit 2021-10-04)
Homebrew/homebrew-cask (git revision 8a108c4; last commit 2021-10-04)

Nice the checks pass now 🎉

Any thoughts on the HEAD: Use branch: "stable" to specify the default branch issue mentioned in the first comment?

@nandahkrishna, thoughts here? (I think you implemented this audit -- apologies if I'm misremembering.)

From the git history for the formula, seems like @chenrui333 made the change to stable if that helps?

🤖 A scheduled task has triggered a merge.