Qualify successor producer workflows with current Pandas before 0.2.0 #170

Problem and reproduction

The installed successor cohort resolves Pandas3.1.0, pandas-market-calendars5.5.0, Polars2.0.0 and NumPy2.5.4 on Python3.12. Dependencies are consistent, but thirteen real Data producer workflows fail under warnings-as-errors: PMC NYSE schedule construction uses deprecated Series.dt.weekday. The existing44-case installed suite does not select these paths. Main3141fbc reproduces all13 failures; the broader independent installed suite reports818passes/13failures/zero skips.

Desired behavior

Keep numerical and workflow assertions unchanged and warnings-as-errors generally. Handle only the exact supported upstream alias deprecation at its dependency origin, after verifying the actual cause. Prove the same warning outside that dependency still raises. Expand installed wheel qualification across the supported optional producer/consumer matrix to the relevant callback, history, identity, Pipeline, accounting and action workflows, requiring every selected case to run.

Prepare the0.2.0 changelog from its authoritative source and qualify a local stable-version wheel/sdist as the same coherent release-readiness change. No release, tag, deployment, licensed authentication retry or reference timing rerun is authorized by this issue.

Acceptance

• Retain the actual original thirteen failures and their dependency identities; corrected installed workflows pass unchanged numerical assertions.
• A narrowly scoped upstream compatibility filter does not suppress the same real Pandas warning in caller code or unrelated warnings.
• The broader installed suite includes the actual producer paths and executes without failures or skips; all supported matrix and existing final-head gates pass.
• Generated changelog includes the new calendar, accounting and migration contracts and their material compatibility differences.
• Stable0.2.0 artifacts retain exact source/version/hash identity and pass installation/docs examples and relevant regression checks before any separate publication decision.

Assistance

OpenAI Codex assists with source inspection, public-workflow reproduction, compatibility repair, regression checks and release preparation. The maintainer remains responsible for the implementation and reported evidence.