Repository navigation
Retire the upstream sync (upstream deleted bindings/python in #10615) - #518
Merged
Merged
Conversation
…h.sh refuse to run ArcadeData/arcadedb deleted bindings/python in ArcadeData#10615 (commit 1e0507a, 2026-10-23, 143 files), so running sync-upstream.sh would merge that deletion into this fork. Decision "Stop syncing" (2026-10-25): nothing needs the engine tree synced any more, since wheels take their jars from the release image and upstream engine PRs branch from upstream/main. - sync-upstream.sh exits 1 with a message naming ArcadeData#10615 and the decision; only --help still prints (the old help, with a retired banner). - make-upstream-pr-branch.sh exits 1 the same way. - AGENTS.md and bindings/python/AGENTS.md: the sync routine is retired by the decision of 2026-10-25; the release routine stays under "ask first". - sync-upstream.md and upstream-bindings-pr.md are marked retired with the reason and a pointer to ArcadeData/arcadedb-python; testing an engine fix without a sync is documented in sync-upstream.md. - release.md, upstream-issues.md, contributing.md, CAMPAIGN.md and the mkdocs nav no longer tell anyone to run the sync. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…ses here match it Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
What
Retires the upstream sync, by the user's decision of 2026-10-25 ("Stop syncing").
ArcadeData/arcadedb deleted
bindings/pythonin ArcadeData#10615 (commit1e0507a522, 2026-10-23, 143 files). Runningsync-upstream.shwould merge that deletion into this fork. Nothing needs the engine tree synced any more: the wheels take their jars from the release image, and upstream engine PRs branch fromupstream/main.sync-upstream.shexits 1 with a message that names chore: remove the Python bindings, moved to ArcadeData/arcadedb-python-bindings ArcadeData/arcadedb#10615, the decision and the date.--help(and-h) still print the old help, now with a retired banner. No other argument reaches the merge code.make-upstream-pr-branch.shexits 1 the same way. Both bodies stay in the files as the record; history is untouched.AGENTS.md: the periodic upstream update and the sync routine are retired by the decision of 2026-10-25. The release routine stays under "do not change without asking".bindings/python/AGENTS.mdrows updated to match.sync-upstream.mdandupstream-bindings-pr.mdare marked retired, say why and point to ArcadeData/arcadedb-python.sync-upstream.mdkeeps the "verify an upstream fix" routine, rewritten to build the engine jars of a commit (Build ArcadeDB engine jarsworkflow plusbuild.sh's third argument) instead of syncing.release.mdnow carries a warning at "Where the Version Comes From" and marks steps 1, 7 and 8 (written around the sync) as retired.upstream-issues.md,contributing.md,benchmarks/experiments/CAMPAIGN.mdand the mkdocs nav no longer tell anyone to run the sync.Open point for the owner
pom.xmlwas the release's version source and only moved through the sync. It now stays at26.11.1-SNAPSHOT(last bumped by the 2026-10-19 sync).release.mdsays to ask before cutting a release here until the version source is decided. This PR does not decide it.Not touched on purpose: comments in the
.github/workflowsfiles that mentionsync-upstream.sh(they stay true of the retired script, and editing workflows triggers CI for no gain).Checks run locally
bash sync-upstream.sh,--dry-run,--status: each exits 1 with the message.--helpand-hexit 0 and print the help.--status --helpexits 1.make-upstream-pr-branch.shand--no-push: exit 1 with the message.bash -non both scripts.mkdocs build --strictinbindings/pythonwith the pins fromdocs-build.yml(passes).pre-commit run --filesover every changed file (passes).🤖 Generated with Claude Code