The default installation and upgrade paths have been updated.

For details, see Upgrade PulseUno.

Because chain plugins now require JRE 11, agents that run on JRE 8 must be upgraded to JRE 11.

To upgrade JRE 8 agents, first uninstall the agents and then run the latest agent installer. For details, see Upgrade PulseUno.

In Git repositories, you can now view Git tags and explore their revision history.

For details, see Browse code.

Create a codeowners file to define trusted users responsible for your product's codebase.

In Git repositories, code owners can be automatically assigned as reviewers to pull requests.

For details, see Define code owners.

You can now create and use generic vaults that support files of any format. For details, see Create and manage vaults.

Files stored in generic vaults are not versioned. If you upload a version of the same file, the new version overwrites the existing file. For details, see Deploy packages.

When working with Maven snapshots, you can now override the vault retention policy for individual snapshot deliveries and choose to keep them forever.

For details, see Review and approve packages.

Create secrets and use them in chains to securely include sensitive details such as usernames and passwords.

For details about creating secrets, see Create and use secrets.

PulseUno uses the master.key file to encrypt all private data in the database, including secrets and credentials for external connections.

Take measures to minimize the risk of losing access to the encrypted data:

• Restrict access to the master.key.

• Create a backup copy of the master.key.

For details on how to safeguard the master.key file and improve PulseUno security, see Secure your PulseUno installation.

Use the alf.events.allowed.cidr system property to specify a list of networks that are allowed to provide ALF events.

For details, see Common system properties.

When you open a product or Git repository, its source control information is now grouped under the Code section on the sidebar:

• Files. Displays a list of files and directories in the product's default stream or branch.

• Branches. Displays a list of product streams or Git repository branches.

• Tags. Displays a list of Git tags in the Git repository.

• Graph. Displays the product's changeset graph.

• Changesets. Displays the product's changeset history.

For details on how to browse the contents of streams, branches, and Git tags, see Browse code.

When your session times out, you now have the option to re-log in and get to the page where you left off.

To change the session timeout, edit the PulseUno server's startup.properties file. For details, see Configure startup.properties.

When you choose to keep a chain run forever, you can also keep the artifacts deployed during the chain run.

For details, see View chain runs.

You can configure a chain to ignore the chain run state when estimating the state of related changesets. This way, if the chain run fails, the chain's failed state doesn't cause the changesets to fail.

For details, see Set chain options.

PulseUno now supports the SARIF output format for code scanning. When running static code analysis, use the new SARIF File Parser plugin to process the contents of SARIF files and convert them into findings.

For details, see SARIF file parser.

To run the SonarQube plugin, you no longer need to create the sonarqube-pulse-expert.properties file. Set the properties directly in the user interface.

For details, see SonarQube.

When auditing the history of your PulseUno instance, you can now filter the event list by Entity Type > Secret to view the history for secrets.

For details, see View global history.

You can run a chain that integrates Fortify static code analysis into a GitHub Actions workflow and generates findings from a SARIF file.

For details, see Fortify on Demand GitHub Actions.

When sending chain run results to ALM Octane, you can now pass a comment with the build link to all ALM Octane work items associated with the build.

For details, see Publish chain results to ALM Octane.

If a Dimensions CM repository uses multiple providers, you can now view requests from each provider, including native Dimensions CM requests:

• To view a list of requests by provider, open the Catalog.

• To view your pending requests by provider, open the Inbox in the My Work area.

For details, see View requests.

You can now change team and member roles for a Dimensions CM product. The role defined for a product overrides the default role inherited from the product's space.

Note: PulseUno roles apply only to PulseUno objects, such as chains or PulseUno settings.

For details, see Manage members and teams.

Use the new Agile option to display or hide the Backlogs and Iterations sections in the user interface.

In a Dimensions CM product, the Agile view includes request backlogs and iterations by default. For details, see Agile request management.

In a Git repository, you can choose to display backlogs and iterations for a Dimensions CM request provider. For details, see Enable Dimensions CM requests.

Note: In products that use multiple request providers, backlogs and iterations are supported for Dimensions CM requests only.