renovate[bot]
commented
10 months ago ⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:
- any of the package files in this branch needs updating, or
- the branch becomes conflicted, or
- you click the rebase/retry checkbox if found above, or
- you rename this PR's title to start with "rebase!" to trigger it manually
The artifact failure details are included below:
File name: example/pubspec.lock
Command failed: docker run --rm --name=renovate_a_sidecar --label=renovate_a_child --memory=3584m -v "/tmp/worker/c7c090/c38693/repos/github/syedmurtaza108/chucker-flutter":"/tmp/worker/c7c090/c38693/repos/github/syedmurtaza108/chucker-flutter" -v "/tmp/worker/c7c090/c38693/cache":"/tmp/worker/c7c090/c38693/cache" -e CONTAINERBASE_CACHE_DIR -w "/tmp/worker/c7c090/c38693/repos/github/syedmurtaza108/chucker-flutter/example" ghcr.io/containerbase/sidecar:9.20.8 bash -l -c "install-tool flutter 3.13.7 && flutter pub get --no-precompile"
pubspec.yaml has no lower-bound SDK constraint.
You should edit pubspec.yaml to contain an SDK constraint:
environment:
sdk: '^3.1.0'
See https://dart.dev/go/sdk-constraint
This PR contains the following updates:
>=2.16.1 <3.0.0-><4.0.0Release Notes
dart-lang/sdk (dart)
### [`v3.2.2`](https://togithub.com/dart-lang/sdk/compare/3.2.1...3.2.2) [Compare Source](https://togithub.com/dart-lang/sdk/compare/3.2.1...3.2.2) ### [`v3.2.1`](https://togithub.com/dart-lang/sdk/compare/3.2.0...3.2.1) [Compare Source](https://togithub.com/dart-lang/sdk/compare/3.2.0...3.2.1) ### [`v3.2.0`](https://togithub.com/dart-lang/sdk/blob/HEAD/CHANGELOG.md#320) [Compare Source](https://togithub.com/dart-lang/sdk/compare/3.1.5...3.2.0) ##### Language Dart 3.2 adds the following features. To use them, set your package's [SDK constraint][language version] lower bound to 3.2 or greater (`sdk: '^3.2.0'`). [language version]: https://dart.dev/guides/language/evolution - **Private field promotion**: In most circumstances, the types of private final fields can now be promoted by null checks and `is` tests. For example: ```dart class Example { final int? _privateField; Example(this._privateField); f() { if (_privateField != null) { // _privateField has now been promoted; you can use it without // null checking it. int i = _privateField; // OK } } } // Private field promotions also work from outside of the class: f(Example x) { if (x._privateField != null) { int i = x._privateField; // OK } } ``` To ensure soundness, a field is not eligible for field promotion in the following circumstances: - If it's not final (because a non-final field could be changed in between the test and the usage, invalidating the promotion). - If it's overridden elsewhere in the library by a concrete getter or a non-final field (because an access to an overridden field might resolve at runtime to the overriding getter or field). - If it's not private (because a non-private field might be overridden elsewhere in the program). - If it has the same name as a concrete getter or a non-final field in some other unrelated class in the library (because a class elsewhere in the program might extend one of the classes and implement the other, creating an override relationship between them). - If there is a concrete class `C` in the library whose interface contains a getter with the same name, but `C` does not have an implementation of that getter (such unimplemented getters aren't safe for field promotion, because they are implicitly forwarded to `noSuchMethod`, which might not return the same value each time it's called). - **Breaking Change** [#53167][]: Use a more precise split point for refutable patterns. Previously, in an if-case statement, if flow analysis could prove that the scrutinee expression was guaranteed to throw an exception, it would sometimes fail to propagate type promotions implied by the pattern to the (dead) code that follows. This change makes the type promotion behavior of if-case statements consistent regardless of whether the scrutinee expression throws an exception. No live code is affected by this change, but there is a small chance that the change in types will cause a compile-time error to appear in some dead code in the user's project, where no compile-time error appeared previously. [#53167]: https://togithub.com/dart-lang/sdk/issues/53167 ##### Libraries ##### `dart:async` - Added `broadcast` parameter to `Stream.empty` constructor. ##### `dart:cli` - **Breaking change** [#52121][]: - `waitFor` is disabled by default and slated for removal in 3.4. Attempting to call this function will now throw an exception. Users that still depend on `waitFor` can enable it by passing `--enable_deprecated_wait_for` flag to the VM. [#52121]: https://togithub.com/dart-lang/sdk/issues/52121 ##### `dart:convert` - **Breaking change** [#52801][]: - Changed return types of `utf8.encode()` and `Utf8Codec.encode()` from `ListConfiguration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Mend Renovate. View repository job log here.