Updating packages

You can get the latest changes made to a package from the external repository.

About this task

Key points to consider for successful packages uploads.
  • You cannot have different versions of the same package between projects that are hosted in the same runtime. You can choose to upgrade the version of a package during an import, but this action also updates all other projects to that version. After an upgrade, you can revert to a previous version.
  • Updates to any dependent packages are not yet supported.
  • Modifying the project package assets outside of the web tools is not recommended when using an external Git repository. The only exception being assets that are not directly editable from the webMethods cloud tools such as the README.md or GitHub actions. Any external changes can be pulled into the package by using the Pull button that is provided in the Package Details view. Any local changes that are not yet committed get overwritten.

Procedure

  1. Go to Projects and select a project.
  2. Click Packages.
    The Packages page is displayed listing packages that are already added to the project.
  3. Click the package that you want to update.
    The Package Information page is displayed listing the Git details.
  4. In Git branch/tag, select a particular branch or tag of the repository to use as the source for the package.
  5. Pull the latest changes from the repository.
    1. In the Git branch/tag drop-down menu, select a particular branch or tag of the repository to use as the source for the package.
    2. Click Pull.
  6. Optional: If you want to associate a dedicated Git account directly with a package, then update the Git account. Any Git account update applies only to the current package being edited and does not affect other packages or projects.
    1. Click Edit beside the Git account name. The Update Git Account dialog is displayed listing all accounts associated with the same Git provider as the existing account. For example, if the existing account is from github.com, all GitHub accounts with valid authentication tokens are displayed. Also, only accounts with valid token status are displayed.
    2. In Source Control, select the Git account name that you want to link to the package.
      The Git accounts that you own or shared are displayed. You can add a new Git account by clicking Add
      .The Git account details are updated. The Git account updates are applicable only to the current project. If either the token validation fails or access to the repository is denied, the update does not happen.

Results

The package is updated with the most recent changes available in the repository. The assets such as flow anywhere services, connectors, and any other artifacts that are associated with the package can now be used in your project.