Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maintenance: Set engines field to Node.js >= 18 for packages #25105

Merged
merged 7 commits into from
Dec 11, 2023

Conversation

valentinpalkovic
Copy link
Contributor

@valentinpalkovic valentinpalkovic commented Dec 4, 2023

Closes #25174

What I did

Set engines field to Node.js >= 18 for npm packages

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>

@valentinpalkovic valentinpalkovic added maintenance User-facing maintenance tasks ci:daily Run the CI jobs that normally run in the daily job. labels Dec 4, 2023
@valentinpalkovic valentinpalkovic self-assigned this Dec 4, 2023
@valentinpalkovic valentinpalkovic changed the title Set engines field to Node.js >= 18 for packages Maintenance: Set engines field to Node.js >= 18 for packages Dec 4, 2023
@valentinpalkovic valentinpalkovic merged commit 1fe208e into next Dec 11, 2023
6 checks passed
@valentinpalkovic valentinpalkovic deleted the valentin/set-engines-field-to-node-18 branch December 11, 2023 15:05
@github-actions github-actions bot mentioned this pull request Dec 11, 2023
9 tasks
Copy link
Contributor

github-actions bot commented Dec 27, 2023

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

Generated by 🚫 dangerJS against b6c438a

@valentinpalkovic valentinpalkovic removed the maintenance User-facing maintenance tasks label Dec 27, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
BREAKING CHANGE ci:daily Run the CI jobs that normally run in the daily job.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Upgrade minimum supported Node.js version to v18
2 participants