slack-markdown-parser 2.4.1__tar.gz → 2.4.2__tar.gz

{slack_markdown_parser-2.4.1 → slack_markdown_parser-2.4.2}/CHANGELOG.md

@@ -6,6 +6,13 @@ The format is based on Keep a Changelog, and the project follows Semantic Versio
 
 ## [Unreleased]
 
+## [2.4.2] - 2026-05-29
+
+### Fixed
+
+- Stopped an unbalanced emphasis delimiter from corrupting unrelated, well-formed spans in the same block. The bold/italic/strikethrough patterns are matched with `re.DOTALL`, so a single stray `**` (for example a whitespace-flanked literal `**` in `閉じ ** が`, or an unclosed marker) shifted marker pairing across the whole block and flipped the protective ZWSP of nearby punctuation-terminated bold to the broken *outer* position, re-exposing the literal markers on Slack. `EMPHASIS_PATTERNS` now enforces CommonMark's minimal flanking requirement — an opening run is not followed by whitespace and a closing run is not preceded by whitespace — so a non-flanking stray marker stays literal and no longer disturbs its neighbours.
+- Bounded the `**` and `~~` emphasis bodies to a single delimiter run so a dangling opener with no valid closer of its own (for example `**oops **` or `**: x **` before a later `**…%**`) can no longer scan past the literal stray and steal a following well-formed span's closing marker, which had misplaced that span's protective ZWSP. The single-`*` italic body is intentionally left unbounded because italics legitimately wrap `**bold**`.
+
 ## [2.4.1] - 2026-05-29
 
 ### Fixed

