[native_assets_cli] Publish 0.15.0

[dcharkes]

Pub gives a warning on releasing a package that's not a pre-release with a Dart dev constraint:

• Pre-release SDK constraints should not require a pre-release version pub-dev#3897

However, pre-releases don't get prioritized by pub:

• https://dart.dev/tools/pub/publishing#publishing-prereleases
• [native_assets_cli][native_assets_builder] Supporting version skew between SDK and build.dart #93 (comment)

Since build hooks are dev/main branch experiments only, we'd want users to always be on the newest version of package:native_assets_cli. (Their CIs will automatically roll forward to the newest Dart dev release or Flutter master channel.)

edit: after dart-lang/ecosystem#357 we can now ignore the warning.

[github-actions]

PR Health

Breaking changes ✔️

Package	Change	Current Version	New Version	Needed Version	Looking good?
native_assets_builder	Breaking	0.14.0	0.15.0-0	0.15.0	✔️
native_assets_cli	Non-Breaking	0.14.0	0.15.0	0.14.1	✔️
native_toolchain_c	Non-Breaking	0.11.0	0.12.0-0	0.11.1	✔️

API leaks ✔️

The following packages contain symbols visible in the public API, but not exported by the library. Export these symbols or remove them from your publicly visible API.

Package	Leaked API symbols

License Headers ✔️

// Copyright (c) 2025, the Dart project authors. Please see the AUTHORS file
// for details. All rights reserved. Use of this source code is governed by a
// BSD-style license that can be found in the LICENSE file.

Files
no missing headers

All source files should start with a license header.

Unrelated files missing license headers

Files
pkgs/jni/lib/src/third_party/generated_bindings.dart
pkgs/objective_c/lib/src/ns_input_stream.dart

[dcharkes]

cc @jonasfj @sigurdm Is there a way to suppress

  Package validation found the following potential issue:
  * Packages with an SDK constraint on a pre-release of the Dart SDK should themselves be published as a pre-release version. If this package needs Dart version 3.8.0-260.0.dev, consider publishing the package as a pre-release instead.

so that we can use the publish automation?

[coveralls]

coverage: 77.114%. remained the same
when pulling 90ba5e9 on try-non-prerelease
into 9c551c1 on main.

[sigurdm]

We don't currently have such a mechanism available (dart-lang/pub#3807)

[github-actions]

Package publishing

Package	Version	Status	Publish tag (post-merge)
package:ffi	2.1.4	already published at pub.dev
package:ffigen	18.1.0	already published at pub.dev
package:jni	0.14.1	already published at pub.dev
package:jnigen	0.14.2-wip	WIP (no publish necessary)
package:native_assets_builder	0.15.0-0	already published at pub.dev
package:native_assets_cli	0.15.0	ready to publish	native_assets_cli-v0.15.0
package:native_toolchain_c	0.12.0-0	already published at pub.dev
package:objective_c	7.1.0	already published at pub.dev
package:swift2objc	0.0.1-wip	WIP (no publish necessary)
package:swiftgen	0.0.1-wip	WIP (no publish necessary)

Documentation at https://github.com/dart-lang/ecosystem/wiki/Publishing-automation.

[goderbauer]

LGTM