Skip to content

Node.js: Update CI to use Node.js v18#24414

Merged
valentinpalkovic merged 8 commits into
nextfrom
valentin/update-to-node-18
Oct 11, 2023
Merged

Node.js: Update CI to use Node.js v18#24414
valentinpalkovic merged 8 commits into
nextfrom
valentin/update-to-node-18

Conversation

@valentinpalkovic
Copy link
Copy Markdown
Contributor

@valentinpalkovic valentinpalkovic commented Oct 9, 2023

Closes #

What I did

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

We should create unlinked sandboxes in both node16 & node 18, check if they all work correctly.

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 self-assigned this Oct 9, 2023
@valentinpalkovic valentinpalkovic added build Internal-facing build tooling & test updates ci:daily Run the CI jobs that normally run in the daily job. labels Oct 9, 2023
@valentinpalkovic valentinpalkovic changed the title Update CI to Node.js v18 Node.js: Update CI to use Node.js v18 Oct 9, 2023
@valentinpalkovic valentinpalkovic force-pushed the valentin/update-to-node-18 branch from 1d70c0b to cce77dc Compare October 10, 2023 12:20
@ndelangen ndelangen self-assigned this Oct 10, 2023
@valentinpalkovic valentinpalkovic force-pushed the valentin/update-to-node-18 branch from 13c745e to 483eb52 Compare October 10, 2023 13:18
ndelangen and others added 5 commits October 10, 2023 15:37
# Conflicts:
#	code/addons/interactions/package.json
#	code/builders/builder-vite/package.json
#	code/builders/builder-webpack5/package.json
#	code/frameworks/angular/package.json
#	code/frameworks/html-vite/package.json
#	code/frameworks/html-webpack5/package.json
#	code/frameworks/nextjs/package.json
#	code/frameworks/preact-vite/package.json
#	code/frameworks/preact-webpack5/package.json
#	code/frameworks/react-vite/package.json
#	code/frameworks/react-webpack5/package.json
#	code/frameworks/server-webpack5/package.json
#	code/frameworks/svelte-vite/package.json
#	code/frameworks/sveltekit/package.json
#	code/frameworks/vue-webpack5/package.json
#	code/frameworks/vue3-vite/package.json
#	code/frameworks/vue3-webpack5/package.json
#	code/frameworks/web-components-vite/package.json
#	code/frameworks/web-components-webpack5/package.json
#	code/lib/core-common/package.json
#	code/lib/core-server/package.json
#	code/lib/core-webpack/package.json
#	code/lib/theming/package.json
#	code/lib/types/package.json
#	code/package.json
#	code/presets/create-react-app/package.json
#	code/presets/html-webpack/package.json
#	code/presets/preact-webpack/package.json
#	code/presets/react-webpack/package.json
#	code/presets/server-webpack/package.json
#	code/presets/vue-webpack/package.json
#	code/presets/vue3-webpack/package.json
#	code/presets/web-components-webpack/package.json
#	code/renderers/react/package.json
#	code/renderers/web-components/package.json
#	code/yarn.lock
#	scripts/package.json
#	scripts/yarn.lock
Dependencies: Upgrade to node18 in a backwards compatible way
@ndelangen
Copy link
Copy Markdown
Member

We changed the name of the "Core Unit Tests node16..." task.
I marked it as no longer required in the repo settings, in the anticipation we'll merge this today @valentinpalkovic

@valentinpalkovic valentinpalkovic merged commit 37f33ab into next Oct 11, 2023
@valentinpalkovic valentinpalkovic deleted the valentin/update-to-node-18 branch October 11, 2023 06:57
@github-actions github-actions Bot mentioned this pull request Oct 11, 2023
13 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

build Internal-facing build tooling & test updates 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.

2 participants