Develop a `make` target to test for releasing pilot

[yungyuc]

The target should check for all runtime requirement packages for both headless (modmesh library without GUI) and GUI (Qt-enabled module code and pilot binary) modes.

The release-testing target will later be used in CI job for nightly packaging.

[iefiru]

I’d like to work on this issue. Could you assign it to me?

[iefiru]

I suggest extending contrib/bundle/bundle-with-homebrew.sh directly, so it can take an argument to run different release steps, and adding Makefile targets as entry points.

For example:

• contrib/bundle/bundle-with-homebrew.sh check
• contrib/bundle/bundle-with-homebrew.sh bundle
• contrib/bundle/bundle-with-homebrew.sh verify <path-to-dmg>

Proposed targets:

• make release-check
  • runs dependency/preflight checks for the macOS bundle environment
• make release
  • runs the macOS bundle script to produce the release artifact
• make release-testing
  • verifies the generated DMG/app artifact

The checks can cover required tools/packages such as Homebrew Python, CMake, pybind11, PySide6/shiboken, numpy, matplotlib, macdeployqt, codesign, and hdiutil.

The release test can verify the DMG by mounting it, checking app structure/signature, scanning for remaining Homebrew paths, and doing a runtime smoke test.

Does this direction sound reasonable, or are there other checks/workflows we should include for the macOS release process?

[yungyuc]

Sounds like a plan. At this stage, the release focuses on macOS bundle (release on Linux and then Windows will be in the future).