mirror of https://github.com/dart-lang/sdk synced 2024-11-02 14:27:18 +00:00

History

Elliott Brooks 4ac70a3696 Add 'cache-control: no-store' header to DevTools server Bug: https://github.com/flutter/devtools/issues/3896 Change-Id: I5cfc2e92716517a044a848339426feb827bb64cb Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/286100 Commit-Queue: Elliott Brooks <elliottbrooks@google.com> Reviewed-by: Nate Bosch <nbosch@google.com> Reviewed-by: Ben Konyi <bkonyi@google.com>		2023-03-01 01:13:40 +00:00
..
_fe_analyzer_shared	[_fe_analyzer_shared] Exclude patterns with when clauses from exhaustiveness	2023-02-28 16:55:29 +00:00
_js_interop_checks	Revert "[dart:js_interop] Add literal constructors for inline classes"	2023-02-24 20:42:14 +00:00
analysis_server	[analysis_server] Don't endlessly rebuild analysis contexts on PathNotFound errors	2023-02-28 20:27:43 +00:00
analysis_server_client
analyzer	new test for failing super param comment resolution	2023-02-28 21:24:35 +00:00
analyzer_cli
analyzer_plugin
analyzer_utilities
async_helper
build_integration
compiler	[dart2js] Implement `@pragma('dart2js:resource-identifier')`	2023-02-28 03:00:18 +00:00
dart2js_info
dart2js_runtime_metrics
dart2js_tools
dart2native
dart2wasm	Revert "[dart:js_interop] Add literal constructors for inline classes"	2023-02-24 20:42:14 +00:00
dart_internal
dartdev	[ CLI ] Lockdown --no-sound-null-safety in `dart compile` subcommands	2023-02-24 20:27:03 +00:00
dds	Add 'cache-control: no-store' header to DevTools server	2023-03-01 01:13:40 +00:00
dds_service_extensions
dev_compiler	[ddc] Using fully qualified import URIs for deferred load caching	2023-02-28 00:12:33 +00:00
expect
front_end	[_fe_analyzer_shared] Exclude patterns with when clauses from exhaustiveness	2023-02-28 16:55:29 +00:00
frontend_server
js	[js] Bump dependency after removing dependency on `package:js`.	2023-02-22 02:49:37 +00:00
js_ast	[dart2js] Implement `@pragma('dart2js:resource-identifier')`	2023-02-28 03:00:18 +00:00
js_runtime
js_shared
kernel	[cfe] Support implements clause on inline classes	2023-02-23 08:07:44 +00:00
language_versioning_2_7_test
meta
mmap
modular_test
native_stack_traces
nnbd_migration
scrape
smith
sourcemap_testing
status_file
telemetry
test_runner
testing
vm	[vm/kernel_service] Fix `native_assets.yaml` discovery	2023-02-27 16:49:25 +00:00
vm_service	[VM/Service] Add support for class modifiers	2023-02-27 21:07:41 +00:00
vm_snapshot_analysis
wasm_builder
.gitignore
analysis_options.yaml
BUILD.gn
OWNERS
pkg.dart
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