Repository navigation
Ensure OSX aarch64 builds are added as assets to our releases #9397
Description
the M1 binaries don't appear to be making it onto our releases page:
https://repo1.maven.org/maven2/com/google/protobuf/protoc/3.19.2/
We've had reports from customers about confusion w.r.t our M1 support so we should add it there to clarify going forward.
Metadata
Metadata
Assignees
Labels
No labels
Activity
teejae commentedon Jan 12, 2022
FYI, I've attempted to download/use the osx-aarch64 binary from the maven repo linked in this issue, but noticed it isn't verified/signed, so won't work out of the box either.
Ref:
https://repo1.maven.org/maven2/com/google/protobuf/protoc/3.19.2/protoc-3.19.2-osx-aarch_64.exe
perezd commentedon Jan 12, 2022
Good catch, we'll get this working.
teejae commentedon Jan 13, 2022
@perezd thanks! looking forward to it. any likely ETA?
khaiwang commentedon Jan 17, 2022
osx-aarch64 still not on release page, any progress or substitution?
perezd commentedon Jan 18, 2022
https://repo1.maven.org/maven2/com/google/protobuf/protoc/3.19.2/protoc-3.19.2-osx-aarch_64.exe
This is the workaround, its unsigned so just go manually allow it in the sys prefs.
We are working on this, but I'd like to set expectations that it'll take more than 5 days. Signing infra for Google is complex and we need to get it spun up properly for these artifacts.
deannagarcia commentedon Jan 26, 2022
Adding for tracking that this issue will also include universal binary releases.
PolarBear292208 commentedon Jan 26, 2022
Any idea on an ETA? I'm trying to decide how much work to put into a workaround in our build process. I'm been inside the Plex, so I know how painful these types of things can be!
deannagarcia commentedon Jan 26, 2022
I would expect at least a month or two, but unfortunately I don't have a more precise estimate.
fabulias commentedon Feb 10, 2022
is there an advance related to this? I need protobuf 😢
PolarBear292208 commentedon Feb 11, 2022
M1 binaries of protobuf are available via homebrew, it's also pretty straightforward to build it from source.
6congyao commentedon Feb 16, 2022
Is there any progress to this? we need the osx-aarch_64 protoc for m1
deannagarcia commentedon Feb 16, 2022
Unfortunately it's still going to be a bit until we are able to publish signed and notarized binaries, but as mentioned you can use them from homebrew, build from source, or use the unsigned binaries and configure your machine to still run it.
yueban commentedon Mar 8, 2022
There has been a new release, version 3.20.0-rc1. But I can't find anything about osx-aarch_64 in the changelog.
deannagarcia commentedon Mar 16, 2022
I'm sorry, we still haven't been able to add it to the new release. The only options are the workarounds that I mentioned before, but I will keep updating when we have anything to report.
dragonsinth commentedon Apr 1, 2022
FYI: https://github.com/protocolbuffers/protobuf/releases 3.20.0 has an OSX aarch_64, but the linked tarball (https://github.com/protocolbuffers/protobuf/releases/download/v3.20.0/protoc-3.20.0-osx-aarch_64.zip) is actually wrong-- the embedded
protocbinary is x86_64.perezd commentedon Apr 1, 2022
Yes, we recently discovered that the aarch64 build was produced to create a placeholder, but hasn't actually had the work done to convert it. We're actively working on this within our release tooling and will provide updates soon.
deannagarcia commentedon May 12, 2022
The most recent release of protobuf (21.0) has an OSX aarch64 binary and an OSX universal binary!
Unfortunately, we have not been able sign it yet due to internal infrastructure problems. I will continue to keep you updated on that when there is progress.
abhijeet-shinde264 commentedon Jun 21, 2022
RobinClowers commentedon Mar 6, 2023
Any update here?
deannagarcia commentedon Mar 6, 2023
21 and 22 releases have an OSX aarch64 binary and an OSX universal binary. Signing is still in progress.
deannagarcia commentedon May 4, 2023
Our newest releases (22.4+ and 23.x) will now have signed OSX binaries, closing this issue.