7865747b91
Update CI deps
...
Change-Id: I3bbaf32196b0cfe0f2ff7cb37a4ebfa65e6a44a9
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/92108
Commit-Queue: Rudolf Polzer <rpolzer@google.com >
Reviewed-by: Rudolf Polzer <rpolzer@google.com >
Presubmit-BoringSSL-Verified: Boringssl LUCI CQ <boringssl-scoped@luci-project-accounts.iam.gserviceaccount.com >
Auto-Submit: David Benjamin <davidben@google.com >
2026-04-09 00:32:57 -07:00
2e606c2dbf
Update other dependencies
...
While I'm here. Also document how to pick the Bazel version.
libc++'s __config_site needs another update. They keep coming up with
new settings we're required to set.
Change-Id: I49feedd75e5a38f07927aa1880916aadcd6bd91a
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/88947
Auto-Submit: David Benjamin <davidben@google.com >
Commit-Queue: Lily Chen <chlily@google.com >
Reviewed-by: Lily Chen <chlily@google.com >
2026-02-09 15:07:10 -08:00
2e2a00337a
Update all the Bazel things
...
It seems we need Bazel 7.6.2 or later to pick up a fix to the
apple_support package for the newest Xcode. Ideally we'd go to 7.7.0,
but CIPD seems not to have a package.
While I'm here, update other deps from BCR.
Change-Id: I30c339eda4aab22beed11d0acf1094dc5e16e4c9
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/83947
Commit-Queue: David Benjamin <davidben@google.com >
Reviewed-by: Lily Chen <chlily@google.com >
Auto-Submit: David Benjamin <davidben@google.com >
Commit-Queue: Lily Chen <chlily@google.com >
2025-11-10 12:06:04 -08:00
b78bfd7153
Update dependencies
...
Notably Go and rules_cc, but also pick up the rest while I'm here.
Updating libc++ once again required reworking the config. They seem to
change it every couple of weeks.
Bug: 396087264
Change-Id: Ied0f6fa11cd8c34fe9f0f87e63fd6283a699a22c
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/76167
Auto-Submit: David Benjamin <davidben@google.com >
Reviewed-by: Bob Beck <bbe@google.com >
Commit-Queue: Bob Beck <bbe@google.com >
2025-02-13 09:45:44 -08:00
059585c8da
Update tools and add a .bazelversion
...
So that MODULE.bazel.lock is actually checked to be up-to-date, we
should run with --lockfile_mode=error on CI. But since the lock file
format changes by Bazel version, that means we also need to pick a
particular Bazel version.
This matches the best practices documented here:
https://bazel.build/external/lockfile#best-practices
To update libc++, we now need to pull in a bit of LLVM libc. See
https://discourse.llvm.org/t/rfc-project-hand-in-hand-llvm-libc-libc-code-sharing/77701
Change-Id: I53b28067bab86d34be8c76625d6bedc23f0baeba
Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/73487
Commit-Queue: Adam Langley <agl@google.com >
Auto-Submit: David Benjamin <davidben@google.com >
Reviewed-by: Adam Langley <agl@google.com >
2024-11-28 00:01:55 +00:00
David Benjamin