unity cloud build normalize line endings

Note: When incrementing the major version, always reset the PATCH and MINOR values to 0.

Removing or renaming assemblies and Assets (because) the compiler might fail to locate them).

Removing non-API features, including removing Assets or changing an Asset’s GUID.

Changing the API surface (the exposed part of the API) or features in a way that risks compilation or runtime errors.

There is at least one breaking change and neither version of the package can be substituted for the other. During initial development, package APIs change often, frequently in a breaking manner, so keep the MAJOR version number at 0 until you consider your package stable enough and ready for use in production.Īfter a package is officially ready for use in production, increment the MAJOR version to 1 and adhere to the following guidelines for subsequent changes: Increment this value: The MAJOR version number 0 is reserved for packages in their initial development phase. When you begin to develop a package, start the version number at 0.1.0. Semantic Versioning expresses versions as, where MAJOR introduces one or more breaking changes, MINOR introduces one or more backward-compatible API changes, and PATCH only introduces bug fixes with no API changes at all. Semantic Versioning is a strategy that allows package authors to provide information on the type of changes included in a given version, compared to the previous version, in a format that automated tools can use. Packages must follow Semantic Versioning (SemVer).

Unity cloud build normalize line endings