chore(deps): update uv.lock dependencies#3703
Closed
renovate[bot] wants to merge 1 commit into
Closed
Conversation
Contributor
Author
|
Member
|
Ok, definitely not the behavior I wanted/expected 😅 |
7 tasks
renovate
Bot
force-pushed
the
renovate/uv.lock-dependencies
branch
from
05b698f to
18f7b53
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
26.4.0→26.6.02026.3.0→2026.6.0==2024.10→==2026.6.01.5.3→1.5.4==1.3→==1.5.4==1.2→==1.5.4==1.1→==1.5.46.152.9→6.155.72.0.3→2.0.5==1.24.4→==2.5.0==1.22.0→==2.5.0==1.21.4→==2.5.0==2.3.0.250703→==2.3.3.2601131.40.1→1.42.0==0.20.8→==1.42.0==0.20.4→==1.42.0<17→<20==19.2→==19.4==1.0.0→==1.1.14.1.1→4.1.2==3.5.0→==4.1.29.0.3→9.1.1==1.3.0→==1.9.0==1.1.0→==1.9.0==1.8.0→==1.18.0==1.7.3→==1.18.04.2.0→4.3.00.0.43→0.0.46Release Notes
rapidsai/cudf (cudf-cu12)
v26.6.0Compare Source
duckdb/duckdb-python (duckdb)
v1.5.4: Bugfix ReleaseCompare Source
See DuckDB's changelog for all changes in DuckDB.
What's Changed in DuckDB-Python
HypothesisWorks/hypothesis (hypothesis)
v6.155.7: Hypothesis version 6.155.7Compare Source
This patch fixes a thread-safety bug where concurrent use of the same
strategy instance could error in rare cases. (issue #4475).
The canonical version of these notes (with links) is on readthedocs.
v6.155.6: Hypothesis version 6.155.6Compare Source
This patch replaces some internal "%"-style string formatting with
f-strings. There is no user-visible change.
The canonical version of these notes (with links) is on readthedocs.
v6.155.5: Hypothesis version 6.155.5Compare Source
"dates()" now raises "InvalidArgument" if a "datetime" is passed as
"min_value" or "max_value". Because "datetime" is a subclass of
"date", such bounds were previously accepted and then failed with a
confusing "TypeError" while generating examples.
The canonical version of these notes (with links) is on readthedocs.
v6.155.4: Hypothesis version 6.155.4Compare Source
This patch removes a stray "print()" which fired whenever a "dates()"
filter was rewritten.
The canonical version of these notes (with links) is on readthedocs.
v6.155.3: Hypothesis version 6.155.3Compare Source
When using an alternative backend (such as hypothesis-crosshair),
Hypothesis no longer emits a "test_case" observation for an iteration
that the backend aborts via "BackendCannotProceed" before the test
body runs. Previously such an iteration -- for example when the
crosshair backend has exhausted its search paths -- could surface as a
spurious, draw-less "passed" observation with an empty representation,
even though the engine already discards the iteration entirely.
The canonical version of these notes (with links) is on readthedocs.
v6.155.2: Hypothesis version 6.155.2Compare Source
This patch rewrites the internal date- and time-drawing helper to use
plain arithmetic instead of branching on the values it draws. The
generated distribution is unchanged, but "dates()", "datetimes()", and
"times()" are now much more efficient under symbolic-execution
backends such as crosshair-tool, which can now solve for a specific
date directly rather than enumerating candidates (issue #4759).
The canonical version of these notes (with links) is on readthedocs.
v6.155.1: Hypothesis version 6.155.1Compare Source
Shrinking large floats, strings, and bytestrings is now much faster in
some cases (issue #4006).
The canonical version of these notes (with links) is on readthedocs.
v6.155.0: Hypothesis version 6.155.0Compare Source
"from_dtype()" now supports the variable-width string dtype
"numpy.dtypes.StringDType", generating arbitrary strings via "text()"
(issue #4039).
Additionally, passing a dtype class such as "np.dtypes.StringDType"
where an instance like "np.dtypes.StringDType()" was expected now
raises a clear error, rather than the previous confusing message (or
silent coercion to the object dtype in "arrays()").
The canonical version of these notes (with links) is on readthedocs.
v6.154.2: Hypothesis version 6.154.2Compare Source
This patch improves the type annotations of "fixed_dictionaries()",
which now accepts a "Mapping" rather than requiring an invariant
"dict". Because the value type is covariant, type-checkers can now
infer the generated type even when the strategies are heterogeneous,
e.g. a "mapping" annotated as "dict[str, SearchStrategy[int] |
SearchStrategy[str]]" (issue #4665).
The "mapping" and "optional" arguments may now also have different key
and value types, which are unioned in the inferred result.
The canonical version of these notes (with links) is on readthedocs.
v6.154.1: Hypothesis version 6.154.1Compare Source
This patch fixes a bug where resolving recursive forward references in
"from_type()" (such as "A = list[Union["A", str]]", added in
v6.152.11) could recurse until it hit the interpreter's recursion
limit before falling back to a deferred strategy. Because this
depended on the ambient stack depth, it occasionally surfaced as a
spurious "RecursionError" or other flaky failure. We now break the
cycle eagerly by deferring, so resolution uses a small and constant
amount of stack regardless of how deeply nested the reference is.
The canonical version of these notes (with links) is on readthedocs.
v6.154.0: Hypothesis version 6.154.0Compare Source
"fixed_dictionaries()" now varies the iteration order of the dicts it
generates, rather than always placing the required keys first, to help
find bugs in code which is sensitive to key order (issue #3906). If
you need a stable order, we recommend using
"fixed_dictionaries(...).map(stable_sort_function)" or similar.
The canonical version of these notes (with links) is on readthedocs.
v6.153.6: Hypothesis version 6.153.6Compare Source
The "--hypothesis-show-statistics" report now accounts for the
"Phase.explain" phase separately, rather than including its runtime
and test cases in the "Phase.shrink" phase (issue #4179).
The canonical version of these notes (with links) is on readthedocs.
v6.153.5: Hypothesis version 6.153.5Compare Source
This patch dramatically improves the performance of "from_type()" on
hierarchies of abstract classes whose subclasses refer back to the
base class (directly, or via a sibling subclass) in their annotations.
Resolution previously took time cubic in the number of subclasses; we
now resolve each type only once (issue #4729).
The canonical version of these notes (with links) is on readthedocs.
v6.153.4: Hypothesis version 6.153.4Compare Source
This patch fixes a bug where fuzz_one_input did not track the
"interesting_origin" of failures (issue #4420). As a result, it only
saved the single smallest failure to the database rather than the
smallest example of each distinct failure, and the
"interesting_origin" was missing from observability reports.
The canonical version of these notes (with links) is on readthedocs.
v6.153.3: Hypothesis version 6.153.3Compare Source
This patch fixes a bug where "decimals()" with the "places" argument
could generate values outside the "min_value" and "max_value" bounds,
when those bounds had more fractional digits than "places" (issue
#4651).
The canonical version of these notes (with links) is on readthedocs.
v6.153.2: Hypothesis version 6.153.2Compare Source
This patch improves the performance of stateful testing for state
machines with a large number of rules (issue #4465).
The canonical version of these notes (with links) is on readthedocs.
v6.153.1: Hypothesis version 6.153.1Compare Source
This patch fixes a bug where we emitted incorrect git patch files when
one file did not have a trailing newline (issue #4744).
The canonical version of these notes (with links) is on readthedocs.
v6.153.0: Hypothesis version 6.153.0Compare Source
"event()"'s "payload" is now typed as accepting "Any", matching its
runtime behavior of accepting any string-coercible object.
The canonical version of these notes (with links) is on readthedocs.
v6.152.12: Hypothesis version 6.152.12Compare Source
When Hypothesis detects that your data generation is flaky and raises
"FlakyStrategyDefinition", the error message now describes what
differed between the two runs - such as a different choice type,
different constraints, or drawing more or less data - as well as the
stack of strategies being drawn from, instead of only reporting that
generation was inconsistent. In stateful tests, it also reports the
steps leading up to the error.
Thanks to Ian Hunt-Isaak for this improvement!
The canonical version of these notes (with links) is on readthedocs.
v6.152.11: Hypothesis version 6.152.11Compare Source
This patch adds support for recursive forward references in
"from_type()", such as "A = list[Union["A", str]]" (issue #4542).
Previously, such recursive type aliases would raise a
"ResolutionFailed" error. Now, Hypothesis can automatically resolve
the forward reference by looking it up in the caller's namespace. This
also resolves forward references inside "type[...]", such as
"type["MyClass"]".
The canonical version of these notes (with links) is on readthedocs.
v6.152.10: Hypothesis version 6.152.10Compare Source
This patch renames our source code directory from "hypothesis-python"
to "hypothesis", and changes our canonical scheme for git tags from
"hypothesis-python-X.Y.Z" to "vX.Y.Z".
We have backfilled git tags in the new "vX.Y.Z" scheme. Any
distributions or build scripts which rely on the git tag scheme should
update to the new scheme.
The canonical version of these notes (with links) is on readthedocs.
mkdocstrings/python (mkdocstrings-python)
v2.0.5Compare Source
Compare with 2.0.4
Bug Fixes
v2.0.4Compare Source
Compare with 2.0.3
Bug Fixes
numpy/numpy (numpy)
v2.5.0Compare Source
pandas-dev/pandas-stubs (pandas-stubs)
v2.3.3.260113Compare Source
v2.3.3.251219Compare Source
v2.3.3.251201Compare Source
v2.3.2.250926Compare Source
v2.3.2.250827Compare Source
zen-xu/pyarrow-stubs (pyarrow-stubs)
v19.4Compare Source
What's Changed
Full Changelog: zen-xu/pyarrow-stubs@19.3...19.4
v19.3Compare Source
What's Changed
DictionaryArraymethods/properties by @dangotbanned in #226(Table|RecordBatch).selectby @dangotbanned in #221Full Changelog: zen-xu/pyarrow-stubs@19.2...19.3
apache/spark (pyspark)
v4.1.2Compare Source
pytest-dev/pytest (pytest)
v9.1.1Compare Source
pytest 9.1.1 (2026-06-19)
Bug fixes
pytest.RaisesGroupwhich would might cause it to display incorrect "It matches FooError() which was paired with BarError" messages.list-itemtyping errors from mypy in@pytest.mark.parametrize <pytest.mark.parametrize ref>argvaluesparameter.conftest.pyfiles located in<invocation dir>/test*were no longer loaded as initial conftests when invoked without arguments.This could cause certain hooks (like
pytest_addoption) in these files to not fire.v9.1.0Compare Source
pytest 9.1.0 (2026-06-13)
Removals and backward incompatible breaking changes
#14533: When using
--doctest-modules, autouse fixtures withmodule,packageorsessionscope that are defined inline in Python test modules (not plugins or conftests) will now possibly execute twice.If this is undesirable, move the fixture definition to a
conftest.pyfile if possible.Technical explanation for those interested:
When using --doctest-modules, pytest possibly collects Python modules twice, once as
pytest.Moduleand once as aDoctestModule(depending on the configuration).Due to improvements in pytest's fixture implementation, if e.g. the
DoctestModulecollects a fixture, it is now visible to it only, and not to theModule.This means that both need to register the fixtures independently.
Deprecations (removal in next major release)
#10819: Added a deprecation warning for class-scoped fixtures defined as instance methods (without
@classmethod). Such fixtures set attributes on a different instance than the test methods use, leading to unexpected behavior. Use@classmethoddecorator instead -- byyastcher.See
10819and14011.#12882: Calling
request.getfixturevalue() <pytest.FixtureRequest.getfixturevalue>during teardown to request a fixture that was not already requested is now deprecated and will become an error in pytest 10.See
dynamic-fixture-request-during-teardownfor details.#13409: Using non-
~collections.abc.Collectioniterables (such as generators, iterators, or custom iterable objects) for theargvaluesparameter in@pytest.mark.parametrize <pytest.mark.parametrize ref>andmetafunc.parametrize <pytest.Metafunc.parametrize>is now deprecated.These iterables get exhausted after the first iteration,
leading to tests getting unexpectedly skipped in cases such as running
pytest.main()multiple times,using class-level parametrize decorators,
or collecting tests multiple times.
See
parametrize-iteratorsfor details and suggestions.#13946: The private
config.inicfgattribute is now deprecated.Use
config.getini() <pytest.Config.getini>to access configuration values instead.See
config-inicfgfor more details.#14004: Passing
baseidto~pytest.FixtureDefornodeidstrings to fixture registration APIs is now deprecated. These are internal pytest APIs that are used by some plugins.Use the
nodeparameter instead for fixture scoping. This enables more robust node-basedmatching instead of string prefix matching.
If you've used
nodeid=None, passnode=sessioninstead.This will be removed in pytest 10.
#14335: The method of configuring hooks using markers, deprecated since pytest 7.2, is now scheduled to be removed in pytest 10.
See
hook-markersfor more details.#14434: The
--pastebinoption is now deprecated.The same functionality is now available in an external plugin,
pytest-pastebin.See
pastebin-deprecatedfor more details.#14513: The private
FixtureDef.has_locationattribute is now deprecated and will be removed in pytest 10.See
fixturedef-has-location-deprecatedfor details.#1764:
pytest.console_mainis now deprecated and will be removed in pytest 10.It was never intended for programmatic use; use
pytest.maininstead.New features
#12376: Added
pytest.register_fixture()to register fixtures using an imperative interface.This is an advanced function intended for use by plugins.
Normally, fixtures should be registered declaratively using the
@pytest.fixture <pytest.fixture>decorator.Pytest looks for these fixture definitions during the collection phase and registers them automatically.
For some plugin usecases the declarative interface can be cumbersome or unviable, in which case this imperative interface can be used.
#14023: Added --report-chars long CLI option.
#14371: Added
--max-warningscommand-line option andmax_warningsconfiguration option to fail the test run when the number of warnings exceeds a given threshold -- bymiketheman.#6757: Added the
assertion_text_diff_styleconfiguration option, allowingstring equality failures to be rendered as separate
Left:andRight:blocks instead of
ndiffoutput.#8395: Added support for
~datetime.datetimeand~datetime.timedeltacomparisons withpytest.approx. An explicitabsorreltolerance as a~datetime.timedeltais required and relative tolerance is not supported for datetime comparisons -- byhamza-mobeen.Improvements in existing functionality
#11225:
pytest.warnsnow shows "Regex pattern did not match" instead of "DID NOT WARN" when warnings were emitted but thematchpattern did not match.#11295: Improved output of
--fixtures-per-testby excluding internal-implementation fixtures generated by@pytest.mark.parametrizeand similar.#13241:
pytest.raises,pytest.warnsandpytest.deprecated_callnow usesParamSpecfor the type hint to the (old and not recommended) callable overload, instead ofAny. This allows type checkers to raise errors when passing incorrect function parameters.funccan now also be passed as a kwarg, which the type hint previously showed as possible but didn't accept.#13862: Improved the readability of "DID NOT RAISE" error messages by using the exception type's name instead of its repr.
#14026: Added test coverage for compiled regex patterns in
pytest.raisesmatch parameter.#14137: pytest.ScopeName is now public to allow using it in function signatures.
#14342: Marked
yield_fixtureas deprecated to type checkers using thedeprecateddecorator. Note ithas originally been deprecated <yield-fixture-deprecated>in pytest 6.2 already.#14373: Added type annotations for
pytest.approx.#14430: When using
--setup-show, a space is now printed after the test name (and possibly used fixtures), to separate it from the test result.#14441: Reduced the default number of
gc.collect()passes in theunraisableexceptionplugin from 5 to 1 on CPython, where reference counting makes a single pass sufficient. PyPy retains 5 passes due to object resurrection via__del__. This can noticeably speed up test suites that trigger many pytester runs.#14461: Improved assertion failure explanations for equality comparisons between mapping objects that are not
dictinstances.#14513: The order in which fixture definitions overriding each other are resolved is now determined first by their visibility in the collection tree rather than by the order in which they are registered.
A fixture defined for a more specific node (e.g. a module or an item) now always takes precedence over one with the same name defined for a more general node (e.g. the session), even when the more general one was registered later.
Fixtures with non-comparable visibility or the same visibility keep the existing behavior of "last registered wins".
This change is supposed to only affect plugins which register multiple fixtures programmatically with the same name.
#14524: Add official Python 3.15 support.
#1764: Improved argparse program name to show
pytest,python -m pytest, orpytest.main()based on how pytest was invoked, making help and error messages clearer.#8265: Emit a
PytestCollectionWarningwhen a module-level__getattr__returnsNoneforpytestmarkinstead of raisingAttributeError.Previously this caused a cryptic
TypeError: got None instead of Markerror.Now pytest issues a helpful warning and continues collecting the module normally.
Bug fixes
#13192: Fixed | (pipe) not being treated as a regex meta-character that needs escaping in
pytest.raises(match=...) <pytest.raises>.#13484: Fixed
-Woption values being duplicated inConfig.known_args_namespace.#13626: Fixed function-scoped fixture values being kept alive after a test was interrupted by
KeyboardInterruptor early exit,allowing them to potentially be released more promptly.
#13784: Fixed
capteesysproducing doubled output when used with--capture=no(-s).#13817: Fixed a secondary AttributeError masking the original error when an option argument fails to initialize.
#13884: Fixed rare internal IndexError caused by builtins.compile being overridden in client code.
#13885: Fixed autouse fixtures defined inside a
unittest.TestCaseclass running even when the class is decorated withunittest.skiporunittest.skipIf-- regression since pytest 8.1.0.#13917:
unittest.SkipTestis no longer considered an interactive exception, i.e.pytest_exception_interactis no longer called for it.#13963: Fixed subtests running with
pytest-xdistwhen their contexts contain objects that are not JSON-serializable.Fixes pytest-dev/pytest-xdist#1273.
#14004: Fixed conftest.py fixture scoping when
testpathspoints outside of therootdir <rootdir>.Previously, fixtures from nested conftest.py files would incorrectly leak to sibling directories
when using a relative
testpathslike../tests/sdk.Conftest fixtures are now parsed during
Directory <pytest.Directory>collection, using theDirectorynode for proper scoping.#14050: Display dictionary differences in assertion failures using the original key insertion order instead of sorted order.
#14080: fix missing type annotations on
Pytester.makepyfileandPytester.maketxtfilemethods.#14114: An exception from
pytest_fixture_post_finalizerno longer prevents fixtures from being torn down, causing additional errors in the following tests.#14161: Fixed
monkeypatch.setattr() <pytest.MonkeyPatch.setattr>leaving a stale entry on the undo stack when the underlyingsetattr()call fails (e.g. on immutable targets), causing anAttributeErrorcrash during teardown.#14214: Fixed
-vhint inpytest.raisesmatch diff not working because assertion verbosity was not propagated.#14234: Allow
pytest.HIDDEN_PARAM <hidden-param>in@pytest.mark.parametrize(ids=...) <pytest.mark.parametrize ref>typing.#14248: Fixed direct parametrization causing the static fixture closure (as reflected in
request.fixturenames <pytest.FixtureRequest.fixturenames>) to omit fixtures that are requested transitively from overridden fixtures.#14263: Unraisable exceptions from finalizers are now collected during
pytest_unconfigure, before pytest tears down the warning filters installed for the session. Previously the collection ran from a cleanup callback whose order relative to other plugins' cleanups was not guaranteed, so an activeerrorfilter could be removed before the exception surfaced and a late resource leak would pass silently. A-W errorfilter, or any filter matchingpytest.PytestUnraisableExceptionWarning, now promotes these exceptions to failures regardless of plugin cleanup order.#14377: Fixed crash in Config.get_terminal_writer when an assertion fails with the
terminalreporterplugin disabled.#14381: Fixed
-V(short form of--version) to properly display the current version.#14389: Improved
pytest.raises(..., match=...) <pytest.raises>failures to suppress the mismatched exception as a cause of the resultingAssertionError.#14392: Fixed a bug in
pytest.raises(match=...) <pytest.raises>"fully escaped" detection, causing the regex diff display to be shown in some instances when the raw string diff display should be shown instead.#14442: Fixed a regression in pytest 9.0 where
--strict-markersand--strict-configspecified throughaddoptswere silently ignored.Note that when targeting pytest >= 9.0, it's nicer to use
strict_markersandstrict_config, orstrict mode <strict mode>.#14456: Fixed
pytest.approxnot recognizing types with__array_interface__as numpy-like arrays.#14474: Fixed a regression where
-kand-mexpressions containing both backslash characters in identifiers and string literal arguments would incorrectly raise aSyntaxErrorabout escaping.#14483: Fixed JUnit XML report incorrectly escaping high Unicode codepoints (supplementary plane characters like emoji) in test failure messages. -- by
EternalRights#14492: Fixed
Code.getargs()incorrectly including local variable names in the returned argument tuple for functions with*argsand/or**kwargs. The method was usingco_flagsbitmask values (4and8) directly as counts instead of converting them to1viabool(), and was not accounting forco_kwonlyargcountwhenvar=True.#3697: Logging capture now works for non-propagating loggers.
Previously only logs which reached the root logger were captured.
This includes
caplogand the "Captured log calls" test reporting.#3850: Fixed JUnit XML report: the
testsattribute of the<testsuite>element now always matches the number of<testcase>elements in the file. In some cases (test passes but fails during teardown) thetestsattribute would report an incorrect number of testcases in the XML file.#5848:
pytest_fixture_post_finalizeris no longer called extra times for the same fixture teardown in some cases.#719: Fixed
@pytest.mark.parametrize <pytest.mark.parametrize ref>not unpacking single-element tuple values when using a string argnames with a trailing comma (e.g.,"arg,").The trailing comma form now correctly behaves like the tuple form
("arg",), treating argvalues as a list of tuples to unpack.Improved documentation
@pytest.hookimpl(specname=...)only works for function names starting withpytest_.requestfixture provides indirect parametrization values viarequest.param.conftest.pyfiles are not available to other plugins during theirpytest_addoption()execution, as conftest files are discovered and loaded after builtin and third-party plugins have been initialized. However, initial conftest files themselves can implementpytest_addoption()to add their own command-line options.ini options refsection of the API Reference now specified the type and default value of every configuration option.pytestconfig.cacheaccess pattern when thecacheproviderplugin is disabled.newhooks.pyfile inpytest-xdistat tagv3.8.0instead of an unrelated 2017-era commit under the old layout. Pointing at a tag keeps the example in sync with the version users actually install, while remaining stable when the project's main branch moves on.Miscellaneous internal changes
scikit-learn/scikit-learn (scikit-learn)
v1.9.0Compare Source
scipy/scipy (scipy)
v1.18.0Compare Source
eakmanrq/sqlframe (sqlframe)
v4.3.0: SQLFrame 4.3.0Compare Source
What's Changed
Full Changelog: eakmanrq/sqlframe@v4.2.0...v4.3.0
zensical/zensical (zensical)
v0.0.46: 0.0.46Compare Source
Summary
This version improves search result quality and includes several bug fixes and refactorings.
Search excerpts
Search results now include excerpts, making it easier to understand why a result matches. Search remains fully client-side and as fast as before, even for projects with thousands of pages. We still consider search an active area of iteration and expect to further improve it and expose more configuration options over time.
Try it in our documentation!
User interface
The user interface is updated to v0.0.19, which includes several navigation and interaction fixes. Search highlighting now ignores single-character tokens, which avoids noisy matches like highlighting every
efor queries such ase-mail. Instant previews now include a hover bridge so moving the cursor from a link to the tooltip no longer drops the popup across the visual gap.Dependencies were also updated, including TypeScript 6 and SVGO 4 compatibility adjustments. 83 new icons were added, 2 icons were removed, and 19 icons were modified. The Lucide icon set was updated to version v1.21.0.
Validation defaults
The validation options
unresolved_references,unresolved_footnotes,unused_definitions,unused_footnotes,shadowed_definitions, andshadowed_footnotesare now disabled by default. These checks remain available when explicitly enabled, but they have proven too unstable in edge cases with the current reference parser. They will eventually be superseded by the higher-fidelity parser that is already used by Zensical Studio and is planned for Open Source release and later integration into Zensical.Changelog
Bug fixes
aeb31adui – update ui to v0.0.1961b6d05compat – preservesmalltags in generated search indexedb0878zensical – search path segment is empty when title is sourced from section index page909f973compat – don't crash on invalid URLs in HTML (#755)e6b55fecompat – strip images from toc labels (#749)0f11c7f– updateConfiguration
📅 Schedule: (UTC)
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.
This PR was generated by Mend Renovate. View the repository job log.