Automigration: Run the mdx-to-csf codemod during automigration

[ndelangen]

Closes #26131

What I did

• Remove the autoblocker for *.stories.mdx files
• Add an invocation of the mdx-to-csf codemod during automigration

Checklist for Contributors

Testing

The changes in this PR are covered in the following automated tests:

• stories
• unit tests
• integration tests
• end-to-end tests

Manual testing

Find a SB6 or SB7 project that uses *.stories.mdx
Upgrade this project to SB8
Expect the *.stories.mdx files to get converted
Expect the main.ts file to be migrated too

Documentation

• Add or update documentation reflecting your changes
• If you are deprecating/removing a feature, make sure to update
  MIGRATION.MD

Checklist for Maintainers

• When this PR is ready for testing, make sure to add ci:normal, ci:merged or ci:daily GH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found in code/lib/cli/src/sandbox-templates.ts

• Make sure this PR contains one of the labels below:

  Available labels

  • bug: Internal changes that fixes incorrect behavior.
  • maintenance: User-facing maintenance tasks.
  • dependencies: Upgrading (sometimes downgrading) dependencies.
  • build: Internal-facing build tooling & test updates. Will not show up in release changelog.
  • cleanup: Minor cleanup style change. Will not show up in release changelog.
  • documentation: Documentation only changes. Will not show up in release changelog.
  • feature request: Introducing a new feature.
  • BREAKING CHANGE: Changes that break compatibility in some way with current major version.
  • other: Changes that don't fit in the above categories.

🦋 Canary release

This pull request has been released as version 0.0.0-pr-26201-sha-690050fb. Try it out in a new sandbox by running npx storybook@0.0.0-pr-26201-sha-690050fb sandbox or in an existing project with npx storybook@0.0.0-pr-26201-sha-690050fb upgrade.

More information

Published version	0.0.0-pr-26201-sha-690050fb
Triggered by	@valentinpalkovic
Repository	storybookjs/storybook
Branch	norbert/mdx-stories-automigration
Commit	690050fb
Datetime	Tue Feb 27 15:26:40 UTC 2024 (1709047600)
Workflow run	8067205278

To request a new release of this pull request, mention the @storybookjs/core team.

core team members can create a new canary release here or locally with gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=26201

[valentinpalkovic]

Please adjust the id here: https://github.com/storybookjs/storybook/pull/26201/files#diff-d0ef7b868c6805eb23300a32fce6b47deb8ef83c44fbbf6061b587ff4a1af9b0R35

[valentinpalkovic]

Can you please tell me how you have tested this (on which particular project/setup. Then I try to reproduce it)? I followed your testing instructions but the automigration doesn't run.

[ndelangen]

@valentinpalkovic the check function only returns true if any entries in maint.ts's stories field would match .stories.mdx.

I didn't change that part.
Sorry if I didn't specify that in my steps to reproduce.

I can definitely change that behavior to also check for any existing .stories.mdx files that aren't listed in the user's main.ts file.

[valentinpalkovic]

That's not what I mean.

I looked into it. Even the check function wasn't executing. The automigration isn't listed in the list of fixes here: https://github.com/storybookjs/storybook/blob/next/code/lib/cli/src/automigrate/fixes/index.ts

[ndelangen]

WHUT? I used an existing automigration, and it's not listed...
Meaning it's never been run before?

[valentinpalkovic]

It was run as part of a codemod.

[valentinpalkovic]

Getting the following error when trying to apply the codemod:

How to reproduce

• Checkout https://github.com/freeCodeCamp/freeCodeCamp/tree/main/tools/ui-components
• Run npx storybook@<canary-id> automigrate

(The canary will be available soon: https://github.com/storybookjs/storybook/actions/runs/8067205278)

[ndelangen]

OK, verified locally on an sandbox this time. It works