ruby2_keywords might be removed in the future after Ruby 2.6 reaches end-of-life. At that point, we recommend to explicitly delegate keyword arguments

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

A major update usually means breaking changes in the API therefore a bit of learning is required in order to embrace it in your projects.

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.

As you installed a development release (17.04) that had only a 9-month life span and had an End of Life (EOL) in Jan 2018, there is no way to upgrade it to 17.10 as that went EOL back in July 2018. So as you're stuck with a release without an upgrade path (as you cannot skip versions)

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.

In the next major, we'll start copying the ref onto both the props and the element.ref. React will now use the props.ref as the source of truth for forwardRef and classes and it will still create a shallow copy of props that excludes the ref in these cases. At the same time, we'll add a getter for element.ref in DEV that warns if you access it. The upgrade path is now to just access it off props if you need it from the element.

The backwards compatible implementation of jsx(...), we would still support key passed as props. We'd just pull it off props and issue a warning that this pattern is deprecated. The upgrade path is to just pass it to JSX separately if you need it.

This would be a breaking change, but we could always clone in the call in a minor and then make the breaking change later in a major.

It's much easier to iterate on new versions by deploying npm packages than updates to the compiler toolchain. Therefore, it might be best if the actual implementation still lives in the react package.

the actual upgrade path should be very simple for most people since the deprecated things are mostly edge cases and any common ones can be codemodded