<?xml version="1.0"?>
<?xml-stylesheet type="text/xsl" href="/rss.xsl.xml"?>
<rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/">
<channel>
    <title>Changes in dokuwiki</title>
    <description></description>
    <language>en</language>
    <copyright>Copyright 2025</copyright>
    <generator>Java</generator><item>
        <title>e014d4c892e4ef0acfe31bae0274dc38e5366089 - docs: updated the security policy</title>
        <link>http://127.0.0.1:8080/history/dokuwiki/#e014d4c892e4ef0acfe31bae0274dc38e5366089</link>
        <description>docs: updated the security policyMore details for out-of-scope issue including previous rejectedexamples.

            List of files:
            /dokuwiki/SECURITY.md</description>
        <pubDate>Mon, 20 Jul 2026 13:00:00 +0000</pubDate>
        <dc:creator>Andreas Gohr &lt;gohr@cosmocode.de&gt;</dc:creator>
    </item>
<item>
        <title>fe58309edafb067d90f3f40ef3d416100d558a04 - extension: don&apos;t crash on malformed conflict/dependency ids</title>
        <link>http://127.0.0.1:8080/history/dokuwiki/#fe58309edafb067d90f3f40ef3d416100d558a04</link>
        <description>extension: don&apos;t crash on malformed conflict/dependency idsThe conflicts and depends fields in the repository metadata are freeform text entered by extension authors and may contain values that arenot valid extension ids, such as &quot;sprintdoc template&quot;. Since 9af82229frouted every Extension construction through the strict setBase()validation, such a value made Extension::createFromId() throw anuncaught RuntimeException while building the notices, taking down thewhole extension manager.Skip entries that cannot be parsed into an extension id when checkingfor missing dependencies and conflicts.As an immeadiate fix this will also be fixed in the repository API toavoid sending invalid extension IDs to the extension manager.Fixes #4691

            List of files:
            /dokuwiki/lib/plugins/extension/Notice.php/dokuwiki/lib/plugins/extension/_test/NoticeTest.php</description>
        <pubDate>Thu, 16 Jul 2026 11:00:00 +0000</pubDate>
        <dc:creator>Andreas Gohr &lt;gohr@cosmocode.de&gt;</dc:creator>
    </item>
