package ID for model dependencies, it is necessary to take into account two factors: • The versioning schema followed by our requirements (semver?, custom?). • The type of library being built or reused (shared static). 7.6. Defining Package ABI Compatibility 75 Conan Documentation, Release 1.56.0 Versioning Schema By default Conan assumes semver compatibility. For example, if a version changes from minor 2.0 doesn’t require a re-build. If it is necessary to change the default behavior, the applied versioning schema can be customized within the package_id() method: from conans import ConanFile, CMake, tools from

factors: • The versioning schema followed by our requirements (semver?, custom?). • The type of library being built or reused (shared (.so, .dll, .dylib), static). Versioning Schema By default Conan assumes doesn’t require a re-build. If it is necessary to change the default behavior, the applied versioning schema can be customized within the package_id() method: 7.6. Defining Package ABI Compatibility 73 Conan certificates 17.24.1 Server certificate validation By default, when a remote is added, if the URL schema is https, the Conan client will verify the certificate using a list of authorities declared in the

package ID for model dependencies, it is necessary to take into account two factors: • The versioning schema followed by our requirements (semver?, custom?). • The type of library being built or reused (shared static). 7.6. Defining Package ABI Compatibility 73 Conan Documentation, Release 1.52.0 Versioning Schema By default Conan assumes semver compatibility. For example, if a version changes from minor 2.0 doesn’t require a re-build. If it is necessary to change the default behavior, the applied versioning schema can be customized within the package_id() method: from conans import ConanFile, CMake, tools from

package ID for model dependencies, it is necessary to take into account two factors: • The versioning schema followed by our requirements (semver?, custom?). • The type of library being built or reused (shared static). 7.6. Defining Package ABI Compatibility 75 Conan Documentation, Release 1.53.0 Versioning Schema By default Conan assumes semver compatibility. For example, if a version changes from minor 2.0 doesn’t require a re-build. If it is necessary to change the default behavior, the applied versioning schema can be customized within the package_id() method: from conans import ConanFile, CMake, tools from

package ID for model dependencies, it is necessary to take into account two factors: • The versioning schema followed by our requirements (semver?, custom?). • The type of library being built or reused (shared static). 7.6. Defining Package ABI Compatibility 75 Conan Documentation, Release 1.54.0 Versioning Schema By default Conan assumes semver compatibility. For example, if a version changes from minor 2.0 doesn’t require a re-build. If it is necessary to change the default behavior, the applied versioning schema can be customized within the package_id() method: from conans import ConanFile, CMake, tools from

package ID for model dependencies, it is necessary to take into account two factors: • The versioning schema followed by our requirements (semver?, custom?). • The type of library being built or reused (shared static). 7.6. Defining Package ABI Compatibility 75 Conan Documentation, Release 1.55.0 Versioning Schema By default Conan assumes semver compatibility. For example, if a version changes from minor 2.0 doesn’t require a re-build. If it is necessary to change the default behavior, the applied versioning schema can be customized within the package_id() method: from conans import ConanFile, CMake, tools from

factors: • The versioning schema followed by our requirements (semver?, custom?). • The type of library being built or reused (shared (.so, .dll, .dylib), static). Versioning Schema By default Conan assumes doesn’t require a re-build. If it is necessary to change the default behavior, the applied versioning schema can be customized within the package_id() method: 7.6. Defining Package ABI Compatibility 65 Conan certificates 17.24.1 Server certificate validation By default, when a remote is added, if the URL schema is https, the Conan client will verify the certificate using a list of authorities declared in the

factors: • The versioning schema followed by our requirements (semver?, custom?). • The type of library being built or reused (shared (.so, .dll, .dylib), static). Versioning Schema By default Conan assumes doesn’t require a re-build. If it is necessary to change the default behavior, the applied versioning schema can be customized within the package_id() method: 7.6. Defining Package ABI Compatibility 65 Conan certificates 17.24.1 Server certificate validation By default, when a remote is added, if the URL schema is https, the Conan client will verify the certificate using a list of authorities declared in the

package ID for model dependencies, it is necessary to take into account two factors: • The versioning schema followed by our requirements (semver?, custom?). • The type of library being built or reused (shared static). 7.6. Defining Package ABI Compatibility 77 Conan Documentation, Release 1.57.0 Versioning Schema By default Conan assumes semver compatibility. For example, if a version changes from minor 2.0 doesn’t require a re-build. If it is necessary to change the default behavior, the applied versioning schema can be customized within the package_id() method: from conans import ConanFile, CMake, tools from

package ID for model dependencies, it is necessary to take into account two factors: • The versioning schema followed by our requirements (semver?, custom?). • The type of library being built or reused (shared static). 7.6. Defining Package ABI Compatibility 79 Conan Documentation, Release 1.59.0 Versioning Schema By default Conan assumes semver compatibility. For example, if a version changes from minor 2.0 doesn’t require a re-build. If it is necessary to change the default behavior, the applied versioning schema can be customized within the package_id() method: from conans import ConanFile, CMake, tools from