• Java Runtime Environment (JRE) upgraded to version 11.0.

• Common Tomcat upgraded to version 9.0.

For upgrade instructions, see Upgrade PulseUno.

PulseUno no longer provides an embedded agent. You need to install at least one agent for each PulseUno instance.

For details, see Install agents.

Branch policies now provide additional protections: 

• Restricting users from pushing to a branch.

• Allowing commits only from specified emails.

For details, see Define branch policies.

To enable other products and Git repositories to run chains in your Git repository or fetch content from it, define these products as trusted.

For details, see Define trusted products for Git repository.

PulseUno now integrates with Python PIP package manager. Use Python vaults to store and retrieve PyPI packages.

For details, see Create and manage vaults.

To enable products or Git repositories to deploy packages to your vault, define these products as trusted.

Only chains from trusted products can access your vault and deploy artifacts to it.

For details, see Define trusted products for vault.

Read-only vaults

To prevent packages from being deployed to a vault, you can make the vault read-only. Remote vaults are read-only by default.

For details, see Create and manage vaults.

PulseUno now always keeps the latest version of any package in a vault, regardless of the retention policy.

Maven vaults: For a Maven snapshot, which is the type of package version that can be delivered multiple times, the retention policy applies to snapshot deliveries the same way it applies to package versions. For example, if your retention policy is set to retain 3 items, PulseUno will keep 3 versions of each Maven package and 3 deliveries of each Maven snapshot.

For details, see Create retention policies.

As an administrator or vault owner, you can bypass the package approval process and instantly approve or reject packages that are pending approval.

For details, see Review and approve packages.

Use the new filtering and viewing options on the Chains page:

• Hide disabled chains and/or chains without runs.

• Switch to compact mode to collapse information about each chain.

For details, see View and share chains.

When publishing or merging a pull request, you can now update the pull request's description, relate the request, and change the target stream/branch to merge to.

You can add reviewers even after you publish the pull request.

For details, see Publish pull requests.

A vault's Activity feed now contains information about vault packages and files removed by your retention policy.

For details, see View activity.

You can now use emojis and checkbox lists in comments, descriptions, and notes.

PulseUno supports the CommonMark 0.30 specification of Markdown.

For details, see Markdown syntax reference.

Changeset history now includes a vertical graph with changeset health indicators and tooltips.

For details, see View changeset history.

You can now view package information, such as the size of the package version, the user who deployed the package, and the time the package was deployed.

The Conversation tab also includes a link to the chain run that deployed the package.

You can sort and search for files in a package.

Maven vaults: For Maven snapshots, files are now grouped by their delivery date and displayed as a tree of nodes, or snapshot deliveries. You can delete snapshot deliveries except the latest one.

For better visibility, each vulnerability is displayed as a set of vulnerability parameters and is color-coded to indicate the severity level.

Measurements for each plugin step are displayed as a table with easy-to-read measurement counts.

You can now set global variables and use them across multiple chains and chain steps.

For details, see Define chain and global variables.

To help you securely deploy to a vault, PulseUno provides a set of temporary system credentials. Use these variables in your build scripts to authenticate to a vault when deploying packages to it.

For details, see Built-in variables.

For optimal performance, an agent now runs one chain at a time.

For details, see Manage agents.

If your chain is configured to run another chain, you can set the parent chain to wait for the child chain to finish. This way, the parent chain can take account of the child chain's result before it continues running.

For details, see Configure chains to run other chains.

Git repositories now support the synchronization of PulseUno reviews and pull requests with ALM Octane work items.

For details, see Synchronize with ALM Octane work items.

• If a Dimensions CM repository integrates with multiple request providers, such as ALM Octane or Atlassian Jira, you can work with tasks and issues from those providers in PulseUno.

  For details about external requests in Dimensions CM, see the Dimensions CM help.

• You can now specify a Sync user for synchronizing Git branches with Dimensions CM streams.

  For details, see Connect to Dimensions CM repository.

You can now install and use PulseUno as part of StarTeam.

The StarTeam 17.3 installer includes PulseUno 22.1.

For details, see the StarTeam help.

The Administration section has moved next to Search at the top right.

To access the administration area, click Administration .

For details, see Navigate PulseUno.

To help you diagnose possible issues with the system, PulseUno provides access to system properties directly in the user interface.

In the Administration section, you can now change and reset system properties. For example, you can update the system's default display language or the number of chains an agent can run at one time.

For details, see Set system properties.