9 Commits (927e7407b4644abf2d26d3c99fca6dc194db290d)

Author	SHA1	Message	Date
renovate[bot]	286227c6b8	ci(deps): Update actions/upload-artifact action to v4.6.0	1 month ago
renovate[bot]	6b37d10772	ci(deps): Update actions/upload-artifact action to v4.5.0	2 months ago
renovate[bot]	36de47cdbc	ci(deps): Update actions/upload-artifact action to v4.4.3	4 months ago
renovate[bot]	d2d707a0b7	ci(deps): Update actions/upload-artifact action to v4.4.1	4 months ago
Robert Dailey	d164662d2c	ci: Upgrade download and upload artifact actions to v4	6 months ago
Robert Dailey	9329e0175f	ci: Add job to test artifact downloads ... Downgrade the artifact upload/download actions to v3 since none of the v4 versions seem to address the "Not a valid zip file" issue. Modified the codesign job to additionally run on PRs, so that when Renovate upgrades the upload/download artifacts, we can tell from the PR if the ZIP file issue is fixed. For more info, see: - https://github.com/actions/download-artifact/issues/328 - https://github.com/docker/build-push-action/issues/1167	8 months ago
Robert Dailey	b5523bdc42	ci: Fix error while re-uploading signed artifacts ... The Apple Signing step grabs an existing artifact, signs the binaries, and then re-uploads the artifact, replacing the original one. The upgrade to v4 of the `actions/upload-artifact` action broke this behavior due to a breaking change documented in [the release notes][1]: > Due to how Artifacts are created in this new version, it is no longer > possible to upload to the same named Artifact multiple times. You must > either split the uploads into multiple Artifacts with different names, > or only upload once. Otherwise you will encounter an error. The fix is to use the `overwrite: true` setting to force the old behavior of replacing the previous (unsigned) artifact. [1]: https://github.com/actions/upload-artifact/blob/main/README.md#breaking-changes	12 months ago
Robert Dailey	16742d68ff	ci: Upgrade Node v16 actions to v20	12 months ago
Robert Dailey	e1f1872cb7	fix: Correct executable bit permissions on binary releases ... Due to [an issue][1] with the `actions/upload-artifact` action, when binaries are uploaded they lose permission bits and `xattr` properties. Composite actions `upload-tar` and `download-tar` have been added that tarball the artifacts before uploading them to retain those properties. [1]: https://github.com/actions/upload-artifact/issues/38	2 years ago