<item>
        <title>1c00c02121477c81b95fe750b94acdf109cba20a - fix(parser): validate inline formatting closers with a single memoized scan</title>
        <link>http://127.0.0.1:8080/history/dokuwiki/#1c00c02121477c81b95fe750b94acdf109cba20a</link>
        <description>fix(parser): validate inline formatting closers with a single memoized scanThe inline formatting modes only open a span when a valid closer existsahead. That check was a lookahead built on CONTENT_UNTIL_PARA, testedcharacter by character up to the next paragraph break and re-evaluatedfrom scratch for every opener candidate &#8212; openers times paragraphlength. With pcre.jit=0 a crafted 32KB page took 16s and an ordinary34KB page with long paragraphs 37s; with the JIT on (the PHP default)the per-character lookahead exhausted the JIT stack, the match silentlyfailed, and the formatting &#8212; or everything after it &#8212; rendered as plaintext.The check also decided the wrong thing. It scanned raw text, so a closerlookalike inside content the lexer consumes atomically &#8212; a nowiki or %%span, a backtick code span, a link, a URL &#8212; counted as a real closereven though the mode&apos;s exit pattern can never fire there. And it ignoredthe enclosing span: an inner delimiter whose only closer lay past thecloser of the mode it sits in was entered anyway, so a stray delimiterpaired with one in a following sibling span and dragged the boundaryalong &#8212; the `*` in &apos;&apos;glob/*.conf&apos;&apos; joined the `*` of the next &apos;&apos;...&apos;&apos;span and corrupted the paragraph; the same held for //, ** and __ insidemonospace, and an emphasis opened inside ((...)) ran past the footnote&apos;s)) and the enclosing bold&apos;s **.Each formatting mode now declares its closer throughLexer::addCloserPattern(), mirroring addExitPattern(), and the lexeranswers &quot;does a valid closer exist ahead&quot; with one anchored possessivescan per range instead of a lookahead per opener:- The scan runs left to right from the opener, hopping over opaque spans  derived from already-registered patterns &#8212; a plain or special match is  consumed in one step, an entry into a verbatim mode (nowiki, the  backtick code spans) extends to that mode&apos;s first exit &#8212; so a closer  lookalike inside consumed content is never mistaken for a closer. Each  hop finds the earliest of boundary, closer, or opaque span in a single  leftmost search, keeping the check linear.- An opener is rejected when the nearest enclosing mode that has a closer  of its own would close before the opener&apos;s own closer, so a delimiter  that can never close within its span stays literal. That ancestor is  found by walking the mode stack past modes that declare no closer  (plugins, footnotes); the nearest guarded ancestor suffices, as it was  itself validated against its own when it opened.- Both verdicts are memoized and reset per parse() run: a proven closer  validates every earlier candidate, and a proven closer-free range  rejects every later candidate before the next boundary. With the lexer  consuming each opened span, the whole parse is linear in document size.Closer patterns match the closing delimiter itself with flanking contextin lookarounds &#8212; the convention exit patterns already follow &#8212; so closerpositions compare exactly across modes and a closer directly after aninner opener is seen. AbstractFormatting derives the closer from the exitpattern and registers it with the paragraph break as the boundary,preserving the rule that formatting never spans paragraphs; a mode withother needs can pass a different boundary or none.Footnote declares its )) as a closer rather than guarding its (( entrywith a (?=.*)) lookahead, so the footnote becomes a boundary the scansees and formatting inside it no longer pairs across the )); its closertakes no paragraph boundary, as footnotes are block-level. GfmEmphasisgains a closer pattern so single * emphasis is validated the same way,while its entry lookahead still enforces CommonMark nearest-delimiterpairing. GfmEmphasis and GfmStrong span bodies cannot contain theirdelimiter, so their in-pattern lookaheads stay linear on their own; theGFM backtick span bodies get deterministic alternatives with possessivequantifiers, removing their per-character backtracking.CONTENT_UNTIL_PARA is removed: any entry pattern built with it recreatesthe quadratic scan. ParallelRegex gains escapePattern() so embeddedcloser fragments follow the lexer&apos;s bare-parenthesis convention, reportsPREG_JIT_STACKLIMIT_ERROR so a future JIT exhaustion surfaces instead ofsilently truncating, and no longer rewrites its registered patterns inplace while compiling the compound regex.The adversarial 32KB page drops to 0.1s, the 37-second benign page to0.1s, and a 128KB variant stays under 0.6s.

            List of files:
            /dokuwiki/_test/tests/Parsing/ParserMode/FormattingTest.php/dokuwiki/_test/tests/Parsing/ParserMode/GfmDeletedTest.php/dokuwiki/_test/tests/Parsing/ParserMode/GfmEmphasisUnderscoreTest.php/dokuwiki/_test/tests/Parsing/ParserMode/GfmStrongUnderscoreTest.php/dokuwiki/inc/Parsing/Lexer/CloserPattern.php/dokuwiki/inc/Parsing/Lexer/Lexer.php/dokuwiki/inc/Parsing/Lexer/ParallelRegex.php/dokuwiki/inc/Parsing/Lexer/StateStack.php/dokuwiki/inc/Parsing/ParserMode/AbstractFormatting.php/dokuwiki/inc/Parsing/ParserMode/AbstractMode.php/dokuwiki/inc/Parsing/ParserMode/Deleted.php/dokuwiki/inc/Parsing/ParserMode/Emphasis.php/dokuwiki/inc/Parsing/ParserMode/Footnote.php/dokuwiki/inc/Parsing/ParserMode/GfmBacktickDouble.php/dokuwiki/inc/Parsing/ParserMode/GfmBacktickSingle.php/dokuwiki/inc/Parsing/ParserMode/GfmDeleted.php/dokuwiki/inc/Parsing/ParserMode/GfmEmphasisStrong.php/dokuwiki/inc/Parsing/ParserMode/GfmEmphasisStrongUnderscore.php/dokuwiki/inc/Parsing/ParserMode/GfmEmphasisUnderscore.php/dokuwiki/inc/Parsing/ParserMode/GfmStrongUnderscore.php/dokuwiki/inc/Parsing/ParserMode/Monospace.php/dokuwiki/inc/Parsing/ParserMode/Strong.php/dokuwiki/inc/Parsing/ParserMode/Subscript.php/dokuwiki/inc/Parsing/ParserMode/Superscript.php/dokuwiki/inc/Parsing/ParserMode/Underline.php</description>
        <pubDate>Thu, 09 Jul 2026 12:00:00 +0000</pubDate>
        <dc:creator>Andreas Gohr &lt;gohr@cosmocode.de&gt;</dc:creator>
    </item>
