Skip to content

Webpack: Remove deprecated standalone webpackConfig option#25481

Merged
valentinpalkovic merged 3 commits into
nextfrom
yann/remove-deprecated-webpack-config-option
Jan 11, 2024
Merged

Webpack: Remove deprecated standalone webpackConfig option#25481
valentinpalkovic merged 3 commits into
nextfrom
yann/remove-deprecated-webpack-config-option

Conversation

@yannbf
Copy link
Copy Markdown
Member

@yannbf yannbf commented Jan 5, 2024

Closes #25377

What I did

TODO (Whoever has context will have to help here)

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

This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!

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 PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the @storybookjs/core team here.

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

@yannbf yannbf added BREAKING CHANGE builder-webpack5 ci:normal Run our default set of CI jobs (choose this for most PRs). labels Jan 5, 2024
@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Jan 5, 2024

Fails
🚫 PR is marked with "BREAKING CHANGE" label.

Generated by 🚫 dangerJS against b91be03

@yannbf
Copy link
Copy Markdown
Member Author

yannbf commented Jan 5, 2024

I don't know whether this is all the change required to remove this feature. I don't have context to write a migration note and when I tried to investigate the introduction of this code there was no explanation.

I need help! @ndelangen could you assist? Thanks!

@valentinpalkovic
Copy link
Copy Markdown
Contributor

cc @ndelangen Can you add a quick migration note or some context as referred above?

@valentinpalkovic valentinpalkovic merged commit 1086e75 into next Jan 11, 2024
@valentinpalkovic valentinpalkovic deleted the yann/remove-deprecated-webpack-config-option branch January 11, 2024 12:51
@github-actions github-actions Bot mentioned this pull request Jan 11, 2024
27 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

BREAKING CHANGE builder-webpack5 ci:normal Run our default set of CI jobs (choose this for most PRs).

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Remove deprecated webpack config from CallOptions

2 participants