Skip to content

docs: populate CHANGELOG.md Unreleased section for v1.1.0 - #276

Merged
iabaako merged 2 commits into
mainfrom
docs/changelog-v1.1.0-unreleased
Aug 19, 2026
Merged

docs: populate CHANGELOG.md Unreleased section for v1.1.0#276
iabaako merged 2 commits into
mainfrom
docs/changelog-v1.1.0-unreleased

Conversation

@iabaako

@iabaako iabaako commented Aug 18, 2026

Copy link
Copy Markdown
Contributor

Pull Request Summary 🚀

What does this PR do? 📝

Populates the ## [Unreleased] section of CHANGELOG.md with every notable change merged into main since the v1.0.0.post1 tag, ahead of cutting a v1.1.0 pre-release for Test PyPI.

Why is this change needed? 🤔

just bump-pre/just bump-minor (and the other release-bump recipes) gate on CHANGELOG.md having entries under [Unreleased] before they'll bump the version. This is a prerequisite step for publishing a 1.1.0rc1 test build to Test PyPI.

How was this implemented? 🛠️

Walked the merge history from v1.0.0.post1 to main (PRs #242#274) and grouped the changes under Added / Changed / Fixed per docs/changelog_guide.md, with module references and PR/issue numbers:

This is a docs-only change — no application code is touched.

How to test or reproduce ? 🧪

git checkout docs/changelog-v1.1.0-unreleased
# Review CHANGELOG.md's [Unreleased] section for accuracy against the merged PRs

No functional testing applies since no application code changed.

Screenshots (if applicable) 📷

N/A — changelog documentation only.

Checklist ✅

  • I have run and tested my changes locally
  • I have limit this PR to less than 1000 lines of code change (if not, explain why)
  • I have updated/added tests to cover my changes (if applicable) — N/A, no application code changed
  • I have updated/added requirements to cover my changes (if applicable) — N/A
  • I have run linting and formatting on any code changes (if applicable) — markdownlint-cli2 clean
  • I have updated the documentation (README, etc.) accordingly — RELEASENOTES.md still needs a user-facing pass before the actual version bump
  • I have reviewed and resolved any merge conflict

Draft note: Opened as a draft — RELEASENOTES.md and the actual bump-pre version tag are still pending before this is ready to merge and trigger a Test PyPI release.

🤖 Generated with Claude Code

iabaako and others added 2 commits August 18, 2026 19:26
Documents everything merged into main since v1.0.0.post1 ahead of cutting
a v1.1.0 pre-release: Parquet import support, correction log Survey ID
display, auto-load on project creation, the outliers module split, the
shared view UI helpers, several bug fixes (prep filter inversion, datetime
parsing, bulk reapply error handling, stale prep/corrected data after
re-import), and the streamlit/dependency/CI housekeeping in between.

Required by the bump-pre release gate, which checks CHANGELOG.md has
entries under [Unreleased] before allowing a version bump.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
@sonarqubecloud

Copy link
Copy Markdown

@iabaako
iabaako marked this pull request as ready for review August 18, 2026 19:43
@iabaako
iabaako requested a review from a team as a code owner August 18, 2026 19:43

@wkirui wkirui left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good.

@iabaako
iabaako merged commit cd632e7 into main Aug 19, 2026
5 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.

Standardize error handling for failed prep/correction steps during bulk reapply bug: New imported data does not reflect on prep and correction pages

2 participants