<item>
        <title>a37b7ba562500c458cad38c990698bead51ff589 - fix(parser): guard row_counter in tablerow_open()</title>
        <link>http://127.0.0.1:8080/history/dokuwiki/#a37b7ba562500c458cad38c990698bead51ff589</link>
        <description>fix(parser): guard row_counter in tablerow_open()The row counter used for row CSS classes was only initialized intable_open(). Renderers that open a row without a preceding table_open()call (such as the data plugin&apos;s empty-result list) triggered an&apos;Undefined array key row_counter&apos; warning on PHP 8. Initialize itdefensively, mirroring the existing cell_counter handling.

            List of files:
            /dokuwiki/inc/parser/xhtml.php</description>
        <pubDate>Tue, 14 Jul 2026 08:00:00 +0000</pubDate>
        <dc:creator>Andreas Gohr &lt;gohr@cosmocode.de&gt;</dc:creator>
    </item>
<item>
        <title>b22130d2b9e76b1247849cd618b2bcf664ee020f - fix(parser): stop group-quantifier body patterns from exhausting memory</title>
        <link>http://127.0.0.1:8080/history/dokuwiki/#b22130d2b9e76b1247849cd618b2bcf664ee020f</link>
        <description>fix(parser): stop group-quantifier body patterns from exhausting memorySeveral patterns repeat a group &#8212; (?:&#8230;)* / (?:&#8230;)+ &#8212; over a body that canspan a large region. On the non-JIT PCRE engine each iteration of agroup repetition keeps its own backtracking frame, so a big body retainsone frame per byte: a linear, unbounded memory spike that can fatal arequest (and, with JIT on, trips pcre.jit_stacklimit so the lexer dumpsthe rest of the document as literal text). A repetition over a singleitem (.* , [^x]+) is optimized by PCRE and unaffected.Make each body possessive: the repeated group cannot match the delimiterthat follows it, so it always stops at the first closer and never needsto backtrack.- media {{&#8230;}}, windowssharelink, gfm_quote, gfm_link: possessive body.- email validation (used by emaillink and mail_isvalid): possessive  local-part and domain groups; a long dotted `a.a.a&#8230;` local part or  domain was a ReDoS vector. Match results are unchanged.

            List of files:
            /dokuwiki/inc/MailUtils.php/dokuwiki/inc/Parsing/ParserMode/GfmLink.php/dokuwiki/inc/Parsing/ParserMode/GfmQuote.php/dokuwiki/inc/Parsing/ParserMode/Media.php/dokuwiki/inc/Parsing/ParserMode/Windowssharelink.php</description>
        <pubDate>Wed, 08 Jul 2026 17:00:00 +0000</pubDate>
        <dc:creator>Andreas Gohr &lt;gohr@cosmocode.de&gt;</dc:creator>
    </item>
<item>
        <title>ea3bdd9231d524fd2992979501f2bc84e6857321 - Merge pull request #4641 from kishoredr/fix/3714-paste-locktimer</title>
        <link>http://127.0.0.1:8080/history/dokuwiki/#ea3bdd9231d524fd2992979501f2bc84e6857321</link>
        <description>Merge pull request #4641 from kishoredr/fix/3714-paste-locktimerfix(locktimer): reset lock timer on paste and other input events

            List of files:
            /dokuwiki/lib/scripts/locktimer.js</description>
        <pubDate>Tue, 14 Jul 2026 09:00:00 +0000</pubDate>
        <dc:creator>Andreas Gohr &lt;andi@splitbrain.org&gt;</dc:creator>
    </item>
