-
Notifications
You must be signed in to change notification settings - Fork 58
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
chore: package released binaries by architecture
Previously when we performed a release, we would do a Github Release for each binary in a particular selection. Now, the approach is to have a single Github Release for all the binaries. The assets for the single release will be a collection of zip files containing all nine binaries for each target architecture. The new release process stipulates that each package name should contain `YYYY.MM.X.Y`, where `X` is the number of the current release cycle, and `Y` is a counter within the cycle, which will be incremented for each RC build that is required. To support these requirements, a `package-arch-artifacts` target is added. It produces packages in the form, e.g., `2024.07.1.1.autonomi.aarch64-unknown-linux-musl.zip`. The release cycle numbers are provided from a new file at the root of the repository. Those numbers should be updated or reset in a release commit. The new process retains the upload of individual binaries to S3, so those packaging and upload targets are retained, but they are renamed to `package-bin` and `upload-packaged-bin-to-s3`, to distinguish them from the architecture packages. The `upload-github-release-assets` target is completely removed because it was uploading the individual binaries to their respective Github Releases, which is no longer relevant. The release workflow will be updated accordingly, but not in this commit. For testing the new targets, this commit only updates the simpler 'build and package release artifacts' workflow; a subsequent commit will update the full release workflow.
- Loading branch information
Showing
4 changed files
with
132 additions
and
107 deletions.
There are no files selected for viewing
This file contains 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
This file contains 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
This file contains 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
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,10 @@ | ||
# The release-cycle is the cycle within the current month. It will be 1 or 2. It is set at the | ||
# beginning of the cycle. | ||
# | ||
# The release-cycle-counter is initially set to 1 at the beginning of each cycle, and during the | ||
# cycle, it will be incremented for each RC build. | ||
# | ||
# Both of these numbers are used in the packaged version number, which is a collective version | ||
# number for all the released binaries. | ||
release-cycle: 1 | ||
release-cycle-counter: 1 |