{slack_markdown_parser-2.4.1/slack_markdown_parser.egg-info → slack_markdown_parser-2.4.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: slack-markdown-parser
-Version: 2.4.1
+Version: 2.4.2
 Summary: Convert LLM Markdown into Slack Block Kit messages
 Author: darkgaldragon
 License-Expression: MIT

{slack_markdown_parser-2.4.1 → slack_markdown_parser-2.4.2}/docs/spec-ja.md

@@ -178,6 +178,7 @@ LLM は外枠パイプの省略、区切り行の欠落、列数の不一致な
 - チャンクの先頭・末尾（行頭・行末・テキスト端、またはフェンスドコードブロックの境界）は安全とみなし、ゼロ幅スペースを付けません。
 - 外側の片方が前後の非境界テキストに密着している場合、その側だけにゼロ幅スペースを付けます。安全（境界）側はそのままにします。
 - 強調マーカー（`**`・`*`・`~~`）の内側が句読点に密着している場合（例 `**注意:**` や `**70.9%→83.0%**`）、マーカーの内側にゼロ幅スペースを挿入します。これによりマーカーの内側隣接文字が非句読点になり、後続が何であっても Slack の CommonMark right-/left-flanking 判定が成立します。Slack が flanking 近傍として認めない CJK テキストや CJK 句読点（`、` / `。`）の直前でも有効です。インラインコードは flanking 規則の対象外なので、このルールから除外します。
+- 強調デリミタは CommonMark の最小 flanking 条件を満たす場合のみ認識します。すなわち、開きランの直後が空白でなく、閉じランの直前が空白でないこと。両側が空白の単独マーカー（例 `閉じ ** が` の literal な `**`）や、その他の対になっていないマーカーはそのまま残します。これにより、1 個の余分なマーカーが近くの正しい装飾のペアリングをずらして、ゼロ幅スペースを誤った位置に挿入することを防ぎます。
 
 例外:
 

{slack_markdown_parser-2.4.1 → slack_markdown_parser-2.4.2}/docs/spec.md

@@ -177,6 +177,7 @@ Rules:
 - The start and end of a chunk (a line/text boundary, or the edge of a fenced code block) are treated as safe; no zero-width space is added there.
 - When an outer edge is tight against surrounding non-boundary text, only that edge is padded with a zero-width space. The safe (boundary) edge is left clean.
 - When an emphasis marker (`**`, `*`, `~~`) sits directly against punctuation on its inner side (for example `**注意:**` or `**70.9%→83.0%**`), a zero-width space is inserted just *inside* the marker. This makes the marker's inner neighbor a non-punctuation character, so Slack's CommonMark right-/left-flanking check succeeds regardless of what surrounds the token — including before CJK text and CJK punctuation (`、` / `。`), which Slack does not accept as a flanking neighbor. Inline code spans are exempt from this rule because they do not obey flanking rules.
+- Emphasis delimiters are recognized only when they satisfy CommonMark's minimal flanking rule: an opening run is not immediately followed by whitespace, and a closing run is not immediately preceded by whitespace. A stray, whitespace-flanked marker (for example the literal `**` in `閉じ ** が`), or an otherwise unbalanced marker, is left untouched. This prevents one dangling marker from shifting the pairing of nearby well-formed spans and misplacing their zero-width spaces.
 
 Exception:
 

{slack_markdown_parser-2.4.1 → slack_markdown_parser-2.4.2}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "slack-markdown-parser"
-version = "2.4.1"
+version = "2.4.2"
 description = "Convert LLM Markdown into Slack Block Kit messages"
 readme = "README.md"
 requires-python = ">=3.10"

{slack_markdown_parser-2.4.1 → slack_markdown_parser-2.4.2}/slack_markdown_parser/__init__.py

@@ -1,6 +1,6 @@
 """slack-markdown-parser public package API."""
 
-__version__ = "2.4.1"
+__version__ = "2.4.2"
 __license__ = "MIT"
 
 from .converter import (

{slack_markdown_parser-2.4.1 → slack_markdown_parser-2.4.2}/slack_markdown_parser/converter.py

@@ -32,10 +32,24 @@ STANDALONE_IMAGE_PATTERN = re.compile(
 )
 MARKDOWN_LINK_PATTERN = re.compile(r"\[[^\]\n]+\]\([^\)\n]+\)")
 INLINE_CODE_SPAN_PATTERN = re.compile(r"(?<!`)`[^`\n]+`(?!`)", flags=re.DOTALL)
+# Emphasis delimiters must satisfy CommonMark's minimal flanking requirement:
+# an opening run is not followed by whitespace and a closing run is not preceded
+# by whitespace. Enforcing this keeps a stray, whitespace-flanked delimiter
+# (e.g. the literal ``**`` in ``閉じ ** が``) from being paired at all.
+#
+# For ``**`` and ``~~`` the body additionally may not contain the same delimiter
+# run (``(?:(?!\*\*).)+?`` / ``(?:(?!~~).)+?``). Without this, a dangling opener
+# with no valid closer of its own (``**oops ** and **70.9%→83.0%**``) would scan
+# past the literal stray and steal a *later* well-formed span's closing marker,
+# shifting the pairing and corrupting that span's ZWSP placement. Bounding the
+# body to a single run makes the regex pair the same markers CommonMark does.
+# (The single-``*`` italic body is intentionally not bounded this way: italics
+# legitimately wrap ``**bold**`` and ``*`` is heavily overloaded, so it keeps the
+# whitespace guard only.)
 EMPHASIS_PATTERNS = (
-    re.compile(r"(?<!\*)\*\*(.+?)\*\*(?!\*)", flags=re.DOTALL),
-    re.compile(r"(?<!\*)\*(?!\*)(.+?)(?<!\*)\*(?!\*)", flags=re.DOTALL),
-    re.compile(r"~~(.+?)~~", flags=re.DOTALL),
+    re.compile(r"(?<!\*)\*\*(?!\s)((?:(?!\*\*).)+?)(?<!\s)\*\*(?!\*)", flags=re.DOTALL),
+    re.compile(r"(?<!\*)\*(?!\*)(?!\s)(.+?)(?<!\s)(?<!\*)\*(?!\*)", flags=re.DOTALL),
+    re.compile(r"~~(?!\s)((?:(?!~~).)+?)(?<!\s)~~", flags=re.DOTALL),
 )
 INLINE_CODE_PLACEHOLDER_PATTERN = re.compile(r"\ufff0code\d+\ufff1")
 PROTECTED_UNDERSCORE_SPAN_PATTERN = re.compile(

{slack_markdown_parser-2.4.1 → slack_markdown_parser-2.4.2/slack_markdown_parser.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: slack-markdown-parser
-Version: 2.4.1
+Version: 2.4.2
 Summary: Convert LLM Markdown into Slack Block Kit messages
 Author: darkgaldragon
 License-Expression: MIT