Skip to content

S6: Release 1.1.0 — C-39 fix, gated publish, to_dataframe deprecation, pandas-free import #71

Description

@Polichinel

Epic: #66 · Wave 3 · Blocked by: S1, S2, S3, S5 (#67, #68, #69, #64) · Starts the ADR-022 §2 clock

Background

ADR-022 §7 requires the release checklist worked through in CHANGELOG.md before any poetry publish. House flow, from how 1.0.0 was cut: release/1.1.0 branch → PR into development → PR developmentmain → tag v1.1.0 on main → publish the GitHub Release (this now runs S2's gated workflow) → back-merge maindevelopment (required: check-branch demands origin/main ancestry on every later PR). A release commit touches exactly pyproject.toml:3, CHANGELOG.md, and reports/technical_risk_register.md.

The work

  • pyproject.toml:31.1.0.
  • CHANGELOG.md: [Unreleased]## [1.1.0] — YYYY-MM-DD (em dash) containing Fixed (C-39), Changed (publish gate; sklearn to dev deps with the float64 and error-text deviations), Deprecated (to_dataframe and the dataframe extra, removal in 2.0.0, replacement to_dict()), and the ADR-022 §7 checklist block modelled on 1.0.0's. Rule-2 answer: no removal in this release; this release ships the deprecation that 2.0.0 will cite. Do not reuse the 0.5.0 migration table header or the "For the … rows" phrasing (tests/test_falsification_session_shutdown.py searches the whole file).
  • Register: dated block at the top like the 2026-08-02 and 2026-09-16 ones; header updated.
  • Tag, publish, back-merge; confirm the publish job ran the suite; confirm PyPI shows 1.1.0.
  • Notify (ADR-022 §3.2): comment on Retire the to_dataframe → save_evaluations egress — three eval_*.parquet files nothing reads are the last caller keeping pandas alive in views-evaluation views-pipeline-core#512 and views-reporting (their ^1.0.0 / <2.0.0 accept 1.1.0 — nothing to do yet; 2.0.0 will need views-reporting's <2.0.0 widened first).

This story does not contain code changes.

Acceptance criteria

  • S2's CHANGELOG-section guard was red on the release branch before the section was written and green after
  • git diff v1.0.0..v1.1.0 --stat -- views_evaluation/ shows only S1, S3, S5 changes
  • Publish workflow green including the test step; pip index versions views-evaluation shows 1.1.0
  • main back-merged into development
  • Register header and dated block updated
  • Both consumers notified with the removal version

Validation

grep -n '^version' pyproject.toml                       # 1.1.0
grep -n '^## \[1.1.0\] — ' CHANGELOG.md                  # present, em dash
conda run --name views_pipeline pytest tests/ -q
bash documentation/validate_docs.sh
git tag -l 'v1.1.0'; gh release view v1.1.0 --json isDraft,publishedAt

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    implementationCode changerisk-registerOpens, closes or reconciles entries in reports/technical_risk_register.mdstoryA single, independently implementable and reviewable unit of an epic

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions