Repository navigation
chore: prepare AI 1.8.0 release - #379
Merged
Merged
Conversation
- align AI, LLM and Python client versions - include workspace metadata in Python source packages - build release packages from Git archives in CI - reduce duplicate CI runs and fix uv setup - disable release tracing before credentials
- check Server 1.7.0 and latest in service jobs - retain Python 3.10 and 3.11 runtime coverage - record the resolved image and Server versions - collect diagnostics from the selected container
imbajin
marked this pull request as draft
October 10, 2026 04:40
- validate returned configuration text for file-backed graphs - require exact HTTP 415 and message for missing file origins - document the server configuration-export limitation
imbajin
marked this pull request as ready for review
October 10, 2026 04:44
MrJs133
approved these changes
Oct 10, 2026
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
2 participants
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.
Prepare the AI, LLM and Python client packages for 1.8.0. Python source distributions now include workspace build metadata, and CI builds release packages from a Git source archive. ML remains at 1.7.0 and excluded from the Apache source archive; MCP and Vermeer keep their independent versions.
Disable release-script tracing before credentials are assigned, cancel superseded PR runs, correct uv setup/cache inputs, and run Ruff once on supported Python 3.11. Service tests cover Server 1.7.0 and the rolling
latestimage on Python 3.10/3.11. Logs record the resolved image ID and/versionsresponse. Once the Server 1.8 image is released, advance the pinned baseline to 1.8.0 while retaininglatest.Validation: native wheel/sdist builds, Git archive rebuilds, root sdist-to-wheel rebuild, Ruff, and the existing client/LLM unit suites passed. Independent diff review found no actionable issues. A local Server 1.8 candidate passed the schema/vertex/edge/Gremlin/auth client tests and the LLM graph boundary/KG smoke tests. Release-script command substitutes confirmed credentials are absent from trace output, without signing or uploading.
Known boundaries:
uv syncstill fails because the existing ML source override references the intentionally excluded ML directory; package builds pass.Current-head CI passed: Python client, LLM, Ruff, license checks, CodeQL, and MCP regression. Client integration, LLM boundary, and KG smoke passed on Python 3.10/3.11 against both 1.7.0 and
latest. The recordedlatestimage reports Server core 1.8.0. Configuration export now verifies the existing file-origin contract; no tests are skipped or allowed to fail to accommodate this behavior.Once the 1.8.0 image is published, advance the pinned Server matrix entry to 1.8.0 while keeping
latest.