| commit | c6077da0da30ff0a31c3f06e456652de2a670e96 | [log] [tgz] |
|---|---|---|
| author | DEPS Autoroller <dart-autoroll@skia-public.iam.gserviceaccount.com> | Tue Feb 18 21:24:48 2025 -0800 |
| committer | Commit Queue <dart-scoped@luci-project-accounts.iam.gserviceaccount.com> | Tue Feb 18 21:24:48 2025 -0800 |
| tree | e08b1167b9c81c397c89c78ee216630eee480eb6 | |
| parent | f0561dcdb9eeea1218d1a12ec2def86dda57de98 [diff] |
Roll BoringSSL from bef0b8b4424d to 8c6b0c04f19f (15 revisions) https://boringssl.googlesource.com/boringssl.git/+log/bef0b8b4424d..8c6b0c04f19f 2025-02-14 davidben@google.com runner: Switch back to filippo.io/mlkem768 for now 2025-02-13 davidben@google.com runner: Include the name of the message we failed to parse 2025-02-13 davidben@google.com runnner: Switch to Go's crypto/ecdh module 2025-02-13 davidben@google.com Switch to Go standard library functions where available 2025-02-13 davidben@google.com Fix include spelling in spake2plus.cc 2025-02-13 davidben@google.com Revert "Speed up sha512 on x86" and update comments 2025-02-13 filippo@golang.org Add ".git" hint to Go module name 2025-02-13 davidben@google.com Bump version for BCR 2025-02-13 davidben@google.com Clarify that sigalg configuration does not impact TLS 1.0/1.1 2025-02-13 davidben@google.com Update dependencies 2025-02-12 bbe@google.com Remove ocsp_revocation_status.h and ocsp_verify_result.h 2025-02-11 davidben@google.com Fix up ClientHello parser errors 2025-02-11 davidben@google.com Add SSL_parse_client_hello 2025-02-11 bbe@google.com use public header instead of internal for ocsp 2025-02-11 bbe@google.com Make CheckOCSP public api If this roll has caused a breakage, revert this CL and stop the roller using the controls here: https://autoroll.skia.org/r/boringssl-dart-sdk Please CC dart-engprod@google.com,dart-vm-gardener@grotations.appspotmail.com,dart-vm-team@google.com on the revert to ensure that a human is aware of the problem. To file a bug in BoringSSL: https://crbug.com/boringssl/new To file a bug in Dart SDK: https://github.com/dart-lang/sdk/issues To report a problem with the AutoRoller itself, please file a bug: https://issues.skia.org/issues/new?component=1389291&template=1850622 Documentation for the AutoRoller is here: https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md Tbr: dart-vm-gardener@grotations.appspotmail.com Change-Id: Ie0f6cd4cd05b8d596ac81b428027bc56f56ef626 Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/410141 Reviewed-by: Brian Quinlan <bquinlan@google.com> Commit-Queue: Alexander Aprelev <aam@google.com> Reviewed-by: Alexander Aprelev <aam@google.com>
Dart is:
Approachable: Develop with a strongly typed programming language that is consistent, concise, and offers modern language features like null safety and patterns.
Portable: Compile to ARM, x64, or RISC-V machine code for mobile, desktop, and backend. Compile to JavaScript or WebAssembly for the web.
Productive: Make changes iteratively: use hot reload to see the result instantly in your running app. Diagnose app issues using DevTools.
Dart's flexible compiler technology lets you run Dart code in different ways, depending on your target platform and goals:
Dart Native: For programs targeting devices (mobile, desktop, server, and more), Dart Native includes both a Dart VM with JIT (just-in-time) compilation and an AOT (ahead-of-time) compiler for producing machine code.
Dart Web: For programs targeting the web, Dart Web includes both a development time compiler (dartdevc) and a production time compiler (dart2js).
Dart is free and open source.
See LICENSE and PATENT_GRANT.
Visit dart.dev to learn more about the language, tools, and to find codelabs.
Browse pub.dev for more packages and libraries contributed by the community and the Dart team.
Our API reference documentation is published at api.dart.dev, based on the stable release. (We also publish docs from our beta and dev channels, as well as from the primary development branch).
If you want to build Dart yourself, here is a guide to getting the source, preparing your machine to build the SDK, and building.
There are more documents in our repo at docs.
The easiest way to contribute to Dart is to file issues.
You can also contribute patches, as described in Contributing.
Future plans for Dart are included in the combined Dart and Flutter roadmap on the Flutter wiki.