Each package must contain a manifest.v3 file in the ..\packages\package directory. This file is created automatically when you create a package in Designer; it defines various package properties to the Integration Server such as the package name, version, and whether it is enabled or disabled.

You can modify a package's properties by right-clicking the package name in the Navigation panel and clicking Open. The various fields of the Settings and Startup/Shutdown/ Replication Services tabs, and of the Properties panel, represent the contents of the manifest.v3 file. In addition, the manifest.v3 file indicates whether the package is enabled or disabled, as set in the Integration Server Administrator.

Whenever you modify any of these package settings or properties, you are changing the manifest.v3 file. This means that after you make these changes, the local version of the manifest.v3 file no longer matches the version in the VCS repository.

You must use your VCS client to add or update the manifest.v3 file in the VCS repository with the most current local version in the ..\packages\package directory of the Integration Server. The exact procedure for doing this varies depending on your VCS.

If you are sharing development of the package with developers who are working on a different Integration Server, you must also notify those developers that the manifest.v3 file has been updated, and that they must manually update the package's manifest.v3 file on their Integration Server using their VCS client. The manifest.v3 file will not be updated automatically the next time they check out the package.