replicate
Upload aarch64 cog binary release
- aarch64 is actually exactly the same as arm64
- Unfortunately because of uname sometimes the architecture is reported as aarch64
- This how most people download our binaries, so if we don’t provide this path we end up not supporting this platform as well as we should.
- Fixes: https://github.com/replicate/cog/issues/1828
As an aside, I'm a bit unsure how to test this because it lives in the release deployment.
@8W9aG Nice! We're several versions behind on goreleaser, using v4 instead of v6 (#1766) and using v0 configuration instead of v2. Is this something we could fix instead by upgrading to newer version of goreleaser software or configuration?
@8W9aG Nice! We're several versions behind on goreleaser, using v4 instead of v6 (#1766) and using v0 configuration instead of v2. Is this something we could fix instead by upgrading to newer version of goreleaser software or configuration?
Certainly I can give that a go, would you happen to have any ideas on how to test it though? Perhaps its just a more involved release next time where we watch it in realtime to make sure it executes as expected.
@8W9aG goreleaser should be runnable locally, so you could tweak the settings until it gives you what you need. Once you have a configuration that works for you, we can test out the integration with a new 0.9.x patch release (we need to do this anyway to get a new Python library package published)