timsaucer opened a new pull request, #1524: URL: https://github.com/apache/datafusion-python/pull/1524
# Which issue does this PR close? Part of #1394 (PR 5 in the implementation plan). # Rationale for this change The repository periodically syncs to a newer upstream `apache/datafusion` version. The workflow we have converged on splits that work into three sequential PRs (crate bump + breakage fixes, transitive dependency consolidation, then API and documentation gap filling), but the workflow has lived only in tribal knowledge. New maintainers have no document to follow, and the agent skills that automate parts of the third step (`/check-upstream`, the new `/audit-skill-md`) have no canonical entry point that describes when to invoke them. This PR captures the workflow in `dev/release/upstream-sync.md`, adds the `audit-skill-md` agent skill that PR 3 of the workflow relies on, and wires a verification checkbox into the existing release instructions so the sync is confirmed complete before a release branch is cut. # What changes are included in this PR? - `dev/release/upstream-sync.md` — describes the three-PR workflow: bump DataFusion crate dependencies and fix breakage, consolidate transitive dependencies, and fill API and documentation gaps via `/check-upstream` and `/audit-skill-md`. Cross-references existing skills and prior reference PRs (#1311, #1337). - `.ai/skills/audit-skill-md/SKILL.md` — new agent skill that audits `skills/datafusion_python/SKILL.md` against the current public Python API. Covers `SessionContext`, `DataFrame`, `Expr`, and `functions` surfaces. Reports four kinds of findings (new APIs not covered, stale mentions, examples that drifted from idiomatic style, missing version notes) and can apply edits directly when asked. Version notes use a single `datafusion-python NN` form because the package and upstream crate share a major version. - `dev/release/README.md` — adds an "Upstream Sync" pointer in the intro and a checklist item under "Preparing the `main` Branch" that confirms the sync workflow has been completed. # Are there any user-facing changes? No. Documentation and agent-skill files only. No code or public API changes. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
