Doc: 1.8.0 Release Updation (#21925)

Co-authored-by: “Rounak <“rounakpreet.d@deuexsolutions.com”>
Co-authored-by: Prajwal214 <167504578+Prajwal214@users.noreply.github.com>
This commit is contained in:
Rounak Dhillon 2025-06-24 18:30:15 +05:30 committed by GitHub
parent 11ac56356b
commit 51b12c40bb
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
7 changed files with 59 additions and 21 deletions

View File

@ -0,0 +1,16 @@
# 1.7.5 Release 🎉
{% note noteType="Tip" %}
**June 20th, 2025**
{% /note %}
You can find the GitHub release [here](https://github.com/open-metadata/OpenMetadata/releases/tag/1.7.5-release).
## Fixes
- Lineage expand collapse nodes.
- Default boost score and improve fqn parsing.
- OpenSearch by default limits the number of characters, if the field is very large then the limit gets exceeded.
- Handled spaces in database, schema, table, and column names across all connectors for reverse metadata.
**Full Changelog**: [link](https://github.com/open-metadata/OpenMetadata/compare/1.7.4-release...1.7.5-release)

View File

@ -1,7 +1,7 @@
# 1.7.5 Release 🎉
# 1.8.0 Release 🎉
{% note noteType="Tip" %}
**20th June 2025**
**24th June 2025**
{% /note %}
{% inlineCalloutContainer %}
@ -10,19 +10,37 @@ color="violet-70"
icon="celebration"
bold="Upgrade OpenMetadata"
href="/deployment/upgrade" %}
Learn how to upgrade your OpenMetadata instance to 1.7.5!
Learn how to upgrade your OpenMetadata instance to 1.8.0!
{% /inlineCallout %}
{% /inlineCalloutContainer %}
You can find the GitHub release [here](https://github.com/open-metadata/OpenMetadata/releases/tag/1.7.5-release).
You can find the GitHub release [here](https://github.com/open-metadata/OpenMetadata/releases/tag/1.8.0-release).
# What's New
## Fixes
OpenMetadata MCP Server — Generative-AI-Ready Metadata with Rich Context
- Lineage expand collapse nodes.
- Default boost score and improve fqn parsing.
- OpenSearch by default limits the number of characters, if the field is very large then the limit gets exceeded.
- Handled spaces in database, schema, table, and column names across all connectors for reverse metadata.
OpenMetadata 1.8 introduces an enterprise-grade MCP (Metadata Context Provider) server, built natively on our unified knowledge graph. This new service delivers a single, high-performance API layer that empowers any Large Language Model—or any downstream application—to access rich, policy-aware context about your data in real time.
**Full Changelog**: [link](https://github.com/open-metadata/OpenMetadata/compare/1.7.4-release...1.7.5-release)
## Key highlights:
- One graph, one endpoint: The MCP server exposes every entity, relationship, data quality metric, lineage detail, and governance rule youve curated in OpenMetadata.
- LLM-optimized responses: JSON schemas are tailored for semantic search and RAG workflows, enabling chatbots and copilots to ground their answers in accurate, up-to-date metadata.
- Enterprise-grade insights: Gain real-time KPIs on asset distribution, metadata coverage (descriptions, ownership), tiering, and PII tagging to strengthen data governance.
- Zero-friction adoption: It comes bundled with OpenMetadata—just enable the service, generate an API key, and start querying from Claude, Cursor, ChatGPT, and more.
With MCP, every data consumer—from BI analysts to autonomous agents generating SQL—can instantly understand tables, lineage, quality, and ownership without leaving their workflow.
## SCIM Provisioning for Okta & Azure AD — Hands-Free User & Group Management (Collate Only)
Collate 1.8 expands our SSO capabilities with native SCIM 2.0 support for Okta and Azure Active Directory. Now, enterprises can manage the full user lifecycle directly from their Identity Provider—no more CSV uploads or manual role assignments.
Key benefits:
- Automated onboarding & offboarding: The Tier Agent continuously analyzes usage patterns and lineage to highlight your most critical data assets.
- Consistent governance: The Documentation Agent generates accurate asset descriptions and powers seamless Text2SQL chat experiences.
- Standards-based interoperability: Built on the SCIM spec, making it easy to extend to other IdPs like JumpCloud, OneLogin, and more.
Together with existing SAML/OIDC SSO, SCIM provisioning completes a turnkey identity stack—giving security teams peace of mind while enabling effortless access for data users.
**Full Changelog**: [link](https://github.com/open-metadata/OpenMetadata/compare/1.7.5-release...1.8.0-release)

View File

@ -101,7 +101,7 @@ This docker compose file contains only the docker compose services for OpenMetad
You can also run the below command to fetch the docker compose file directly from the terminal -
```bash
wget https://github.com/open-metadata/OpenMetadata/releases/download/1.7.5-release/docker-compose-openmetadata.yml
wget https://github.com/open-metadata/OpenMetadata/releases/download/1.8.0-release/docker-compose-openmetadata.yml
```
### 3. Update Environment Variables required for OpenMetadata Dependencies
@ -195,7 +195,7 @@ You can validate that all containers are up by running with command `docker ps`.
```commandline
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
470cc8149826 openmetadata/server:1.7.5 "./openmetadata-star…" 45 seconds ago Up 43 seconds 3306/tcp, 9200/tcp, 9300/tcp, 0.0.0.0:8585-8586->8585-8586/tcp openmetadata_server
470cc8149826 openmetadata/server:1.8.0 "./openmetadata-star…" 45 seconds ago Up 43 seconds 3306/tcp, 9200/tcp, 9300/tcp, 0.0.0.0:8585-8586->8585-8586/tcp openmetadata_server
```
In a few seconds, you should be able to access the OpenMetadata UI at [http://localhost:8585](http://localhost:8585)

View File

@ -1132,6 +1132,8 @@ site_menu:
url: /releases/supported
- category: Releases / All Releases
url: /releases/all-releases
- category: Releases / All Releases / 1.7.5 Release
url: /releases/all-releases/#1.7.5-release
- category: Releases / All Releases / 1.7.4 Release
url: /releases/all-releases/#1.7.4-release
- category: Releases / All Releases / 1.7.3 Release

View File

@ -119,15 +119,15 @@ The latest version is at the top of the page
You can use the curl or wget command as well to fetch the docker compose files from your terminal -
```commandline
curl -sL -o docker-compose.yml https://github.com/open-metadata/OpenMetadata/releases/download/1.7.5-release/docker-compose.yml
curl -sL -o docker-compose.yml https://github.com/open-metadata/OpenMetadata/releases/download/1.8.0-release/docker-compose.yml
curl -sL -o docker-compose-postgres.yml https://github.com/open-metadata/OpenMetadata/releases/download/1.7.5-release/docker-compose-postgres.yml
curl -sL -o docker-compose-postgres.yml https://github.com/open-metadata/OpenMetadata/releases/download/1.8.0-release/docker-compose-postgres.yml
```
```commandline
wget https://github.com/open-metadata/OpenMetadata/releases/download/1.7.5-release/docker-compose.yml
wget https://github.com/open-metadata/OpenMetadata/releases/download/1.8.0-release/docker-compose.yml
wget https://github.com/open-metadata/OpenMetadata/releases/download/1.7.5-release/docker-compose-postgres.yml
wget https://github.com/open-metadata/OpenMetadata/releases/download/1.8.0-release/docker-compose-postgres.yml
```
### 3. Start the Docker Compose Services
@ -166,10 +166,10 @@ You can validate that all containers are up by running with command `docker ps`.
```commandline
docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
470cc8149826 openmetadata/server:1.7.5 "./openmetadata-star…" 45 seconds ago Up 43 seconds 3306/tcp, 9200/tcp, 9300/tcp, 0.0.0.0:8585-8586->8585-8586/tcp openmetadata_server
63578aacbff5 openmetadata/ingestion:1.7.5 "./ingestion_depende…" 45 seconds ago Up 43 seconds 0.0.0.0:8080->8080/tcp openmetadata_ingestion
470cc8149826 openmetadata/server:1.8.0 "./openmetadata-star…" 45 seconds ago Up 43 seconds 3306/tcp, 9200/tcp, 9300/tcp, 0.0.0.0:8585-8586->8585-8586/tcp openmetadata_server
63578aacbff5 openmetadata/ingestion:1.8.0 "./ingestion_depende…" 45 seconds ago Up 43 seconds 0.0.0.0:8080->8080/tcp openmetadata_ingestion
9f5ee8334f4b docker.elastic.co/elasticsearch/elasticsearch:7.16.3 "/tini -- /usr/local…" 45 seconds ago Up 44 seconds 0.0.0.0:9200->9200/tcp, 0.0.0.0:9300->9300/tcp openmetadata_elasticsearch
08947ab3424b openmetadata/db:1.7.5 "/entrypoint.sh mysq…" 45 seconds ago Up 44 seconds (healthy) 3306/tcp, 33060-33061/tcp openmetadata_mysql
08947ab3424b openmetadata/db:1.8.0 "/entrypoint.sh mysq…" 45 seconds ago Up 44 seconds (healthy) 3306/tcp, 33060-33061/tcp openmetadata_mysql
```
In a few seconds, you should be able to access the OpenMetadata UI at [http://localhost:8585](http://localhost:8585)

View File

@ -14,6 +14,8 @@ version. To see what's coming in next releases, please check our {% collateConte
{% partial file="/v1.8/releases/latest.md" /%}
{% partial file="/v1.8/releases/1.7.5.md" /%}
{% partial file="/v1.8/releases/1.7.4.md" /%}
{% partial file="/v1.8/releases/1.7.3.md" /%}

View File

@ -12,10 +12,10 @@ We are now going to present a high-level Python API as a type-safe and gentle wr
The Python SDK is part of the `openmetadata-ingestion` base package. You can install it from [PyPI](https://pypi.org/project/openmetadata-ingestion/).
Make sure to use the same `openmetadata-ingestion` version as your server version. For example, if you have the OpenMetadata
server at version 1.7.5, you will need to install:
server at version 1.8.0, you will need to install:
```python
pip install "openmetadata-ingestion~=1.7.5.0"
pip install "openmetadata-ingestion~=1.8.0.0"
```
{% /note %}