fix(release): sort groups topologically bottom-up and fix typo to allow multi-level group dependencies

[mpsanchis]

Current Behavior

• topological sorting returns array top-bottom (i.e.: if A -> B -> C, it returns [A, B, C])
• multi-level dependencies are not bumped (i.e.: if A -> B -> C and C is bumped, B is bumped but A is not)
• a set: Set<string> is accessed with set[0], which always returns undefined

Expected Behavior

• topological sorting returns array bottom-up ([C, B, A]), because we typically want to deal with leaves first, and then "touch" the intermediate nodes as we travel up the tree
• multi-level dependencies are bumped (C bumps A, which bumps B)
• set is accessed with set.values().next().value, assuming we want to get any one element from it

Related Issue(s)

Fixes #31375

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

1 Skipped Deployment

Name	Status	Preview	Updated (UTC)
nx-dev	⬜️ Ignored (Inspect)	Visit Preview	May 28, 2025 0:28am

[nx-cloud]

View your CI Pipeline Execution ↗ for commit 52b9631.

Command	Status	Duration	Result
nx affected --targets=lint,test,build,e2e,e2e-c...	❌ Failed	38m 2s	View ↗
nx run-many -t check-imports check-commit check...	✅ Succeeded	16s	View ↗
nx-cloud record -- nx-cloud conformance:check	✅ Succeeded	2s	View ↗
nx-cloud record -- nx format:check	✅ Succeeded	4s	View ↗
nx-cloud record -- nx sync:check	✅ Succeeded	3s	View ↗
nx documentation	✅ Succeeded	53s	View ↗

---

☁️ Nx Cloud last updated this comment at 2025-05-28 13:05:36 UTC

[JamesHenry]

Thanks a lot for this @mpsanchis! You'll need to please update some e2e snapshots as a result of this change. We capture the user experience as best as we can via the snapshots so with the ordering of things changes it impacts those

[JamesHenry]

See comment