Product | Update | Details |
|---|---|---|
Platform | New Platform Security APIs | These new Security APIs replace the previous Security APIs, which are planned to be deprecated at a later stage. The new APIs address aspects of JFrog Platform security and access, such as users, groups, permissions, tokens, and more. For more information, see Security REST APIs. |
Platform-specific REST APIs Moved to a Dedicated Page | All REST APIs that are not specific to Artifactory - but are relevant to the JFrog Platform as a whole - have been moved to their own documentation page called JFrog Platform REST API. Here you will find all the APIs that were previously on the Artifactory page, including Security, System and Configuration, Support, Access, Projects, Router, and Webhooks. You will also find links from the existing Artifactory API page to the relevant sections in the new page. | |
npm Deprecation Flow Improvements | Simplified the npm deprecation handling flow - npm deprecations will now be reflected in the package.json file, and the npm client will return an appropriate error in the case of lacking permissions (note that if you have a large number of deprecated npm packages, upgrading Artifactory will cause Artifactory to start with a few seconds delay). | |
Binary Management | Federated Repository Multi-Version Support | Multi-version support enables the members of a Federation to run different versions of Artifactory, even if the version at one site includes configuration features and values that are not supported on the versions running at other sites. Thanks to multi-version support, future upgrades after Artifactory 7.49.3 can be performed on one site at a time, eliminating the need for simultaneous upgrades across all locations.Whenever an instance with a new Artifactory version is introduced to the Federation, the configurations of the other members are retrieved and a negotiation process checks for new and upgraded features that are not supported on the older versions. If there are new features that older versions do not support, the new feature is disabled. For upgraded features, a default value is chosen that is supported on all member versions. Multi-version support requires Artifactory 7.49.3 and above. Therefore, it is a prerequisite of this feature to upgrade all Federated repository members to Artifactory 7.49.3. After this has been done, multi-version support is enabled for all versions going forward. |
Federated Repository Monitoring | This new feature enables you to monitor the status of Federated repositories using a set of dedicated REST APIs. Use these APIs to get the status of the Federation for a specific repository, including task status, pending event status, server lag time, and the number of fully (binary and metadata) and artificially (metadata only) replicated artifacts. In addition, you can use these APIs to get a list of Federation mirror lag times and a list of unsynchronized mirrors.The new monitoring features become available after the one-time database optimization process (which is part of the upgrade to this version) is complete. | |
CI/CD | New Variable for SCM Repository Name | A new variable, {{ sourceRepository }}, has been introduced to replace the SCM repository full path during Pipelines sync. |
New OOTB Global Template | A new template to promote a BuildInfo resource is now available out of the box. | |
Support for Multiple Operating Systems in Matrix Step | In the matrix native step, steplets can now be configured to execute in parallel on multiple node pools with different operating systems. | |
New Custom Views | Non-admin users can now create custom personal views for pipelines using simple wildcard patterns on pipelines name or branch name. Up to five views can be created per Project. | |
Ability to Add Description | A new utility function, update_run_description, has been introduced, which can be used to add custom text to every run. This is useful for providing more context for a run. The run description can be updated at any time. | |
View Git Repo Event for Runs | The Overview section in the Pipelines UI will now show the git repo event (such as, commit details, pull request details, tag details) that triggered the run, along with a link to the commit SHA. | |
New Status Icons | The Active Runs, Node Pools, and Extensions Templates pages now use new Status icons. |