> For the complete documentation index, see [llms.txt](https://docs.catalyx.solutions/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.catalyx.solutions/catalyx-package-manager/release-notes.md). # Release Notes
Version 2.1 Building on the public package management capabilities introduced in version 2.0, CPM 2.1 introduces private package distribution, flexible artifact management, and enhanced user engagement through subscriptions and notifications. ### What’s new?
* **Private Packages & Access Management** Users can now publish private packages, restricting access to authorized users only. Package owners can manage access requests through a dedicated interface, with the ability to approve, deny, or revoke access. Users can request access directly from the Registry, and once approved, packages become available in their library.
* **DAR file artifactory hosting** CPM 2.1 provides flexibility in how DAR files are stored and distributed. Users will have an option of choosing to host the file directly within CPM, ensuring it is fully managed and secured by the platform, or provide an artifactory hosting link if preferred. This option will allow teams to maintain existing infrastructure practices while benefiting from CPM’s management and distribution features.
* **"My Packages" becomes "My Library"** *My Packages* evolves into My Library, a centralized space where users can manage both Published and Retrieved packages, providing a complete view of what they own and consume.
* **Subscriptions & Notifications** Users can now subscribe to packages and publishers and receive updates when: * New versions are released * Access to private packages are granted or revoked * Packages/ package versions are deleted\ \ Notifications are available through email and are managed through a dedicated Notifications tab.
* **Improved Onboarding Experience** The onboarding flow has been simplified to reduce friction, including: * Removal of initial billing requirements * Streamlined registration steps * Improved validation and input handling * Removed mandatory docusign step * **CatalyX-branded UI** The CPM console is updated alongside the broader CatalyX rebrand (catalyx.solutions)
Version 2.0 Building on the UI-driven sign-up flow introduced in the previous release, CPM now enables users to publish and manage public packages directly through the UI. Users can manage their published packages in a dedicated My Packages section and explore all public packages in the Marketplace, with clear visibility into package details, versions, and available actions. This unified experience allows users to efficiently manage, share, and monitor their software artifacts. #### What’s new * **My Packages** – In addition to the existing Marketplace, My Packages provides a personal workspace where users can view and manage all packages they have published. This section serves as the central hub for a user’s package lifecycle, giving quick access to management actions such as viewing package metadata, creating new versions, or removing packages. The Marketplace remains a comprehensive catalog of all published public packages, allowing users to explore packages shared by other users or teams, search, filter by type or status, sort, and download public packages, with full visibility into package details and versioning, giving users confidence in selecting and using the right packages for their needs.
* **Publish New Public Package** - Users can now create and publish new public packages through the CPM UI, an improvement over the previous CLI-only workflow. Users are guided to provide all required information, including application name, description, version, type, and Artifactory links. This workflow ensures packages are consistently documented, discoverable, and ready for distribution in the Marketplace. * **Public Package Management** – A set of actions for managing existing packages, including editing package details, downloading packages, or removing them from My Packages and, by extension, the Marketplace. This functionality gives users control over package content, access, and lifecycle while maintaining a clear and auditable record of all changes. * **Package Versioning** – The ability to create new versions of existing packages while keeping previous versions intact and accessible. Users can update package content, metadata, and links for new releases without affecting older versions, ensuring continuity and traceability across the lifecycle of the package. * **Package Version History** – A dedicated view that lists all versions of a package, showing details such as version number, type, and associated metadata. Users can review previous versions, manage version-level actions (edit, download, delete), and maintain a clear history of package evolution. This view supports governance, auditing, and informed decision-making when updating or using packages. #### Coming soon The CPM 2.1 release will introduce several key enhancements aimed at increasing control, governance, and flexibility for users managing software packages. This release will bring support for private packages with full access management, enhanced package auditing capabilities, and the option to host DAR files directly within CPM or via external links. These features give users more control over package distribution, secure access, and compliance while streamlining workflows for both publishers and consumers. * **Private Packages & Access Management** – Users will be able to publish packages privately, restricting visibility and download access to authorized individuals. The system will provide a dedicated workflow for managing access, allowing package owners to review incoming access requests, approve or deny requests, and maintain a clear record of who has access. This will ensure that sensitive or internal packages are securely managed while still enabling controlled collaboration. * **Requesting Access** – For packages marked as private, users without access will be able to submit a request for approval through the Marketplace. The request will be sent to the package publisher, who can review the requester’s Party ID and grant or deny access. This process will ensure that private packages remain secure while providing a clear and auditable mechanism for users to request access. * **DAR Files Artifactory Hosting** – CPM 2.1 will provide flexibility in how DAR files are stored and distributed. Users will have an option of choosing to host the file directly within CPM, ensuring it is fully managed and secured by the platform, or provide an artifactory hosting link if preferred. This option will allow teams to maintain existing infrastructure practices while benefiting from CPM’s management and distribution features.
Version 1.1 CPM 1.1 introduces the full CPM onboarding experience directly in the UI, significantly simplifying the process of registering and preparing a Canton validator node for participation in the CatalyX ecosystem. This is the first step toward a fully UI-driven CPM experience, laying the foundation for the upcoming CPM 2.0 release. In addition, this release includes a new Top-Up Management page that allows users to pre-allocate operating funds through an intuitive visual interface. #### What’s new * **Full UI Onboarding Flow** – CPM 1.1 now supports the complete onboarding workflow within the UI. This eliminates much of the manual setup previously required through the CLI. * **Check out the onboarding guide** [**here**](https://docs.catalyx.solutions/cpm/1.1/CPM/onboarding-guide.html) * **Top-Up Management** – A new Top-Up Guide and Management interface has been added to help users allocate funds * **Check out the Top-up management guide** [**here**](https://docs.catalyx.solutions/cpm/1.1/CPM/top-up-guide.html) #### Coming soon CPM 2.0, will introduce full UI support for all [CPM functionalities](https://docs.catalyx.solutions/cpm/1.1/CPM/installation-instructions.html) currently available only via CLI.
Version 1.0 #### What’s new * **Initial CLI Release** – The first version of CatalyX Package Manager (CPM) introduces a powerful Command Line Interface (CLI) tool that allows developers to interact with the Canton ecosystem and manage app packages directly from the terminal. * **App Publishing and Listing** – App Builders can now publish applications to the CPM registry and list existing packages in the network. This facilitates sharing and discovery of reusable application components across entities within the Canton ecosystem. * **Access Control Management** – App Builders can define and manage access permissions for each of their published apps, controlling who can access, download, or audit the packages. * **Access Request Workflow** – Users can request access to apps published by others, enabling secure and auditable collaboration between Canton participants. * **Audit Request Feature** – Builders can request external entities to audit their packages, supporting regulatory compliance and security best practices. #### Coming soon * **Web-Based User Interface** – An upcoming release of CPM will introduce a standalone UI, allowing users to interact with packages through a visual interface. * **Integration with CatalyX Blockchain Manager** – In future versions, CPM will be fully integrated into the CatalyX Blockchain Manager UI, enabling unified app management and governance within the broader CatalyX platform.
--- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.catalyx.solutions/catalyx-package-manager/release-notes.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.