Skip to content
  1. Dec 13, 2024
  2. Dec 12, 2024
  3. Dec 11, 2024
  4. Dec 10, 2024
  5. Dec 09, 2024
  6. Dec 05, 2024
  7. Dec 04, 2024
  8. Dec 03, 2024
  9. Nov 28, 2024
  10. Nov 27, 2024
  11. Nov 25, 2024
    • Egor_P's avatar
      [stable2412] Backport: github/workflows: add ARM macos build binaries job (#6427) (#6596) · 9ab06167
      Egor_P authored
      # Description
      
      This PR adds the required changes to release `polkadot`,
      `polkadot-parachain` and `polkadot-omni-node` binaries built on Apple
      Sillicon macos.
      
      ## Integration
      
      This addresses requests from the community for such binaries: #802, and
      they should be part of the Github release page.
      
      ## Review Notes
      
      Test on paritytech-stg solely focused on macos binaries:
      https://github.com/paritytech-stg/polkadot-sdk/actions/runs/11824692766/job/32946793308,
      except the steps related to `pgpkms` (which need AWS credentials,
      missing from paritytech-stg). The binary names don't have a `darwin-arm`
      identifier, and conflict with the existing x86_64-linux binaries. I
      haven't tested building everything on `paritytech-stg` because the
      x86_64-linux builds run on `unbutu-latest-m` which isn't enabled on
      `pairtytech-stg` (and I haven't asked CI team to enable one), so testing
      how to go around naming conflicts should be covered next.
      
      ### TODO
      
      - [x] Test the workflow start to end (especially the last bits related
      to uploading the binaries on S3 and ensuring the previous binaries and
      the new ones coexist harmoniously on S3/action artifacts storage without
      naming conflicts) @EgorPopelyaev
      - [x] Publish the arm binaries on the Github release page - to clarify
      what's needed @iulianbarbu
      
       . Current practice is to manually publish the
      binaries built via `release-build-rc.yml` workflow, taken from S3. Would
      be great to have the binaries there in the first place before working on
      automating this, but I would also do it in a follow up PR.
      
      ### Follow ups
      
      - [ ] unify the binaries building under
      `release-30_publish_release_draft.yml` maybe?
      - [ ] automate binary artifacts upload to S3 in
      `release-30_publish_release_draft.yml`
      
      Signed-off-by: default avatarIulian Barbu <[email protected]>
      Co-authored-by: default avatarIulian Barbu <[email protected]>
      9ab06167
  12. Nov 20, 2024
  13. Nov 19, 2024