Brew fomulas SHA1 mismatch

Build has been revised. Each time CommandBox builds, the be brew file will be placed in the root of the artifacts folder (outside the version number folders). A corresponding stable brew file will be placed in the matching version folder. The S3 sync job takes the version from the parameterized build and copies that specific stable brew file to the root of the S3 folder. This way a previous CommandBox version can be synced to S3 as the "stable" version.

I have not modified the build process at all, but I did manually update the SHA-1 hashes tonight on S3 so the brew install would start working.

I think I know the issue with the SHA-1 hashes. Both the commandbox.rb and commandbox-be.rb files are re-created for each build. The URL in the stable version points to the download link for the stable version, yet the SHA-1 hashes are always the hashes for the bleeding edge version. As long as we sync S3 prior to bumping the stable version this is not an issue. The last CommandBox release, I bumped the stable version to 2.3 BEFORE syncing S3 so the commandbox.rb file has the link to the stable binary, but has the SHA-1 hash for the first 2.3 build.

We could change the build to has the current stable version, but better yet would be to store a separate commandbox.rb file for every version. The S3 sync can grab the correct one, plus people will then have the ability to install any previous version of CommandBox in Brew by hitting the brew file for that version.

??

Can you look into this?