chore(deps): bump the pub-version-updates group across 1 directory with 2 updates

[dependabot]

Bumps the pub-version-updates group with 2 updates in the / directory: cupertino_icons and flutter_dotenv.

Updates cupertino_icons from 1.0.8 to 1.0.9

Commits

• f330175 [cupertino_icons] Remove empty Dart file (#11308)
• 02f231f [various] iOS/macOS example project automigrations (#11227)
• ee460d6 [various] Modernize non-plugin Android example apps (#11168)
• 1e0338b Updated AGP and KGP to align with flutter/flutter templates (#10423)
• e774c2a [flutter_svg] Update README with an example to scale images (#10547)
• 0250616 [ci] Update repo for 3.41 (#11017)
• 7805d3e [flutter_svg] Convert example app to Swift (#10968)
• 9db114f [mustache_template] Improve error throwing (#10700)
• cc3dca6 [all] Omit obvious local types (#10511)
• 22c6056 [various] Replace deprecated Color.value in SVG packages (#10482)
• Additional commits viewable in compare view

Updates flutter_dotenv from 6.0.0 to 6.0.1

Changelog

Sourced from flutter_dotenv's changelog.

6.0.1

• [fix] isEveryDefined() now throws NotInitializedError before load(), consistent with all other read APIs
• [fix] Replace assert() with explicit if/throw in getInt(), getDouble(), and getBool() so null-safety checks are enforced in release builds
• Error messages now include the variable name for easier debugging
• [fix] load(isOptional: true) no longer discards successfully loaded base file when an override file is missing or empty (fixes #70, #93, #101, #125)
• [fix] clean() now resets isInitialized to false, so accessing env after clean() correctly throws NotInitializedError
• [fix] Error classes (NotInitializedError, FileNotFoundError, EmptyEnvFileError) now include informative messages in toString() instead of the unhelpful Instance of 'ClassName' (fixes #72, #127; improves diagnostics for #59, #89)
• FileNotFoundError and EmptyEnvFileError now carry the filename when available

Note on error message improvements

NotInitializedError, FileNotFoundError, and EmptyEnvFileError now override toString() with actionable messages (e.g., FileNotFoundError: Environment file ".env" not found. Ensure the file exists and is listed under assets in pubspec.yaml.). This is not a breaking change — the class names and hierarchy are unchanged, so existing on FileNotFoundError catch clauses continue to work. FileNotFoundError now accepts an optional positional filename parameter, and EmptyEnvFileError accepts an optional named filename parameter; both default to null for backward compatibility.

Note on release-build behavior change

In debug mode, behavior is unchanged — AssertionError was thrown before, AssertionError is thrown now.

In release mode, calling getInt(), getDouble(), or getBool() with a missing variable and no fallback previously threw a TypeError (from the null-check operator !) because assert() was stripped. It now correctly throws AssertionError with a descriptive message. If your release-mode code catches on TypeError around these methods, update it to catch on AssertionError (or on Error) instead.

Breaking change: clean() now resets initialization state

Previously, calling clean() only cleared the env map but left isInitialized == true. Now it also sets isInitialized = false. Code that calls clean() and then immediately accesses dotenv.env without reloading will now throw NotInitializedError. The fix is to call load() or loadFromString() again after clean().

Commits

• 4f80495 chore(release): publish 6.0.1
• eafce27 fix: isEveryDefined() now throws NotInitializedError before load()
• 8cae9e7 chore: update readme
• 83bcbd8 chore: update readme
• 94f3922 chore: update readme
• 30ecced chore: correct test name
• 2d15c7d fix: add informative messages to error classes (#144)
• 833fcba fix: preserve base env when optional override fails and reset init state on c...
• 3c782c9 chore: update changelog
• b536c85 fix: typed getters without fallback silently fail in release (#142)
• Additional commits viewable in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions