• Modified applications can now be tagged automatically (i.e. on-the-fly) when triggering a pipeline. To activate this feature, Site Property 'Feature_AutoTagging' must be enabled;
• It is now possible to re-trigger a pipeline by bypassing the check for new application versions. To activate this feature, Site Property 'Feature_ForceTriggerPipeline' must be enabled;
• Revamped UX in 'Trigger Details' screen and general UI improvements (Kudos to Pedro Cardoso);
• Improved error messages when invoking the configured pipeline server to trigger a pipeline;
• Added version number to plugin name label in top-right corner of plugin screens.

NOTE: Since the AutoTagging feature relies on the LifeTime Deployment API, a valid service account token must be provided (as a Site Property) and the correct API endpoint must be specified in the 'Integrations' tab in Service Center.

• Added Site Property to control if a Jenkins Crumb (i.e. CSRF protection token) should be requested prior to triggering a Jenkins pipeline.

IMPORTANT NOTE: From Jenkins version 2.176.3 onward, authentication of requests to Jenkins Remote API using username/password credentials is no longer supported. Instead of the user password you should provide an API token when configuring the 'Pipeline Server Credentials' field.

• Support for triggering pipelines in Azure DevOps (including both 'Build' and 'Release' pipeline types);
• It is now possible to define a default pipeline server configuration, which can be overridden for each trigger configuration.