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
Update React to 18.3.1 #3249
Update React to 18.3.1 #3249
Conversation
It seems the useless empty comments are no longer added as often as they used to be.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If these warnings are not overwhelming, then it is probably fine to merge as-is. Otherwise it is preferable to fix the majority of warnings in the same pull request.
Does the upgrade actually cause new warnings to be logged for us, or are you talking about simply removing the deprecated APIs from the Flow libdefs? |
The latter - no warnings I could see, but I didn't use everything - if warnings are logged to sentry then we know what to improve on though :) |
* master: Update POT files using the production database MBS-13577 / MBS-13578: Release filtering for missing data (#3262) MBS-13589: Handle Operabase /o links (#3268) Convert /static/scripts/release templates to use Flow component syntax Convert /static/scripts/relationship-editor templates to use Flow component syntax Convert some more /static/scripts/ templates to use Flow component syntax Remove seemingly useless double export Convert /static/scripts/edit/components templates to use Flow component syntax Convert /static/scripts/common/components templates to use Flow component syntax Drop dead code in AddEntityDialog Drop unneeded instance typing in hydrate input Convert /components templates to use Flow component syntax Convert /components/list templates to use Flow component syntax Convert /components/Aliases templates to use Flow component syntax Convert /layout sidebar templates to use Flow component syntax Convert /layout templates to use Flow component syntax MBS-13585: Report for non-video recordings with video relationships (#3266) MBS-13581: Check "renamed into" in ArtistsThatMayBeGroups (#3265) Convert /edit/details templates to use Flow component syntax Convert /edit/details/historic templates to use Flow component syntax Convert /edit/component templates to use Flow component syntax Convert /edit templates to use Flow component syntax Update React to 18.3.1 (#3249) MBS-13263: Align release titles despite indicators (#3256) MBS-13588: Relationship phrase groups with pending edits are sometimes not highlighted Add `PendingEditsRoleT` to `RelatableEntityRoleT` Make `Entity::Artist::TO_JSON` consistent with `ArtistT` Use consistent chained method formatting Cache pending requests for `getOrFetchRecentItems` MBS-12741: Convert Create/Edit attribute admin pages to React Fix typo Limit `getReleaseGroupRecordings` to 5 attempts MBS-13558: Convert /report templates to use Flow component syntax MBS-13558: Convert /report/component templates to use Flow component syntax MBS-13573: Support a second format of Ticketmaster links MBS-13572: Support LiveNation links with _ and - MBS-13559: Don't reject dailysomething Bandcamp pages (#3255) Add context to newly added [removed] (#3246) Reuse same 'view list' string everywhere (#3247) Document that language packs must be installed Fix installing translations for beta/test websites admin/cron/hourly-sitemaps.sh: Dump FKs from READONLY Add missing scripts required by JSON dumps/sitemaps
18.2.0 fixed some false positive errors, maybe it will improve the issues with tons of Suspense hydration errors being logged on Sentry?
18.3.0 / .1 make no changes other than adding warnings for things that will be removed with v19, which is now in beta.
For now this just updates the package - I have not changed the types to remove the deprecated stuff with warnings since I guess we'll want to do that for 19.0.0?
Putting this up for CI and for general advice on what else if anything is needed, since recently we've only updated on major versions (which obviously require more work).