# Project Dependencies Mass Update

> The **Project Dependencies Mass Update Tool** is used for updating dependency packages and their runtime rules in multiple automation projects, stored locally or in source control repositories.

The **Project Dependencies Mass Update Tool** is used for updating dependency packages and their runtime rules in multiple automation projects, stored locally or in source control repositories.

:::note
**Project Dependencies Mass Update Tool** is available starting with Studio v2018.4.4.
:::

The wizard can be accessed both from Studio Backstage view and [command line](https://docs.uipath.com/studio/standalone/latest/user-guide/mass-update-command-line-parameters#mass-update-command-line-parameters). Please note that the **Project Dependencies Mass Update Tool** from Studio Backstage view cannot be used for removing dependencies from the project.

:::note
Before using the **Project Dependencies Mass Update Tool** with **TFS**, make sure the projects you want to update are disconnected from **TFS** for the current user.
:::

Please note that when using the **Project Dependencies Mass Update Tool**, you implicitly accept the license terms of each package version that you update.

It is recommended to save and close projects from Studio, before making changes to them using the **Project Dependencies Mass Update Tool**.

## Mass Updating Projects

1. Select **Home** (Studio Backstage View) > **Tools** > **Apps** > **Project Dependencies Mass Update Tool**. The **Project Dependencies Mass Update** window opens.
2. The **Choose Feeds** step shows all default and custom package feeds configured in Studio. Select the check box next to the feeds that contain the needed dependency versions.
3. Click **Next**. The **Select Dependencies** step is displayed.

   ![docs image](https://dev-assets.cms.uipath.com/assets/images/studio/studio-docs-image-167941-aa97ebdf.webp)
4. Similar to the [Manage Packages](https://docs.uipath.com/studio/standalone/latest/user-guide/managing-activities-packages#managing-activity-packages) window, use the search bar in the **Select Dependencies** tab to find a specific dependency version. Select the **Include Prerelease** check box to view intermediary versions. Under **Install Missing Package**, select **Do Not Install** to update the dependency only for projects that already include the dependency, or select **Install** to add the dependency to all projects.
5. Click **Next**. The **Get Repository** step is displayed.

   ![docs image](https://dev-assets.cms.uipath.com/assets/images/studio/studio-docs-image-171760-d9ef1ac1.webp)

   * The **All Dependencies** tab displays the list of all packages available on the previously selected feeds.
   * The **Selected Dependencies** tab shows the list of dependencies to be updated in the project.
6. At the **Get Repository** step, select the location of your projects:
   * **Local** - Enter a local path or click **Browse** ![docs image](https://dev-assets.cms.uipath.com/assets/images/studio/studio-docs-image-browse_files-1431ef7d.png) to select one.
   * **GIT** - Enter the repository URL. After you click **Next**, you are prompted to select a branch. If authentication is required, you are also prompted to provide your credentials.
   * **TFS** - Enter the repository URL or click **Browse** ![docs image](https://dev-assets.cms.uipath.com/assets/images/studio/studio-docs-image-browse_files-1431ef7d.png) to connect to a server and browse through TFS projects.
   * **SVN** - Enter the repository URL. For password-protected **SVN** repositories, you are prompted to authenticate with a username and password, if no previous authentication was performed.
7. Click **Next**. The **Filter Projects** step is displayed.

   ![docs image](https://dev-assets.cms.uipath.com/assets/images/studio/studio-docs-image-170073-3a0eb345.webp)
8. In the **Filter Projects** tab, select at least one project from the list by checking the box next to the project name.
9. Click **Next**. The **Commit** step is displayed.

   ![docs image](https://dev-assets.cms.uipath.com/assets/images/studio/studio-docs-image-167913-5115fbd3.webp)
10. In the **Commit** tab, write a message detailing the changes made to project dependencies. To skip this tab, simply select the **Skip Step** check box.
11. Click **Next**. The **Publish** step is displayed.

    ![docs image](https://dev-assets.cms.uipath.com/assets/images/studio/studio-docs-image-170117-7b603939.webp)

    :::note
    The **Commit** tab opens only if you've connected to **GIT**, **SVN**, or **TFS** in the **Get Repository** tab.
    :::
12. In the **Publish** tab, select a location for publishing the modified projects, either Orchestrator, a custom feed or locally. To skip this step, simply click the **Skip Step** check box. Select how the project version increments:
    * **Increment version only** - The project version auto increments.
    * **Increment version to pre-release** - The project version is incremented and is marked as pre-release with a specified suffix (the default suffix is alpha) regardless of its current version.
    * **Increment version to release-ready** - The project version is incremented and is marked as release-ready regardless of its current version.
13. Click **Confirm** to publish the modified project as a `.nupkg` file. The **Results** tab is displayed.

    ![docs image](https://dev-assets.cms.uipath.com/assets/images/studio/studio-docs-image-172460-e31c0887.webp)
14. The **Results** step shows details about the updated dependencies, as well as the projects that failed.

    ![docs image](https://dev-assets.cms.uipath.com/assets/images/studio/studio-docs-image-169077-aca6fddb.webp)

The **Added Dependencies** category shows the updated version of the package, while the **Removed Dependencies** category mentions the previously installed version.