There are three migration paths:

It is also used to migrate existing clients using direct authentication schemes such as HTTP Basic or Digest authentication to OAuth by converting the stored credentials to an access token.

WI model will be built on top of the existing Issue model and we’ll gradually migrate Issue model code to the WI model.

one should not upgrade a production environment without extensive testing. I prefer to not upgrade prod at all. Instead, I create a new instance with latest everything, host my apps there, test everything out, and then make it production.

Don't worry if your project isn't quite ready for Plug'n'Play just yet! This guide will let you migrate without losing your node_modules folder. Only in a later optional section we will cover how to enable PnP support, and this part will only be recommended, not mandatory. Baby steps!

it is highly encouraged to switch to zeitwerk mode because it is a better autoloader

o help us meet this vision, the frontend should use GraphQL in preference to the REST API for new features.

Seamless transitions; changes made to the old repositories after they were migrated must be imported to the new monorepository.

What happens to my functions? I encourage you to migrate your workloads to OpenFaaS.

We have fully documented the migration path to 2.1 while upgrading several complex apps. It worked.

Sass variables, like all Sass identifiers, treat hyphens and underscores as identical. This means that $font-size and $font_size both refer to the same variable. This is a historical holdover from the very early days of Sass, when it only allowed underscores in identifier names. Once Sass added support for hyphens to match CSS’s syntax, the two were made equivalent to make migration easier.

Users want work be done. Not struggling about how allowing access to removable medias or such a file on another partition… Not breaking their habits or workflows each time a snap replaces a deb.