<item>
        <title>057ab5a057a76df652cfe4176512a550ca9937f6 - ci: update workflow actions to their latest releases</title>
        <link>http://127.0.0.1:8080/history/dokuwiki/#057ab5a057a76df652cfe4176512a550ca9937f6</link>
        <description>ci: update workflow actions to their latest releasesBumps actions/checkout to v7, actions/cache to v6, actions/github-scriptto v9, peter-evans/create-pull-request to v8 and softprops/action-gh-releaseto v3. The cache bump is required since the v3 cache service backend wasretired. All existing inputs and outputs remain compatible.

            List of files:
            /dokuwiki/.github/workflows/deletedFiles.yml</description>
        <pubDate>Tue, 14 Jul 2026 09:00:00 +0000</pubDate>
        <dc:creator>Andreas Gohr &lt;gohr@cosmocode.de&gt;</dc:creator>
    </item>
<item>
        <title>6d10fb865f5e25ac6523d2bf15c2cb9763853197 - style(changelog): fix overlong line</title>
        <link>http://127.0.0.1:8080/history/dokuwiki/#6d10fb865f5e25ac6523d2bf15c2cb9763853197</link>
        <description>style(changelog): fix overlong line

            List of files:
            /dokuwiki/inc/ChangeLog/ChangeLog.php</description>
        <pubDate>Tue, 14 Jul 2026 09:00:00 +0000</pubDate>
        <dc:creator>Andreas Gohr &lt;gohr@cosmocode.de&gt;</dc:creator>
    </item>
<item>
        <title>3a56ec9bc396c50c9d879450c0f5baf168a75b06 - fix(parser): stop unclosed GFM fenced code and emphasis from exhausting memory</title>
        <link>http://127.0.0.1:8080/history/dokuwiki/#3a56ec9bc396c50c9d879450c0f5baf168a75b06</link>
        <description>fix(parser): stop unclosed GFM fenced code and emphasis from exhausting memoryBoth modes repeat a group over their body, and on the non-JIT PCREengine each iteration of a group repetition keeps its own backtrackingframe. On unclosed input the body runs to end of input (or a paragraphbreak), the required closer fails, and the engine unwinds frame byframe: a linear, unbounded memory spike that can fatal a request oncethe body grows past the memory limit (and, with JIT on, tripspcre.jit_stacklimit so the lexer dumps the rest of the document asliteral text).gfm_code/gfm_file: the fence body (?:(?!CLOSE).)* already stops at thefirst valid closer, so no backtracking into it is ever legitimate. Makeit possessive so the no-closer case fails immediately.gfm_emphasis: its closer lookahead ended with a character the body hadto backtrack to reach (the [^\s*] before the closing *). Verify thatflanking-closer rule with a lookbehind instead, so the [^*] body &#8212; whichcannot match the * it stops at &#8212; can be possessive too.Matching is unchanged for well-formed input. The fenced-code patternswere introduced in b1c59bed2.

            List of files:
            /dokuwiki/inc/Parsing/ParserMode/GfmCode.php/dokuwiki/inc/Parsing/ParserMode/GfmEmphasis.php</description>
        <pubDate>Wed, 08 Jul 2026 16:00:00 +0000</pubDate>
        <dc:creator>Andreas Gohr &lt;gohr@cosmocode.de&gt;</dc:creator>
    </item>
<item>
        <title>f4daad6a571b2cc0cb5a470cab75eab8a2bfee9f - AI Policy document added</title>
        <link>http://127.0.0.1:8080/history/dokuwiki/#f4daad6a571b2cc0cb5a470cab75eab8a2bfee9f</link>
        <description>AI Policy document added

            List of files:
            /dokuwiki/CONTRIBUTING.md</description>
        <pubDate>Sat, 13 Jun 2026 10:00:00 +0000</pubDate>
        <dc:creator>Andreas Gohr &lt;andi@splitbrain.org&gt;</dc:creator>
    </item>
</channel>
</rss>
