#86 \part and numbers=noenddot

[Herbert Voss]

\listfiles
\documentclass%[numbers=noenddot]
{scrbook}
\begin{document}
\tableofcontents
%\part{Foo}
\chapter{Baz}
\section{Bar}
\end{document}

shows the numbers with no enddot. Umcommenting the \part I'll get the numbers with enddot.
Happens also for scrreprt and without chapters for scrartcl. With the optionsl setting for numbers it will be as expected.

Up-to-date TeXLive 2025 from today and running with lualatex.
.

 *File List*
 scrbook.cls    2025/06/04 v3.45 KOMA-Script document class (book)
scrkbase.sty    2025/06/04 v3.45 KOMA-Script package (KOMA-Script-dependent bas
ics and keyval usage)
 scrbase.sty    2025/06/04 v3.45 KOMA-Script package (KOMA-Script-independent b
asics and keyval usage)
scrlfile.sty    2025/06/04 v3.45 KOMA-Script package (file load hooks)
scrlfile-hook.sty    2025/06/04 v3.45 KOMA-Script package (using LaTeX hooks)
 scrlogo.sty    2025/06/04 v3.45 KOMA-Script package (logo)
  keyval.sty    2022/05/29 v1.15 key=value parser (DPC)
tocbasic.sty    2025/06/04 v3.45 KOMA-Script package (handling toc-files)
scrsize11pt.clo    2025/06/04 v3.45 KOMA-Script font size class option (11pt)
typearea.sty    2025/06/04 v3.45 KOMA-Script package (type area)
l3backend-luatex.def    2025-04-14 L3 backend support: PDF output (LuaTeX)

[Markus Kohm]

First of all: Why have you ignored:

Note: The milestone refers to the release in which an issue should be fixed, not the release in which it occurs. That's why the default for new issues is always the next release and usually the best choice for reports. It makes absolutely no sense to select a closed milestone when reporting a new issue!

Adding a new issue to an already closed milestone makes no sense.

And the dot is there, because the part number uses a Roman number. See the user manuals for more information, i.e. the description of option numbers in section 3.16 and table 3.14.

If you want the behavior of numbers=noenddot, just use numbers=noenddot. So there isn't an issue and nothing to change.