langgenius/dify-plugins
1
0
Fork 0
mirror of https://github.com/langgenius/dify-plugins.git synced 2026-07-22 01:55:36 -04:00
Code Issues 119 Packages Projects Releases Wiki Activity

[PR #1875] [MERGED] feat(markdown-chunker): update to v2.1.7 #1921

New Issue
Closed
opened 2026-02-22 18:11:44 -05:00 by yindo · 0 comments
yindo commented 2026-02-22 18:11:44 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/langgenius/dify-plugins/pull/1875
Author: @asukhodko
Created: 1/10/2026
Status: ✅ Merged
Merged: 1/11/2026
Merged by: @crazywoola

Base: main ← Head: main

📝 Commits (1)

  • 41932b8 feat(markdown-chunker): update to v2.1.7

📊 Changes

1 file changed (+0 additions, -0 deletions)

View changed files

➕ asukhodko/markdown-chunker-2.1.7.difypkg (+0 -0)

📄 Description

Plugin Submission Form

1. Metadata

2. Submission Type

  • New plugin submission
  • Version update for existing plugin

3. Description

This PR bumps markdown_chunker from v2.1.4 → v2.1.7.

The big story in this version range: the plugin has been migrated from the previously embedded markdown_chunker_v2 implementation to the external chunkana library (the plugin is now an integration layer that maps Dify Tool params → chunkana config and formats the output for KB/RAG use).

What’s included in v2.1.7 (v2.1.4...v2.1.7)

Chunkana-powered engine + repo cleanup

  • Removed the embedded chunking implementation (markdown_chunker_v2/ and legacy markdown_chunker/) from the plugin repo.
  • Added a migration compatibility layer:
    • adapter.py (param mapping + boundary-invariant chunking + output rendering),
    • input_validator.py (input/metadata normalization),
    • output_filter.py (hierarchy/debug filtering and indexable-oriented output shaping).

Docs refreshed to match the new architecture

  • README + docs were updated heavily to reflect the new “powered by chunkana” reality:
    • updated usage/quickstart/configuration/strategies/API docs,
    • added a dedicated migration guide: docs/guides/migration-to-chunkana.md,
    • removed legacy Stage1 / markdown_chunker_v2 docs and examples.
  • Docs now clearly explain:
    • include_metadata as an output-format choice (boundaries don’t depend on it),
    • hierarchy behavior (enable_hierarchy, leaf_only, debug) and how it affects what chunks are returned.

Metadata/marketplace descriptions

  • manifest.yaml and provider/markdown_chunker.yaml descriptions were updated (all locales) to explicitly mention chunkana as the underlying engine.

Testing / dev housekeeping

  • Test suite and fixtures were refactored to focus on migration/backward-compatibility baselines (new fixtures + golden snapshots).
  • Added run_test.sh, updated pytest.ini, and cleaned up old demo/validation scripts.
  • Minor repo maintenance: .difyignore, .gitignore, Makefile, and CONTRIBUTING.md updates.

Notes:

  • Tool interface / parameter names remain stable (this is a version update, not a new tool contract).
  • Chunking runs locally in Dify; no external API calls are made by this plugin.

This PR contains only the updated plugin package (.difypkg) as required for Dify Marketplace submissions.

4. Checklist

  • I have read and followed the Publish to Dify Marketplace guidelines
  • I have read and comply with the Plugin Developer Agreement
  • I confirm my plugin works properly on both Dify Community Edition and Cloud Version
  • I confirm my plugin has been thoroughly tested for completeness and functionality
  • My plugin brings new value to Dify

5. Documentation Checklist

Please confirm that your plugin README includes all necessary information:

  • Step-by-step setup instructions
  • Detailed usage instructions
  • All required APIs and credentials are clearly listed
  • Connection requirements and configuration details
  • Link to the repository for the plugin source code

6. Privacy Protection Information

Based on Dify Plugin Privacy Protection Guidelines:

Data Collection

This plugin does not collect or store any user personal data. It processes user-provided Markdown locally inside the user’s Dify environment and returns chunked output. No external services are called.

Privacy Policy

  • I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/langgenius/dify-plugins/pull/1875 **Author:** [@asukhodko](https://github.com/asukhodko) **Created:** 1/10/2026 **Status:** ✅ Merged **Merged:** 1/11/2026 **Merged by:** [@crazywoola](https://github.com/crazywoola) **Base:** `main` ← **Head:** `main` --- ### 📝 Commits (1) - [`41932b8`](https://github.com/langgenius/dify-plugins/commit/41932b8257b6d0d2041513017c6653245bb5cf04) feat(markdown-chunker): update to v2.1.7 ### 📊 Changes **1 file changed** (+0 additions, -0 deletions) <details> <summary>View changed files</summary> ➕ `asukhodko/markdown-chunker-2.1.7.difypkg` (+0 -0) </details> ### 📄 Description # Plugin Submission Form ## 1. Metadata <!-- Please provide the following metadata of your plugin to make it easier for the reviewer to check the changes. - Plugin Author : The author of the plugin which is defined in your manifest.yaml - Plugin Name : The name of the plugin which is defined in your manifest.yaml - Repository URL: The URL of the repository where the source code of your plugin is hosted --> - **Plugin Author**: asukhodko - **Plugin Name**: markdown_chunker - **Repository URL**: https://github.com/asukhodko/dify-markdown-chunker ## 2. Submission Type - [ ] New plugin submission - [x] Version update for existing plugin ## 3. Description <!-- Please briefly describe the purpose of the new plugin or the updates made to the existing plugin --> This PR bumps **markdown_chunker** from **v2.1.4 → v2.1.7**. The big story in this version range: the plugin has been migrated from the previously embedded `markdown_chunker_v2` implementation to the external **chunkana** library (the plugin is now an integration layer that maps Dify Tool params → chunkana config and formats the output for KB/RAG use). ### What’s included in v2.1.7 (v2.1.4...v2.1.7) **Chunkana-powered engine + repo cleanup** - Removed the embedded chunking implementation (`markdown_chunker_v2/` and legacy `markdown_chunker/`) from the plugin repo. - Added a migration compatibility layer: - `adapter.py` (param mapping + boundary-invariant chunking + output rendering), - `input_validator.py` (input/metadata normalization), - `output_filter.py` (hierarchy/debug filtering and indexable-oriented output shaping). **Docs refreshed to match the new architecture** - README + docs were updated heavily to reflect the new “powered by chunkana” reality: - updated usage/quickstart/configuration/strategies/API docs, - added a dedicated migration guide: `docs/guides/migration-to-chunkana.md`, - removed legacy Stage1 / `markdown_chunker_v2` docs and examples. - Docs now clearly explain: - `include_metadata` as an output-format choice (boundaries don’t depend on it), - hierarchy behavior (`enable_hierarchy`, `leaf_only`, `debug`) and how it affects what chunks are returned. **Metadata/marketplace descriptions** - `manifest.yaml` and `provider/markdown_chunker.yaml` descriptions were updated (all locales) to explicitly mention chunkana as the underlying engine. **Testing / dev housekeeping** - Test suite and fixtures were refactored to focus on migration/backward-compatibility baselines (new fixtures + golden snapshots). - Added `run_test.sh`, updated `pytest.ini`, and cleaned up old demo/validation scripts. - Minor repo maintenance: `.difyignore`, `.gitignore`, `Makefile`, and `CONTRIBUTING.md` updates. Notes: - Tool interface / parameter names remain stable (this is a version update, not a new tool contract). - Chunking runs locally in Dify; no external API calls are made by this plugin. > This PR contains only the updated plugin package (`.difypkg`) as required for Dify Marketplace submissions. ## 4. Checklist - [x] I have read and followed the Publish to Dify Marketplace guidelines - [x] I have read and comply with the Plugin Developer Agreement - [x] I confirm my plugin works properly on both Dify Community Edition and Cloud Version - [x] I confirm my plugin has been thoroughly tested for completeness and functionality - [x] My plugin brings new value to Dify ## 5. Documentation Checklist Please confirm that your plugin README includes all necessary information: - [x] Step-by-step setup instructions - [x] Detailed usage instructions - [x] All required APIs and credentials are clearly listed - [x] Connection requirements and configuration details - [x] Link to the repository for the plugin source code ## 6. Privacy Protection Information Based on Dify Plugin Privacy Protection Guidelines: ### Data Collection This plugin does **not** collect or store any user personal data. It processes user-provided Markdown locally inside the user’s Dify environment and returns chunked output. No external services are called. ### Privacy Policy - [x] I confirm that I have prepared and included a privacy policy in my plugin package based on the Plugin Privacy Protection Guidelines --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-22 18:11:44 -05:00
yindo closed this issue 2026-02-22 18:11:44 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Plugin Request
Plugin Request
Plugin Request
bug
duplicate
enhancement
pull-request
Mirrored from GitHub Pull Request
 question
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: langgenius/dify-plugins#1921
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?