feat(core): support collecting migrations excluding the already applied ones

[leosvelperez]

Current Behavior

To run previously skipped migrations, the user needs to run nx migrate latest --from=nx@<older version>. This will collect all migrations from every package collected from the specified older version, regardless of whether the migration ran before. While it shouldn't pose an actual issue (migrations should be idempotent), it does take longer to run things that are not needed and it's harder for the user to know which migrations really matter.

Expected Behavior

To collect migrations while excluding migrations that were meant to be applied on previous updates, the user would use a new flag: nx migrate latest --from=nx@<older version> --exclude-applied-migrations. Note that migrations manually removed from the migrations.json on previous updates won't be collected.

Related Issue(s)

Fixes #

[vercel]

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

Name	Status	Preview	Comments	Updated
nx-dev	✅ Ready (Inspect)	Visit Preview	💬 Add your feedback	Feb 21, 2023 at 3:53PM (UTC)

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 9058d73. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

---

✅ Successfully ran 1 target

• nx run-many -t e2e-macos --parallel=1 --exclude=e2e-detox

---

Sent with 💌 from NxCloud.

[AgentEnder]

I accidentally caused you some conflicts... 😞 Sorry.

Otherwise, this only works for packageJsonUpdates right? There's no way to tell if migrations.json generator based updates have previously been applied.

[leosvelperez]

I accidentally caused you some conflicts... 😞 Sorry.

No worries!

Otherwise, this only works for packageJsonUpdates right? There's no way to tell if migrations.json generator based updates have previously been applied.

We can tell whether migrations were meant to run based on the currently installed versions and the requirements and target versions of each migration. That's what we're doing here. We definitely don't account for manually removed migrations. If someone needs to run all, they can still run nx migrate latest --from=nx@<older version> without the new flag. This is an opt-in feature, it won't change the default behavior. We could probably call it out better in docs.

[isaacplmann]

This is a much cleaner experience. I like it

[github-actions]

This pull request has already been merged/closed. If you experience issues related to these changes, please open a new issue referencing this pull request.