# July - 2023

This latest product update for [Ozone](http://ozone.one/) – **1.2.14** brings in six major features and enhancements along with a few fixes and improvements based on our user feedback. For context on the previous months, you can refer to our previous release notes [here](https://www.ozone.one/release-notes/).&#x20;

The following is the summary of what you can find in this release:

1. **Ozone plugin for Backstage:** Backstage is an open platform for building developer portals. It is an ecosystem of plugins that helps make a developer’s life easy by helping build a central place for an organization’s tools, resources, and documentation. Backstage provides developers with a framework along with a wide range of plugins for integrating all their tools, such as Source Code Platforms, Security (SAST & DAST) tools, and everything else outside of their repo and IDE.

In this release, Ozone provides a Backstage plugin that can be added to the Backstage instance. Basic deployments with support for GitHub, GitLab, Harbor, and DockerHub can be performed with Ozone as they are available for the Backstage community to be leveraged along with their existing toolchains. Other features like Ozone’s CI/CD can also be used directly from within the developer’s developer portal.&#x20;

**Accounts Manager for service providers:** As the name suggests, the Ozone Accounts Manager helps administrators and Ozone partners to set up new control planes for individual or combined instances of Ozone on Kubernetes clusters. They can create and map them to specific regions as per their use cases. The control plane metadata can be filtered as well for better visibility and control.&#x20;

**Ozone API & CLI for third-party integrations:** This release also features a refreshed catalog of Ozone APIs and CLIs to facilitate integrations with major tools and frameworks necessary across CI/CD, making it easier to orchestrate and automate DevOps with Ozone being the single source of truth for everything DevOps.&#x20;

**Resource imports within projects**: Just like many mainstream CI/CD and DevOps platforms, Ozone uses “Projects” as the anchor to segregate teams, microservices, infrastructure, etc. However, unlike other platforms, Ozone also gives the flexibility to import resources from one project to another with just a few clicks, making collaboration easier while still retaining a structure to your teams, infrastructure, and projects.&#x20;

&#x20;**Deep-linking of pipelines and releases:** Users can share the pipeline and release run views via Slack with a link. It then opens up the run views and preserves the context, thus making pipeline and release insights sharable with relevant stakeholders.

Other minor fixes:

1. Webhook edits: Users can modify webhooks on the go to facilitate pipeline triggers based on the webhook type rather than creating and duplicating webhooks.&#x20;
2. Though Ozone ships with numerous pre-configured pipelines, users can still edit them or their self-authored pipelines by creating a clone of the same.

<br>


---

# Agent Instructions: 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.ozone.one/ozone-end-user-guide/release-notes/july-2023.md?ask=<question>
```

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.