Skip to content

chore: sync main back into development after v1.14.0 - #496

Merged
Polichinel merged 2 commits into
developmentfrom
main
Oct 12, 2026
Merged

Polichinel merged 2 commits into
developmentfrom
main

Conversation

@Polichinel

Copy link
Copy Markdown
Contributor

Routine back-merge after the v1.14.0 release. Merge as a merge commit, never squash.

Two merge commits exist on main that are not on development — the promotions from #492 and #494. Without this sync the branches diverge a little further after every release, and git log main..development starts counting work that already shipped.

No code difference: git diff origin/main origin/development is empty. This is ancestry bookkeeping only.

v1.14.0 is tagged at 2b22a64 and published to PyPI (wheel + sdist, 2026-10-12T10:34Z).

🤖 Generated with Claude Code

https://claude.ai/code/session_01EfeuULbPTqrx4qtNki5dy9

release: v1.14.0 — ACLED pagination walks cursors before offset dies 27 Oct
release: v1.14.0 evidence — the parity notebook and the wider measurement
@Polichinel
Polichinel enabled auto-merge October 12, 2026 10:34
@Polichinel
Polichinel merged commit 47fa8b4 into development Oct 12, 2026
13 of 14 checks passed
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.

1 participant