Skip to content

chore(deps): bump web from 1.1.1 to 1.1.2 - #1290

Open
dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/pub/web-1.1.2
Open

dependabot[bot] wants to merge 1 commit into
mainfrom
dependabot/pub/web-1.1.2

Conversation

@dependabot

@dependabot dependabot Bot commented on behalf of github Nov 12, 2026 •

Copy link
Copy Markdown
Contributor

Bumps web from 1.1.1 to 1.1.2.

Release notes

Sourced from web's releases.

package:web v1.1.2

  • Added dart fix migrations for package:web/helpers.dart and deprecated 1.1.x APIs.
  • Removed the broken UnderlyingSourceBase to UnderlyingSource dart fix rename where the target type does not exist.
  • Require Dart ^3.13.0 to support library-level dart fix migrations.
Commits
  • b28c2cc Add 1.1.2 fix_data.yaml migrations and prepare 1.1.2 release (#602)
  • 06c9933 Require Dart ^3.13.0 and format package:web with tall style (#601)
  • f69d498 Replace mono_repo CI with standalone workflows on v1.1-stable (#600)
  • See full diff in compare view

@dependabot dependabot Bot added the dart Pull requests that update dart code label Nov 12, 2026
@dependabot dependabot Bot added the dependencies Pull requests that update a dependency file label Nov 12, 2026

@devin-ai-integration devin-ai-integration Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Devin Review found 1 potential issue.

Devin Review

Comment thread pubspec.lock
url: "https://pub.dev"
source: hosted
version: "1.1.1"
version: "1.1.2"

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🟡 Locked web release excludes supported Dart

On Dart 3.11 or 3.12, flutter pub get --enforce-lockfile cannot install web 1.1.2, which requires Dart 3.13. Ordinary pub get downgrades it and rewrites the lockfile instead.

Learn more

The repository advertises Dart >=3.10 in environment, and the committed lockfile itself advertises >=3.11. The new web release requires Dart ^3.13.0. Pub's solver cannot preserve a lockfile containing that release on a supported Dart 3.11 or 3.12 installation; enforcing the lockfile fails, while ordinary dependency resolution selects an older compatible release and modifies it.

Example: A contributor on Flutter with Dart 3.12 checks out this commit and runs flutter pub get --enforce-lockfile. The install fails because web 1.1.2 excludes their SDK, although Dart 3.12 is supported by the package.

Recommended fix: Keep the committed web version compatible with the supported Dart floor, or explicitly raise the supported SDK floor if dropping older Dart releases is intended. Validate dependency resolution with a supported pre-3.13 SDK.

Devin Review


Was this helpful? React with 👍 or 👎 to provide feedback.

Bumps [web](https://github.com/dart-lang/web) from 1.1.1 to 1.1.2.
- [Release notes](https://github.com/dart-lang/web/releases)
- [Commits](dart-lang/web@web-v1.1.1...web-v1.1.2)

---
updated-dependencies:
- dependency-name: web
  dependency-version: 1.1.2
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <support@github.com>
@dependabot
dependabot Bot force-pushed the dependabot/pub/web-1.1.2 branch from c83371f to 31c3462 Compare November 19, 2026 04:01
@github-actions

Copy link
Copy Markdown

Warning

No changeset found

If this PR includes user-facing changes, please add a changeset file in .changes/

Format: level type="kind" "description"

patch type="fixed" "Fix audio frame generation"
minor type="added" "Add support for custom audio processing"
major type="changed" "Breaking: Rename Room.connect() to Room.join()"

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

dart Pull requests that update dart code dependencies Pull requests that update a dependency file

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants