mirror of https://github.com/dart-lang/sdk synced 2024-11-02 12:24:24 +00:00

History

Konstantin Shcheglov 9e296e1553 Use Uint8List in ByteStore. Change-Id: I36530aabc6169a9bf05cd212da5fe604f45d4cee Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/216277 Reviewed-by: Brian Wilkerson <brianwilkerson@google.com> Commit-Queue: Konstantin Shcheglov <scheglov@google.com>		2021-10-12 15:33:10 +00:00
..
_fe_analyzer_shared	[vm/ffi] Adds FFI transform FfiNative instance methods.	2021-10-12 10:58:44 +00:00
_js_interop_checks
analysis_server	Update the names of benchmarks to skip.	2021-10-11 21:11:13 +00:00
analysis_server_client
analyzer	Use Uint8List in ByteStore.	2021-10-12 15:33:10 +00:00
analyzer_cli
analyzer_plugin
analyzer_utilities	Improve test that error codes were generated	2021-10-12 14:47:20 +00:00
async_helper
build_integration
compiler
dart2js_info
dart2js_runtime_metrics
dart2js_tools
dart2native
dart_internal
dartdev
dds	[dds] Wrap DAP dart.log message in an object for future extensibility	2021-10-12 15:17:00 +00:00
dev_compiler
diagnostic
expect
front_end	[vm/ffi] Adds FFI transform FfiNative instance methods.	2021-10-12 10:58:44 +00:00
frontend_server
js
js_ast
js_runtime
kernel	[cfe] Account for bounds changes in override substitution	2021-10-12 09:46:25 +00:00
language_versioning_2.7_test
meta
modular_test
native_stack_traces
nnbd_migration
scrape
smith
sourcemap_testing
status_file
telemetry
test_runner
testing
vm	[vm/ffi] Adds FFI transform FfiNative instance methods.	2021-10-12 10:58:44 +00:00
vm_service
vm_snapshot_analysis
.gitignore
BUILD.gn
pkg.status
README.md

README.md

Package validation

The packages in pkg/ are automatically validated on the LUCI CI bots. The validation is largely done by the tools/package_deps package; it can be tested locally via:

dart tools/package_deps/bin/package_deps.dart

Packages which are published

There are several packages developed in pkg/ which are published to pub. Validation of these packages is particularly important because the pub tools are not used for these packages during development; we get our dependency versions from the DEPS file. Its very easy for the dependencies specified in a package's pubspec file to get out of date wrt the packages and versions actually used.

In order to better ensure we're publishing correct packages, we validate some properties of the pubspec files on our CI system. These validations include:

that the dependencies listed in the pubspec are used in the package
that all the packages used by the source are listed in the pubspec
that we don't use relative path deps to pkg/ or third_party/ packages

Packages which are not published

For packages in pkg/ which we do not intend to be published, we put the following comment in the pubspec.yaml file:

# This package is not intended for consumption on pub.dev. DO NOT publish.
publish_to: none

These pubspecs are still validated by the package validation tool. The contents are more informational as the pubspecs for these packages are not consumed by the pub tool or ecosystem.

We validate:

that the dependencies listed in the pubspec are used in the package
that all the packages used by the source are listed in the pubspec
that a reference to a pkg/ package is done via a relative path dependency