| commit | 53935217e69dd5bb98fb83e2895cc8cef26ad4af | [log] [tgz] |
|---|---|---|
| author | David Benjamin <davidben@google.com> | Tue Jul 01 13:37:35 2025 -0400 |
| committer | David Benjamin <davidben@google.com> | Mon Jul 07 14:19:33 2025 -0700 |
| tree | ad049fc58c672565d6df2477eaabfae9e05c2fc5 | |
| parent | 09f7078f953362d5c5afdd224118845327b60fb4 [diff] |
Deprecate the chromium-stable-with-bazel branch We haven't updated this branch for six months. I believe users have moved off of it by now. Historically, this branch pointed to, though lagged behind, the revision of BoringSSL that the current latest stable release of Chromium used. It was used by projects that wanted some slower-moving branch to follow than `HEAD`. BoringSSL now tags periodic releases that can be used instead. See the tags of the form `0.YYYYMMDD.N`. Change-Id: I4d1090f68919f7a1f8539ed26ee55b55783206ce Reviewed-on: https://boringssl-review.googlesource.com/c/boringssl/+/80108 Reviewed-by: Adam Langley <agl@google.com>
The chromium-stable-with-bazel branch is no longer being updated. Historically, this branch pointed to, though lagged behind, the revision of BoringSSL that the current latest stable release of Chromium used. It was used by projects that wanted some slower-moving branch to follow than HEAD.
BoringSSL now tags periodic releases that can be used instead. See the tags of the form 0.YYYYMMDD.N. These releases contain Bazel builds.
