Skip to content

Comments

Bump boringssl from 0.20250114.0 to 0.20260211.0#3873

Open
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/bazel/boringssl-0.20260211.0
Open

Bump boringssl from 0.20250114.0 to 0.20260211.0#3873
dependabot[bot] wants to merge 1 commit intomainfrom
dependabot/bazel/boringssl-0.20260211.0

Conversation

@dependabot
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Feb 21, 2026

Bumps boringssl from 0.20250114.0 to 0.20260211.0.

Release notes

Sourced from boringssl's releases.

0.20260211.0

Full Changelog: google/boringssl@0.20260204.0...0.20260211.0

0.20260204.0

Full Changelog: google/boringssl@0.20251124.0...0.20260204.0

0.20251124.0

Full Changelog: google/boringssl@0.20251110.0...0.20251124.0

0.20251110.0

No release notes provided.

0.20251002.0

No release notes provided.

0.20250818.0

No release notes provided.

0.20250807.0

No release notes provided.

0.20250701.0

No release notes provided.

0.20250514.0

No release notes provided.

0.20250415.0

BoringSSL usage typically follows a “live at head” model. Projects pin to whatever the current latest of BoringSSL is at the time of update, and regularly update it to pick up new changes.

Some systems cannot consume git revisions and expect git tags. BoringSSL tags periodic snapshots as “releases”, to meet the needs of those systems. These versions do not represent any kind of stability or development milestone. BoringSSL does not branch at these releases and will not cherry-pick bugfixes to them. Unless there is a technical constraint to use one of these revisions, projects should simply use the latest untagged revision when updating.

0.20250311.0

BoringSSL usage typically follows a “live at head” model. Projects pin to whatever the current latest of BoringSSL is at the time of update, and regularly update it to pick up new changes.

Some systems cannot consume git revisions and expect git tags. BoringSSL tags periodic snapshots as “releases”, to meet the needs of those systems. These versions do not represent any kind of stability or development milestone. BoringSSL does not branch at these releases and will not cherry-pick bugfixes to them. Unless there is a technical constraint to use one of these revisions, projects should simply use the latest untagged revision when updating.

0.20250212.0

BoringSSL usage typically follows a “live at head” model. Projects pin to whatever the current latest of BoringSSL is at the time of update, and regularly update it to pick up new changes.

Some systems cannot consume git revisions and expect git tags. BoringSSL tags periodic snapshots as “releases”, to meet the needs of those systems. These versions do not represent any kind of stability or development milestone. BoringSSL does not branch at these releases and will not cherry-pick bugfixes to them. Unless there is a technical constraint to use one of these revisions, projects should simply use the latest untagged revision when updating.

Commits
  • 617634b Bump BCR
  • c8bf4de Migrate X509Impl to RefCounted.
  • 738fe6a Migrate X509Store to RefCounted.
  • 4289ec2 Migrate RSAImpl to RefCounted.
  • ae830b1 Migrate ECKey to RefCounted.
  • 03934c4 Fix up DECLARE_OPAQUE_STRUCT docs
  • 3bfa067 Migrate ECCustomGroup to RefCounted.
  • ec1c593 Migrate EVP_PKEY to RefCounted.
  • 3f7fc87 Also implement UpRef() for kAllowRefCountedUniquePtr types.
  • 1113222 Migrate DSA to RefCounted.
  • Additional commits viewable in compare view

Dependabot compatibility score

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Bumps [boringssl](https://github.com/google/boringssl) from 0.20250114.0 to 0.20260211.0.
- [Release notes](https://github.com/google/boringssl/releases)
- [Commits](google/boringssl@0.20250114.0...0.20260211.0)

---
updated-dependencies:
- dependency-name: boringssl
  dependency-version: 0.20260211.0
  dependency-type: direct:production
  update-type: version-update:semver-minor
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot dependabot bot added bazel Pull requests that update bazel code dependencies Pull requests that update a dependency file labels Feb 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bazel Pull requests that update bazel code dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants