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

upgrade next #869

Merged
merged 1 commit into from
Dec 15, 2021
Merged

upgrade next #869

merged 1 commit into from
Dec 15, 2021

Conversation

phoenixAja
Copy link
Collaborator

@phoenixAja phoenixAja commented Dec 15, 2021

Summary:

  • What: upgrade Next (In versions of Next.js prior to 12.0.5 or 11.1.3, invalid or malformed URLs could lead to a server crash. In order to be affected by this issue, the deployment must use Next.js versions above 11.1.0 and below 12.0.5)
  • Ticket: sc177040
  • Env: rdev link

Demos:

Notes:

Checklist:

  • I merged latest trunk
  • I manually verified the change
  • I added labels to my PR
  • I tested in multiple browsers
  • I added relevant unit tests
  • I have notified others of changes they need to make locally (migrations, jobs, package updates, etc)

@phoenixAja phoenixAja added frontend Involves changes to frontend code dependencies Pull requests that update a dependency file labels Dec 15, 2021
Copy link
Contributor

@vincent-czi vincent-czi left a comment

Choose a reason for hiding this comment

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

Seems reasonable! My only concern would be if there turns out to be some kind of version issue, but as long as you were able to do some QA and it was clean of any weird behavior, seems good to me.

@@ -1,5 +1,4 @@
/// <reference types="next" />
/// <reference types="next/types/global" />
Copy link
Contributor

Choose a reason for hiding this comment

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

What's this about?

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

a little confusing to tell from the docs but this file is regenerated when you run next build, i think it removed that line because that next type is no longer relevant to the typescript compiler with the upgrade

Copy link
Contributor

Choose a reason for hiding this comment

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

I just needed to docker-compose down then up the containers -- also ran a DB migration, but I don't think that matters -- and this line re-appeared in my next-env.d.ts file.

/// <reference types="next/types/global" />

Maybe we should re-commit it back in? Probably has no impact on how it runs since we build during the CI pipeline, but if it keeps showing up as a dirty file locally that will just be confusing to see.

@phoenixAja phoenixAja merged commit c4b655c into trunk Dec 15, 2021
@phoenixAja phoenixAja deleted the phoenix/next-upgrade branch December 15, 2021 20:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file frontend Involves changes to frontend code
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants