Maybe related to #2914 ?

If this is intended, maybe this deprecation should be included in the changelog

Confirming this impacts Firefox pretty badly too, where Vue Devtools v7 isn't yet distributed on the extensions store, making developing with Pinia in Firefox much more difficult currently.

Indeed @Cherry, thanks for bringing that up !
I didn't even think about that and I've been following vuejs/devtools#660 for a while.

You can:

• use the Vite plugin
• Stay on Pinia 2
• Wait until Firefox approves the new version for the devtools

I didn't know the Firefox version was still on v6, that's quite a shame but also nothing I can do about it 😅

@posva

1. I don't know what you mean by vite plugin, I'll look it up.

2. Ok, but I didnt know I'd lose devtools when i upgraded. There is no mention of this, and there is no warning in the console or anywhere so I lost quite a bit of time.

Can this be documented anywhere ? I feel like a mention in the changelog would be a good place, no ? How are people expected to know that Pinia v3 doesn't support Devtools v6 anymore otherwise ?

3. The problem is not that v7 is not approved by Firefox, the problem is that the devtools team did not even send the update for approbation... But hopefully that's going to change, I see a team member said he talk to Evan You about this

It's indeed not in the changelog! It wasn't meant to be a breaking change either. Contribution welcome!

I'll open a PR, thanks.
Although if I add it to changelog.md, I'm not sure it will update the GitHub Release content.
I might add a mention in the regular doc if I find somewhere suitable

@posva I have a basic PR that add a note to the changelog, I also wanted to see if I could add a runtime console.warn() if we detect Pinia >= 3.0.0 when running with Devtools v6, but can't seem to find a way to get the devtools version.

But in my investigation, I found out that Devtools v7 still use the exact same API as Devtools v6, see here.
So now I'm wondering with the plugin wouldn't work with both version, I've reviewed the whole v3 PR and couldn't understand why.