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

build: Upgrade pipelines to Node18 + upgrade nvm recommendation #17389

Merged
merged 29 commits into from Oct 3, 2023

Conversation

robertobe-ms
Copy link
Contributor

@robertobe-ms robertobe-ms commented Sep 20, 2023

Update the recommended versions of Node.js for developers to use, as well as the version used by CI, from version 14 to 18.

This change made some scenarios in some e2e tests hang, so a fix for skipping them had to be included.
Details:
0.58.x doesn't have the fix to routerlicious-driver in this PR: #8913
(also see related issue for more context on the problem: #9163)
This causes this test to hang while loading container2, as the snapshot is over 16KB.

@github-actions github-actions bot added the area: build Build related issues label Sep 20, 2023
@github-actions github-actions bot added the dependencies Pull requests that update a dependency file label Sep 20, 2023
This reverts commit 314a286.
@github-actions github-actions bot removed the dependencies Pull requests that update a dependency file label Sep 20, 2023
@github-actions github-actions bot added the dependencies Pull requests that update a dependency file label Sep 20, 2023
.npmrc Outdated Show resolved Hide resolved
package.json Outdated Show resolved Hide resolved
@CraigMacomber
Copy link
Contributor

package-lock.json was changed from lock file format 1 to 3. This seems like a bad change since you are trying to stay on the same npm version. Probably revert that file.

@github-actions github-actions bot added the area: server Server related issues (routerlicious) label Sep 21, 2023
@github-actions github-actions bot removed the area: server Server related issues (routerlicious) label Sep 21, 2023
@github-actions github-actions bot added the area: server Server related issues (routerlicious) label Sep 21, 2023
@github-actions github-actions bot added the area: tests Tests to add, test infrastructure improvements, etc label Sep 28, 2023
@msfluid-bot
Copy link
Collaborator

msfluid-bot commented Sep 29, 2023

Could not find a usable baseline build with search starting at CI 7920d44

Generated by 🚫 dangerJS against 9855bf1

@robertobe-ms robertobe-ms marked this pull request as ready for review September 29, 2023 19:58
package.json Outdated Show resolved Hide resolved
Copy link
Member

@tylerbutler tylerbutler left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice work getting the CI to pass! I think you can merge now. :) Even if we need to upgrade npm, we can do that separately.

Copy link
Contributor

@jason-ha jason-ha left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just a few things to comment on or make sure are required changes from me.
Without doing new npm, package-lock.json should probably go back too as Craig suggested.

@tylerbutler
Copy link
Member

Just a few things to comment on or make sure are required changes from me. Without doing new npm, package-lock.json should probably go back too as Craig suggested.

I was able to revert all of these file to their lts versions and everything worked locally:

package-lock.json
examples/apps/view-framework-sampler/src/views/reactView.tsx
examples/data-objects/diceroller/src/main.tsx
examples/hosts/app-integration/container-views/src/view.tsx
packages/test/test-end-to-end-tests/src/test/deRehydrateContainerTests.spec.ts

I suggest reverting those files and seeing if CI still passes.

@jason-ha
Copy link
Contributor

jason-ha commented Oct 3, 2023

CI did fail on examples/apps/view-framework-sampler/src/views/reactView.tsx which is what I had seen too. I don't know how your build worked, Tyler. Of course I don't know why it actually fails either. Mysteries of lerna managed dependencies. Home stretch.


In reply to: 1743993967

@robertobe-ms
Copy link
Contributor Author

The packages/test/test-end-to-end-tests/src/test/deRehydrateContainerTests.spec.ts file was not reverted because that fix and e2e test that hangs.
For details this is the comment that Abram did in the fix:
0.58.x doesn't have the fix to routerlicious-driver in this PR: #8913
(also see related issue for more context on the problem: #9163)
This causes this test to hang while loading container2, as the snapshot is over 16KB.

@robertobe-ms robertobe-ms merged commit a0368d6 into microsoft:lts Oct 3, 2023
21 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: build Build related issues area: dds: propertydds area: dds Issues related to distributed data structures area: driver Driver related issues area: examples Changes that focus on our examples area: server Server related issues (routerlicious) area: tests Tests to add, test infrastructure improvements, etc dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

5 participants