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 to node 20.17.0 lts #1000

Merged
merged 12 commits into from
Nov 11, 2024
Merged

Upgrade to node 20.17.0 lts #1000

merged 12 commits into from
Nov 11, 2024

Commits on Nov 9, 2024

  1. feat: Upgrade node to 16.20.2

    munen committed Nov 9, 2024
    Configuration menu
    Copy the full SHA
    de73bd6 View commit details
    Browse the repository at this point in the history
  2. Configuration menu
    Copy the full SHA
    f6a0892 View commit details
    Browse the repository at this point in the history
  3. Configuration menu
    Copy the full SHA
    fbc257a View commit details
    Browse the repository at this point in the history
  4. feat: Upgrade CRA to v4.0.3

    munen committed Nov 9, 2024
    Configuration menu
    Copy the full SHA
    cbd7cf5 View commit details
    Browse the repository at this point in the history
  5. fix: Make eslint happy

    munen committed Nov 9, 2024
    Configuration menu
    Copy the full SHA
    10e3919 View commit details
    Browse the repository at this point in the history
  6. fix: Silence sass warning

         We use sass only for the landing page. Versions >1.44.0 warn for
         an API change. But we only need to require one file. I didn't see
         how to use the new API without hitting the warning. We already
         just upgraded from node-sass to sass. So we can work with a
         slightly older new library, I'd say(;
    munen committed Nov 9, 2024
    Configuration menu
    Copy the full SHA
    ac447a9 View commit details
    Browse the repository at this point in the history
  7. fix: Silence a 'this will never change' warning

         One of your dependencies, babel-preset-react-app, is importing
         the "@babel/plugin-proposal-private-property-in-object" package
         without declaring it in its dependencies. This is currently
         working because
         "@babel/plugin-proposal-private-property-in-object" is already in
         your node_modules folder for unrelated reasons, but it may break
         at any time.
    
         babel-preset-react-app is part of the create-react-app project,
         which is not maintianed anymore. It is thus unlikely that this
         bug will ever be fixed. Add
         "@babel/plugin-proposal-private-property-in-object" to your
         devDependencies to work around this error. This will make this
         message go away.
    munen committed Nov 9, 2024
    Configuration menu
    Copy the full SHA
    20ec311 View commit details
    Browse the repository at this point in the history
  8. feat: Upgrade to Node 20.17.0

    munen committed Nov 9, 2024
    Configuration menu
    Copy the full SHA
    ce83d76 View commit details
    Browse the repository at this point in the history
  9. Configuration menu
    Copy the full SHA
    ffc61c8 View commit details
    Browse the repository at this point in the history
  10. Configuration menu
    Copy the full SHA
    04fd7f6 View commit details
    Browse the repository at this point in the history
  11. chore: Upgrade redux-undo

    munen committed Nov 9, 2024
    Configuration menu
    Copy the full SHA
    f4ca1b2 View commit details
    Browse the repository at this point in the history

Commits on Nov 11, 2024

  1. doc: Update changelog

    munen committed Nov 11, 2024
    Configuration menu
    Copy the full SHA
    8c0e157 View commit details
    Browse the repository at this point in the history