Skip to content

Update dependency get_it to v9#31

Open
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/get_it-9.x
Open

Update dependency get_it to v9#31
renovate[bot] wants to merge 1 commit intomasterfrom
renovate/get_it-9.x

Conversation

@renovate
Copy link
Copy Markdown
Contributor

@renovate renovate Bot commented Nov 3, 2025

This PR contains the following updates:

Package Type Update Change
get_it dependencies major ^7.7.0^9.0.0

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.


Release Notes

flutter-it/get_it (get_it)

v9.2.1

  • Added AI skill files in skills/ directory for AI coding assistants
  • Added AI-Assisted Development section to README

v9.2.0

  • allReady() now caches its Future and returns the same instance on repeated calls
    • Cache is automatically invalidated when new async singletons are registered
    • This enables watch_it to detect when async registrations change (e.g., after pushNewScope)
  • Fixed: pending async singletons now complete their ready completer when removed via unregister() or scope reset, allowing allReady() to complete properly

v9.1.1

  • Updated example project

v9.1.0

  • Added DevTools extension for visualizing and inspecting GetIt registrations
    • View all registered objects with their type, scope, registration mode, and state
    • See instance details via toString() output for created instances
    • Manual refresh button to update the registration list
    • Requires debugEventsEnabled = true to be set on GetIt instance
    • See README for setup instructions

v9.0.5

  • Use absolute GitHub URL for logo in README

v9.0.4

  • Fixed screenshots description to match working 9.0.1 format

v9.0.3

  • Fixed logo display on pub.dev by using relative path

v9.0.2

  • Fixed button sizing in README for pub.dev display

v9.0.1

  • Fixed linter error (missing trailing comma in test file)

v9.0.0

  • BREAKING: Disposal order now always follows strict LIFO (Last-In-First-Out) based on registration order
    • Previously, disposal order was based on the order objects appeared in internal hash maps, which was unpredictable when mixing named and unnamed registrations
    • Now all disposals are sorted by registrationNumber (a sequential counter assigned during registration) ensuring true LIFO order
    • The strictDisposalOrder parameter has been removed from reset(), resetScope(), popScope(), popScopesTill(), and dropScope() methods
    • Performance impact is minimal: ~8% overhead for 10,000 registrations (approximately 2-3ms), negligible for typical applications
    • This change ensures correctness and predictability in dependency cleanup, which is more important than the minor performance cost
    • Impact on existing apps: If your app's behavior relies on the previous imperfect reverse disposal order, there is likely a design issue in your dependency structure that should be addressed
  • Fixed bug in registerCachedFactoryParamAsync where calling getAsync would fail with null error because it was checking the wrong function parameter (sync creationFunctionParam instead of asyncCreationFunctionParam)

v8.3.0

  • Added findAll() method for finding all registered instances by type with flexible matching options (subtypes, interfaces, scope filtering)
  • Added resetLazySingletons() method to reset multiple lazy singletons at once with optional scope parameters
  • Added onCreated callback parameter to registerLazySingleton, registerLazySingletonAsync, and registerSingletonAsync for lifecycle hooks
  • Improved parameter validation error messages in debug mode - now provides clear, actionable feedback when wrong parameter types are passed to factories
  • Fixed bug in cached factories where parameter validation could throw unhelpful errors

v8.2.0

Thanks to PR by @​Hu-Wentao we now expose part of the internal state of get_it so tool authors have more options. While doing so internal renaming has happened, so where previously where the term "ServiceFactory" was uses we not use consistently ObjectRegistration and instead of variables with factory in the name we use registration this has not impact on the public API so it is not a breaking change.

v8.1.0

  • adding documentation #​411
  • registerCachedFactoryAsync usded FactoryFunc instead of FactoryFuncAsync #​410
  • adding getMaybe which will return null instead of throwing an exception in case a type is not registered
  • dependsOn of registerSingletonWithDependencies is now required. Although this could be seen as a breaking change, if you didn't pass dependsOn your code wouldn't have worked before so I won't define this as breaking change

v8.0.3

v8.0.2

v8.0.1

v8.0.0

  • official new release with all the changes

Configuration

📅 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.


  • If you want to rebase/retry this PR, check this box

This PR was generated by Mend Renovate. View the repository job log.

@renovate renovate Bot force-pushed the renovate/get_it-9.x branch from 5631f6c to 3f4b280 Compare November 3, 2025 10:58
@renovate renovate Bot force-pushed the renovate/get_it-9.x branch 2 times, most recently from 11d7ba0 to 4e7e2f4 Compare November 25, 2025 21:41
@renovate renovate Bot force-pushed the renovate/get_it-9.x branch from 4e7e2f4 to 0064e57 Compare December 4, 2025 06:44
@renovate renovate Bot force-pushed the renovate/get_it-9.x branch from 0064e57 to d4aa40a Compare February 12, 2026 12:00
@renovate renovate Bot force-pushed the renovate/get_it-9.x branch from d4aa40a to a588a9a Compare February 20, 2026 01:03
@renovate renovate Bot force-pushed the renovate/get_it-9.x branch from a588a9a to a9d1262 Compare March 13, 2026 16:10
@renovate renovate Bot force-pushed the renovate/get_it-9.x branch from a9d1262 to ac982db Compare March 30, 2026 13:28
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants