publish a new blog: 2.5 to 2.6 #512
Conversation
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ChelseyZ The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
WalkthroughA new blog post is added at blog/en/how-to-safely-upgrade-from-milvu-2-5-x-to-milvus-2-6-x.md documenting Milvus 2.6 architectural changes (StreamingNode, MixCoord consolidation, separation of streaming vs. batch), feature highlights, and a step-by-step upgrade guide from Milvus 2.5.x. It details upgrade sequencing (StreamingNode → MixCoord → QueryNode → DataNode → Proxy, removal of IndexNode), Helm and Milvus Operator paths, a Milvus CR example, rolling upgrade behavior, commands/snippets (helm/kubectl), compatibility notes, FAQs, and additional resources. Estimated code review effort🎯 1 (Trivial) | ⏱️ ~3 minutes Pre-merge checks and finishing touches✅ Passed checks (3 passed)
✨ Finishing touches🧪 Generate unit tests (beta)
Comment |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 6
🧹 Nitpick comments (1)
blog/en/how-to-safely-upgrade-from-milvu-2-5-x-to-milvus-2-6-x.md (1)
422-422: Remove extra spaces inside link textLine 422 has extra spaces after opening brackets in link syntax, which violates markdown conventions and may affect rendering.
🔎 Proposed fix
-Have questions or want a deep dive on any feature of the latest Milvus? Join our[ Discord channel](https://discord.com/invite/8uyFbECzPX) or file issues on[ GitHub](https://github.com/milvus-io/milvus). You can also book a 20-minute one-on-one session to get insights, guidance, and answers to your questions through[ Milvus Office Hours](https://milvus.io/blog/join-milvus-office-hours-to-get-support-from-vectordb-experts.md). +Have questions or want a deep dive on any feature of the latest Milvus? Join our [Discord channel](https://discord.com/invite/8uyFbECzPX) or file issues on [GitHub](https://github.com/milvus-io/milvus). You can also book a 20-minute one-on-one session to get insights, guidance, and answers to your questions through [Milvus Office Hours](https://milvus.io/blog/join-milvus-office-hours-to-get-support-from-vectordb-experts.md).
📜 Review details
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
blog/en/how-to-safely-upgrade-from-milvu-2-5-x-to-milvus-2-6-x.md
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2025-12-25T12:37:16.088Z
Learnt from: septemberfd
Repo: milvus-io/community PR: 511
File: blog/en/embedding-first-chunking-second-smarter-rag-retrieval-with-max-min-semantic-chunking.md:7-7
Timestamp: 2025-12-25T12:37:16.088Z
Learning: In milvus-io/community blog posts, the front matter 'cover' field does not require the 'https://' protocol prefix. When editing or adding blog markdown files under the blog directory (e.g., blog/en/...), specify cover URLs without the protocol (the blogging system handles protocol-less URLs). This applies to all markdown files in the blog area.
Applied to files:
blog/en/how-to-safely-upgrade-from-milvu-2-5-x-to-milvus-2-6-x.md
🪛 LanguageTool
blog/en/how-to-safely-upgrade-from-milvu-2-5-x-to-milvus-2-6-x.md
[style] ~73-~73: Consider using the synonym “brief” (= concise, using a few words, not lasting long) to strengthen your wording.
Context: ...ing into the upgrade workflow, here’s a quick look at what Milvus 2.6 brings to the t...
(QUICK_BRIEF)
[style] ~125-~125: Consider a more concise word here.
Context: ... to detect the versions of Worker Nodes in order to handle cross-version compatibility with...
(IN_ORDER_TO_PREMIUM)
[grammar] ~318-~318: Ensure spelling is correct
Context: ...grade Milvus to version 2.5.16 or later zand enable MixCoord. ``` mixCoordinator 。 ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
🪛 markdownlint-cli2 (0.18.1)
blog/en/how-to-safely-upgrade-from-milvu-2-5-x-to-milvus-2-6-x.md
33-33: Images should have alternate text (alt text)
(MD045, no-alt-text)
46-46: Images should have alternate text (alt text)
(MD045, no-alt-text)
119-119: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
123-123: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
127-127: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
131-131: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
135-135: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
139-139: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
167-167: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
218-218: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
228-228: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
234-234: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
245-245: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
256-256: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
271-271: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
286-286: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
313-313: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
320-320: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
340-340: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
366-366: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
422-422: Spaces inside link text
(MD039, no-space-in-links)
422-422: Spaces inside link text
(MD039, no-space-in-links)
422-422: Spaces inside link text
(MD039, no-space-in-links)
blog/en/how-to-safely-upgrade-from-milvu-2-5-x-to-milvus-2-6-x.md
Outdated
Show resolved
Hide resolved
| **1. Start the Streaming Node first** | ||
|
|
||
| Start the Streaming Node in advance. The new **Delegator** (the component in the Query Node responsible for streaming data handling) must be moved to the Milvus 2.6 Streaming Node. | ||
|
|
||
| **2. Upgrade MixCoord** | ||
|
|
||
| Upgrade the coordinator components to **MixCoord**. During this step, MixCoord needs to detect the versions of Worker Nodes in order to handle cross-version compatibility within the distributed system. | ||
|
|
||
| **3. Upgrade the Query Node** | ||
|
|
||
| Query Node upgrades typically take longer. During this phase, Milvus 2.5 Data Nodes and Index Nodes can continue handling operations such as Flush and Index building, helping reduce query-side pressure while Query Nodes are being upgraded. | ||
|
|
||
| **4. Upgrade the Data Node** | ||
|
|
||
| Once Milvus 2.5 DataNodes are taken offline, Flush operations become unavailable, and data in Growing Segments may continue to accumulate until all nodes are fully upgraded to Milvus 2.6. | ||
|
|
||
| **5. Upgrade the Proxy** | ||
|
|
||
| After upgrading a Proxy to Milvus 2.6, write operations on that Proxy will remain unavailable until all cluster components are upgraded to 2.6. | ||
|
|
||
| **6. Remove the Index Node** | ||
|
|
||
| Once all other components are upgraded, the standalone Index Node can be safely removed. | ||
|
|
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Convert emphasis to proper markdown headings
Multiple section headers use bold emphasis (**text**) instead of markdown heading syntax (###). This breaks document structure, harms SEO, and impacts accessibility.
All numbered steps in the upgrade sequences (lines 119–142, 218–239, 366–379) and the "Standalone mode" and other subsections should use ### heading syntax:
🔎 Examples of proposed fixes
Lines 119-142 (upgrade order steps):
-**1. Start the Streaming Node first**
+### 1. Start the Streaming Node first
Start the Streaming Node in advance...
-**2. Upgrade MixCoord**
+### 2. Upgrade MixCoord
Upgrade the coordinator components...Lines 218-239 (operator upgrade scenario detection):
-**1. Upgrade Scenario Detection**
+### 1. Upgrade Scenario Detection
During an upgrade, Milvus Operator...
-**2. Rolling Upgrade Execution Order**
+### 2. Rolling Upgrade Execution Order
When a 2.5 → 2.6 upgrade is detected...
-**3. Automatic Coordinator Consolidation**
+### 3. Automatic Coordinator Consolidation
Milvus 2.6 replaces multiple coordinator...Lines 366-379 (MQ choice for deployment modes):
-**1. Standalone mode:** For cost-sensitive...
+### 1. Standalone mode
For cost-sensitive deployments, RocksMQ...
-**2. Cluster mode**
+### 2. Cluster mode
- **Pulsar**...
- **Kafka**...
-**3. Woodpecker (introduced in Milvus 2.6):**
+### 3. Woodpecker (introduced in Milvus 2.6)
Woodpecker removes the need...Also applies to: 218-239, 366-379
🧰 Tools
🪛 LanguageTool
[style] ~125-~125: Consider a more concise word here.
Context: ... to detect the versions of Worker Nodes in order to handle cross-version compatibility with...
(IN_ORDER_TO_PREMIUM)
🪛 markdownlint-cli2 (0.18.1)
119-119: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
123-123: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
127-127: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
131-131: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
135-135: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
139-139: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
🤖 Prompt for AI Agents
In blog/en/how-to-safely-upgrade-from-milvu-2-5-x-to-milvus-2-6-x.md around
lines 119-142, 218-239, and 366-379 (and any “Standalone mode” and related
subsections), replace bold emphasis used as section titles (e.g., "**1. Start
the Streaming Node first**") with proper Markdown headings (e.g., "### 1. Start
the Streaming Node first") so headings are semantically correct and consistent;
ensure each numbered step and subsection uses a consistent heading level (###),
update any bold-only subsection titles to the same heading style, and verify
TOC/anchor links remain valid after the change.
| ``` | ||
| apiVersion: milvus.io/v1beta1 | ||
| kind: Milvus | ||
| metadata: | ||
| name: my-milvus-mansion | ||
| namespace: dev | ||
| spec: | ||
| mode: cluster # cluster or standalone | ||
| # Milvus Components | ||
| components: | ||
| image: milvusdb/milvus:v2.6.5 | ||
| imageUpdateMode: rollingUpgrade | ||
| proxy: | ||
| replicas: 1 | ||
| mixCoord: | ||
| replicas: 1 | ||
| dataNode: | ||
| replicas: 1 | ||
| queryNode: | ||
| replicas: 2 | ||
| resources: | ||
| requests: | ||
| cpu: "2" | ||
| memory: "8Gi" | ||
| # Dependencies, including etcd, storage and message stream | ||
| dependencies: | ||
| etcd: | ||
| inCluster: | ||
| values: | ||
| replicaCount: 3 | ||
| storage: | ||
| type: MinIO | ||
| inCluster: | ||
| values: | ||
| mode: distributed | ||
| msgStreamType: pulsar | ||
| pulsar: | ||
| inCluster: | ||
| values: | ||
| bookkeeper: | ||
| replicas: 3 | ||
| # Milvus configs | ||
| config: | ||
| dataCoord: | ||
| enableActiveStandby: true | ||
| ``` |
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Specify language for YAML code block
Code blocks should declare their language for proper syntax highlighting and readability.
🔎 Proposed fix
-```
+```yaml
apiVersion: milvus.io/v1beta1🧰 Tools
🪛 markdownlint-cli2 (0.18.1)
167-167: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
In blog/en/how-to-safely-upgrade-from-milvu-2-5-x-to-milvus-2-6-x.md around
lines 167 to 212 the YAML code block lacks a language tag which prevents proper
syntax highlighting; add "yaml" immediately after the opening triple backticks
so the block starts with ```yaml and leave the rest unchanged.
blog/en/how-to-safely-upgrade-from-milvu-2-5-x-to-milvus-2-6-x.md
Outdated
Show resolved
Hide resolved
| 2.If the cluster is deployed with multiple coordinator components, first upgrade Milvus to version 2.5.16 or later zand enable MixCoord. | ||
|
|
||
| ``` | ||
| mixCoordinator | ||
| 。 |
There was a problem hiding this comment.
Remove formatting artifact in Helm upgrade section
Lines 318-322 contain a malformed transition between text and code block. Line 321 has "mixCoordinator" and line 322 has "。" on separate lines, which appears to be a copy-paste error.
🔎 Proposed fix
2.If the cluster is deployed with multiple coordinator components, first upgrade Milvus to version 2.5.16 or later and enable MixCoord.
-```
-mixCoordinator
-。
-helm upgrade -i my-release zilliztech/milvus \
+```bash
+helm upgrade -i my-release zilliztech/milvus \Committable suggestion skipped: line range outside the PR's diff.
🧰 Tools
🪛 LanguageTool
[grammar] ~318-~318: Ensure spelling is correct
Context: ...grade Milvus to version 2.5.16 or later zand enable MixCoord. ``` mixCoordinator 。 ...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
🪛 markdownlint-cli2 (0.18.1)
320-320: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
In blog/en/how-to-safely-upgrade-from-milvu-2-5-x-to-milvus-2-6-x.md around
lines 318-322, there is a malformed transition where "mixCoordinator" and a
stray "。" appear between paragraphs and the Helm command; remove those two
artifact lines and replace them with a proper fenced bash code block containing
the Helm upgrade command (helm upgrade -i my-release zilliztech/milvus ...) so
the instructions render correctly and the MixCoord mention remains in the
surrounding text.
There was a problem hiding this comment.
Actionable comments posted: 2
♻️ Duplicate comments (5)
blog/en/how-to-safely-upgrade-from-milvu-2-5-x-to-milvus-2-6-x.md (5)
119-142: Convert emphasis to proper markdown headings.All numbered steps (1–6) use bold emphasis (
**text**) instead of markdown heading syntax (###). This breaks document structure and harms SEO.🔎 Proposed fix for upgrade sequencing steps
-**1. Start the Streaming Node first** +### 1. Start the Streaming Node first Start the Streaming Node in advance... -**2. Upgrade MixCoord** +### 2. Upgrade MixCoord Upgrade the coordinator components... -**3. Upgrade the Query Node** +### 3. Upgrade the Query Node Query Node upgrades typically take longer... -**4. Upgrade the Data Node** +### 4. Upgrade the Data Node Once Milvus 2.5 DataNodes... -**5. Upgrade the Proxy** +### 5. Upgrade the Proxy After upgrading a Proxy... -**6. Remove the Index Node** +### 6. Remove the Index Node Once all other components...
218-239: Convert emphasis to proper markdown headings (rolling upgrades section).Lines 218, 228, and 234 use bold emphasis instead of
###heading syntax.🔎 Proposed fix for rolling upgrade steps
-**1. Upgrade Scenario Detection** +### 1. Upgrade Scenario Detection During an upgrade, Milvus Operator... -**2. Rolling Upgrade Execution Order** +### 2. Rolling Upgrade Execution Order When a 2.5 → 2.6 upgrade is detected... -**3. Automatic Coordinator Consolidation** +### 3. Automatic Coordinator Consolidation Milvus 2.6 replaces multiple coordinator...
364-378: Convert FAQ item headings from emphasis to markdown headings.Lines 364, 366, and 372 use bold emphasis for numbered list items instead of
###heading syntax.🔎 Proposed fix for message queue (MQ) section
-**1. Standalone mode:** For cost-sensitive deployments, RocksMQ is recommended. +### 1. Standalone mode +For cost-sensitive deployments, RocksMQ is recommended. -**2. Cluster mode** +### 2. Cluster mode - **Pulsar** supports... - **Kafka** has a more mature... -**3. Woodpecker (introduced in Milvus 2.6):** Woodpecker removes... +### 3. Woodpecker (introduced in Milvus 2.6) +Woodpecker removes...
167-167: Specify language for YAML code block.🔎 Proposed fix
-``` +```yaml apiVersion: milvus.io/v1beta1
320-322: 🔴 Remove formatting artifacts in Helm upgrade command.Lines 320–322 contain stray
mixCoordinatorand。characters that appear to be copy-paste artifacts. These break the code block and should be removed.🔎 Proposed fix
2.If the cluster is deployed with multiple coordinator components, first upgrade Milvus to version 2.5.16 or later and enable MixCoord. -``` -mixCoordinator -。 -helm upgrade -i my-release zilliztech/milvus \ +```bash +helm upgrade -i my-release zilliztech/milvus \
📜 Review details
Configuration used: Organization UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (1)
blog/en/how-to-safely-upgrade-from-milvu-2-5-x-to-milvus-2-6-x.md
🧰 Additional context used
🧠 Learnings (1)
📚 Learning: 2025-12-25T12:37:16.088Z
Learnt from: septemberfd
Repo: milvus-io/community PR: 511
File: blog/en/embedding-first-chunking-second-smarter-rag-retrieval-with-max-min-semantic-chunking.md:7-7
Timestamp: 2025-12-25T12:37:16.088Z
Learning: In milvus-io/community blog posts, the front matter 'cover' field does not require the 'https://' protocol prefix. When editing or adding blog markdown files under the blog directory (e.g., blog/en/...), specify cover URLs without the protocol (the blogging system handles protocol-less URLs). This applies to all markdown files in the blog area.
Applied to files:
blog/en/how-to-safely-upgrade-from-milvu-2-5-x-to-milvus-2-6-x.md
🪛 LanguageTool
blog/en/how-to-safely-upgrade-from-milvu-2-5-x-to-milvus-2-6-x.md
[style] ~73-~73: Consider using the synonym “brief” (= concise, using a few words, not lasting long) to strengthen your wording.
Context: ...ing into the upgrade workflow, here’s a quick look at what Milvus 2.6 brings to the t...
(QUICK_BRIEF)
[style] ~125-~125: Consider a more concise word here.
Context: ... to detect the versions of Worker Nodes in order to handle cross-version compatibility with...
(IN_ORDER_TO_PREMIUM)
🪛 markdownlint-cli2 (0.18.1)
blog/en/how-to-safely-upgrade-from-milvu-2-5-x-to-milvus-2-6-x.md
119-119: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
123-123: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
127-127: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
131-131: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
135-135: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
139-139: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
167-167: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
218-218: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
228-228: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
234-234: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
245-245: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
256-256: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
271-271: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
286-286: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
313-313: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
320-320: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
340-340: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
366-366: Emphasis used instead of a heading
(MD036, no-emphasis-as-heading)
422-422: Spaces inside link text
(MD039, no-space-in-links)
422-422: Spaces inside link text
(MD039, no-space-in-links)
422-422: Spaces inside link text
(MD039, no-space-in-links)
🔇 Additional comments (1)
blog/en/how-to-safely-upgrade-from-milvu-2-5-x-to-milvus-2-6-x.md (1)
33-33: ✅ Alt text additions are well done.The architecture diagrams now have clear, descriptive alt text that improves accessibility and SEO.
Also applies to: 46-46
| ``` | ||
| # Option 1: Using Helm | ||
| helm upgrade --install milvus-operator \ | ||
| -n milvus-operator --create-namespace \ | ||
| https://github.com/zilliztech/milvus-operator/releases/download/v1.3.3/milvus-operator-1.3.3.tgz | ||
| # Option 2: Using kubectl & raw manifests | ||
| kubectl apply -f https://raw.githubusercontent.com/zilliztech/milvus-operator/v1.3.3/deploy/manifests/deployment.yaml | ||
| ``` |
There was a problem hiding this comment.
🛠️ Refactor suggestion | 🟠 Major
Specify language for all bash/shell code blocks.
Multiple command blocks lack language specification (bash or shell), which reduces syntax highlighting. Add the language tag after opening backticks for all occurrences.
🔎 Examples of proposed fixes
Lines 245-252 (Helm install):
-```
+```bash
# Option 1: Using Helm
helm upgrade --install milvus-operator \Lines 256-267, 271-282, 286-297, 313-316, 340-349: Apply the same pattern.
For example, line 256:
-```
+```bash
kubectl patch milvus my-release...Also applies to: 256-267, 271-282, 286-297, 313-316, 340-349
🧰 Tools
🪛 markdownlint-cli2 (0.18.1)
245-245: Fenced code blocks should have a language specified
(MD040, fenced-code-language)
🤖 Prompt for AI Agents
blog/en/how-to-safely-upgrade-from-milvu-2-5-x-to-milvus-2-6-x.md lines 245-252,
256-267, 271-282, 286-297, 313-316, 340-349: several fenced command blocks are
missing a language specifier which prevents proper syntax highlighting; update
each triple-backtick fence that contains shell/helm/kubectl commands to use
```bash (or ```shell) at the start of the block and keep the closing ``` as-is
so all command blocks include the language tag for proper highlighting.
|
|
||
| With enhanced search capabilities, richer data types, tiered storage, and improved message queue options, Milvus 2.6 is well-positioned to support modern AI applications that require real-time ingestion, high query performance, and efficient operations at scale. | ||
|
|
||
| Have questions or want a deep dive on any feature of the latest Milvus? Join our[ Discord channel](https://discord.com/invite/8uyFbECzPX) or file issues on[ GitHub](https://github.com/milvus-io/milvus). You can also book a 20-minute one-on-one session to get insights, guidance, and answers to your questions through[ Milvus Office Hours](https://milvus.io/blog/join-milvus-office-hours-to-get-support-from-vectordb-experts.md). |
There was a problem hiding this comment.
Remove spaces inside link brackets.
Line 422 has spaces inside markdown link text (e.g., [ Discord channel] should be [Discord channel]). This affects link rendering.
🔎 Proposed fixes
-Have questions or want a deep dive on any feature of the latest Milvus? Join our[ Discord channel](https://discord.com/invite/8uyFbECzPX) or file issues on[ GitHub](https://github.com/milvus-io/milvus). You can also book a 20-minute one-on-one session to get insights, guidance, and answers to your questions through[ Milvus Office Hours](https://milvus.io/blog/join-milvus-office-hours-to-get-support-from-vectordb-experts.md).
+Have questions or want a deep dive on any feature of the latest Milvus? Join our [Discord channel](https://discord.com/invite/8uyFbECzPX) or file issues on [GitHub](https://github.com/milvus-io/milvus). You can also book a 20-minute one-on-one session to get insights, guidance, and answers to your questions through [Milvus Office Hours](https://milvus.io/blog/join-milvus-office-hours-to-get-support-from-vectordb-experts.md).🧰 Tools
🪛 markdownlint-cli2 (0.18.1)
422-422: Spaces inside link text
(MD039, no-space-in-links)
422-422: Spaces inside link text
(MD039, no-space-in-links)
422-422: Spaces inside link text
(MD039, no-space-in-links)
🤖 Prompt for AI Agents
blog/en/how-to-safely-upgrade-from-milvu-2-5-x-to-milvus-2-6-x.md around line
422: the markdown link texts have stray spaces inside the square brackets which
breaks rendering; remove the leading spaces in each link label so "[ Discord
channel]" becomes "[Discord channel]", "[ GitHub]" becomes "[GitHub]", and "[
Milvus Office Hours]" becomes "[Milvus Office Hours]" ensuring no extra spaces
between the opening bracket and the label for all links on that line.
3 participants
Uh oh!
There was an error while loading. Please reload this page.