Documentation for Where's-my-commit > Finding the Dart SDK commit contained in Engine commit X is out of date

[puf]

Context: https://x.com/k8lovett/status/1922354997590671645
Docs link: https://github.com/flutter/flutter/blob/master/docs/releases/Where's-my-commit.md#finding-the-versions-that-contain-framework-commit-x

The documentation on how to find the version that includes a specific commit/PR seems to be outdated, as it doesn't cover autorolls such as flutter/packages#9098.

It would also be good if the documentation linked out to this handy tool: https://justinmc.github.io/flutter_releases (e.g. https://justinmc.github.io/flutter_releases/#/pr/framework/162667)

Tagging @Piinks who asked me to file this issue. :)

[stuartmorgan-g]

as it doesn't cover autorolls such as flutter/packages#9098.

The flutter/flutter->flutter/packages autoroller is not relevant to determining Flutter releases; what would you expect these docs to say about it?

[puf]

Fair question, I probably should've included that into. :)

I'm trying to find it in which version (if any) this PR has been released: #162667

Thanks to @justinmc 's flutter_releases tool I now know that it's not out yet, but I was unable to determine that by following the steps in this documentation section. That might certainly be a me problem (in which case it may be an opportunity to make the docs more puf proof), but from the Twitter thread it might also be that the docs section needs a (monorepo related?) update.

[stuartmorgan-g]

Sure, there may be changes to be made there. It looks like the screenshot should be showing an example of the merge queue for the commit line, for instance, rather than the auto-submit bot.

But I was trying to understand the specific part of the request that said it should cover flutter/packages autorollers. What is the relationship between that roller and the task you were trying to accomplish? I (as the primary owner of that particular roller) am not sure what you would want these docs to say about it.

[puf]

I was trying to follow the documented process from #162667 to a release, and that seems to have gotten rolled into flutter/packages#9098 where I lost track of what to do next. Let's assume-without-blame I misused the term "autorolls" there and stick to the use-case only.

[stuartmorgan-g]

You used the term autorolls correctly; the important question now is why you ended up in flutter/packages#9098 in the first place. Were you trying to follow this step:

and clicked on this entry:

instead of this one:

? If so, just updating the screenshot in step 1 may be all we need here.

[puf]

Let me see if I can retrace: 1. I started from Taha's PR #162667 2. From there I clicked on the Commits tab and then the most recent commit f74f39c 3. That led to: [image: CleanShot 2025-05-14 at ***@***.*** 4. This shows no sha, so I could no longer follow the documented process But now how did I get to flutter/packages#9098? 🤔 Oh yeah, that's definitely it: [image: CleanShot 2025-05-14 at ***@***.*** (At some point) I clicked on that last one, because it also showed "Merged" there. Thanks for sticking with me on that, Stuart. 🙏 Now that I clicked on the correct link, I see: [image: CleanShot 2025-05-14 at ***@***.*** Which shows a tag as the docs say. That's not as clear as the ismypriunflutteryet.com <https://ismyprinflutteryet.com/> for the same commit, so it'd still be good to link that too: [image: CleanShot 2025-05-14 at ***@***.***

…

On Wed, May 14, 2025 at 7:27 AM stuartmorgan-g ***@***.***> wrote: *stuartmorgan-g* left a comment (flutter/flutter#168753) <#168753 (comment)> You used the term autorolls correctly; the important question now is why you ended up in flutter/packages#9098 <flutter/packages#9098> in the first place. Were you trying to follow this step: Screenshot.2025-05-14.at.10.24.06.AM.png (view on web) <https://github.com/user-attachments/assets/91ea7fd5-9628-4c5a-9ade-1f3fec9e2273> and clicked on this entry: Screenshot.2025-05-14.at.10.25.21.AM.png (view on web) <https://github.com/user-attachments/assets/28e522b8-35c2-4884-93d8-b89c4a5cc592> instead of this one: Screenshot.2025-05-14.at.10.25.28.AM.png (view on web) <https://github.com/user-attachments/assets/8d12e299-6605-4a1a-8645-e853c3baa551> ? If so, just updating the screenshot in step 1 may be all we need here. — Reply to this email directly, view it on GitHub <#168753 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAG7BX7C3VHY3ZZQLISCR7D26NHFBAVCNFSM6AAAAAB5BLEXOKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDQOBQGQ2TOOJTGE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[tirth-patel-nc]

Possibly related to #66565