Visitar URL original
docs: the fixes that shipped in 26.10.2 are no longer "not released yet" (#335) by tae898 · Pull Request #336 · humemai/arcadedb-embedded-python · GitHub
Skip to content

docs: the fixes that shipped in 26.10.2 are no longer "not released yet" (#335) - #336

Merged
tae898 merged 1 commit into
mainfrom
hygiene-20261019
Oct 18, 2026
Merged

tae898 merged 1 commit into
mainfrom
hygiene-20261019

Conversation

@tae898

@tae898 tae898 commented Oct 18, 2026

Copy link
Copy Markdown

Closes #335. Closes #99.

The weekly docs pass of 2026-10-19. The bindings docs still described six engine fixes as "fixed for 26.11.1, which is not released yet"; each fix's merge commit is an ancestor of the 26.10.2 tag e5040d0339, so 26.10.2 carries them all. Known Engine Issues drops those entries by its own rule and lists them under "Fixed in 26.10.2"; the guide, API pages, example comment, wheel sizes and test docstrings follow. Also: sync-upstream.sh --help now prints the real path lists, three small fixes in the release and upstream-PR pages, and two in the benchmark docs (a probe path not in the repository, a figure that exists but is skipped).

One test change. From ArcadeData#10253 (merged 2026-10-17, in upstream's 26.11.1-SNAPSHOT image that this repo's bindings CI downloads) the engine's Result.toJSON() writes an undeclared LocalDate as days since the epoch, as it already wrote a declared DATE on 26.10.2. to_json_list() keeps its documented midnight-UTC milliseconds (the #116 fix); test_to_json_list_writes_a_date_as_midnight_utc_in_any_jvm_zone no longer requires the two to be equal, and results.md no longer says they are. Without this the test fails on every platform at the next bindings CI run.

Checked locally before pushing:

  • the edited test files (test_bridge_fixes, test_count_pushdown_known_issues, test_light_edge_and_view_known_issues, test_null_index_known_issues, test_declared_type_known_issues): 105 passed on a wheel built with upstream main a830b2114a's engine, and 105 passed on the 26.10.2 release wheel
  • the full suite on that synced-engine wheel before the test change: 1055 passed, 3 failed (the date test in its three zones, fixed here)
  • mkdocs build --strict with the pins of docs-build.yml: passes
  • bash -n sync-upstream.sh and its --help output; py_compile on the edited Python files

🤖 Generated with Claude Code

…et" (#335)

The weekly docs pass (2026-10-19) found the bindings docs still describing six engine fixes as "fixed for 26.11.1, which is not released yet". Each fix's merge commit is an ancestor of the 26.10.2 tag (e5040d0), so 26.10.2 carries them all.

- known-issues.md: the six entries leave the page by its own rule and are listed under "Fixed in 26.10.2"; the ArcadeData#9228, ArcadeData#9289 and light_edges notes in the guide and API pages, the wheel sizes (70.2 MiB download, 97.8 MiB unpacked, computed from the PyPI file) and the test docstrings follow.
- test_bridge_fixes: from ArcadeData#10253 the engine's Result.toJSON writes an undeclared LocalDate as days since the epoch, as it already wrote a declared DATE on 26.10.2. to_json_list keeps its documented midnight-UTC milliseconds (the #116 fix); the test no longer requires the two to be equal, and results.md stops saying they are.
- sync-upstream.sh --help prints the real path lists (it named 1 of 5 fork-owned paths and 4 of 7 allowlisted workflows); release.md and upstream-bindings-pr.md: a dead anchor, a wrong step number, an optional argument shown as required.
- FAIRNESS.md: a probe path that is not in the repository; PAGE-SPEC.md: f3_sparse_perquery exists and is skipped, not unbuilt.

Closes #335. Closes #99: its cause, ArcadeData#9694, is fixed by ArcadeData#9703, which 26.10.2 carries.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@tae898
tae898 merged commit 4030179 into main Oct 18, 2026
50 checks passed
@tae898
tae898 deleted the hygiene-20261019 branch October 18, 2026 16:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Weekly docs pass 2026-10-19: fixes that shipped in 26.10.2 are still described as unreleased test_async_executor_bulk_command_is_exact_at_parallel_four stored 8742 of 9742 once on a darwin/arm64 runner

1 participant