Thoughts on fixing pubspec dependencies

[jtmuller5]

In the latest version (0.5.3) of the openai_dart package, they made a change that causes dartantic_ai not to work. This is because dartantic_ai is using "^0.5.2" for the openai_dart version which allows newer versions to be used automatically.

What are your thoughts on pinning some of the more unstable dependencies to version that work and updating them whenever there's a new dartantic_ai version?

I ended up forking and pinning the openai_dart package to version 0.5.2 if anyone is running into this issue:

dartantic_ai:
    git:
      url: https://github.com/jtmuller5/dartantic_ai
      path: packages/dartantic_ai
      ref: fixed-deps

Easier solution

dependency_overrides:
  openai_dart: 0.5.2

[csells]

Hey, @jtmuller5. you're on fire today! Thanks for jumping in.

I think Dart dependency overrides can fix this issue w/o changing dartantic. However, ideally @davidmigloz wouldn't make breaking changes w/o bumping the major version number (or the minor version number of the major version number is 0). What do you think, David?

[davidmigloz]

Apologies, I didn’t realize at the time of merging the PR that it introduced a breaking change.

I use Conventional Commits in combination with Melos for versioning. When a commit includes an exclamation mark in the commit type (e.g., feat!: ...), Melos automatically interprets it as a breaking change and bumps the version accordingly. But in this case, I unfortunately didn’t mark it as breaking.

If this has caused issues, I can retract the current release and publish a new one with the correct versioning to avoid any disruption. Let me know what works best.

[csells]

No worries, David. I need to update for the latest versions of this packages anyway.

Can you tell me about the new googleai_dart? From the changelog, it doesn't look like it's been updated enough to replace google_generative_ai yet.

[davidmigloz]

Alright! In the last release, I mainly updated some dependencies that had major version updates. I haven’t finalized the new googleai_dart yet, but I’m getting close. I’ll let you know as soon as it goes live.

[jtmuller5]

This may be a non issue. After shuffling my dependencies a bit and running flutter clean, I can't reproduce the error. It was related to the CreateChatCompletionStreamResponse.choices field becoming nullable.

[csells]

and to be clear, I asked @davidmigloz to make that parameter nullable. I just have to move dartantic to that new version.

[csells]

fixed with dartantic_ai 1.0.4