Skip to content

release: ship ExcelAlchemy 2.0.0#49

Merged
ruicore merged 27 commits intomainfrom
v2
Mar 28, 2026
Merged

release: ship ExcelAlchemy 2.0.0#49
ruicore merged 27 commits intomainfrom
v2

Conversation

@ruicore
Copy link
Copy Markdown
Contributor

@ruicore ruicore commented Mar 28, 2026

Summary

This PR promotes the v2 branch to the first stable public release of ExcelAlchemy 2.0.

What changed

  • bump the package version from 2.0.0rc1 to 2.0.0
  • finalize stable-release wording across README, README_cn, migrations, and changelog
  • add a dedicated docs/releases/2.0.0.md release checklist
  • finalize the CI + Codecov upload path
  • remove the public author email from package metadata
  • sanitize fixture contact data to avoid ambiguous personal-looking information

Verification

  • ./.venv/bin/ruff check .
  • ./.venv/bin/uv run pyright
  • ./.venv/bin/pytest -q

@codecov
Copy link
Copy Markdown

codecov bot commented Mar 28, 2026

Codecov Report

❌ Patch coverage is 85.72961% with 399 lines in your changes missing coverage. Please review.
✅ Project coverage is 86.04%. Comparing base (527b51c) to head (e00b246).
⚠️ Report is 31 commits behind head on main.

Files with missing lines Patch % Lines
src/excelalchemy/metadata.py 74.41% 37 Missing and 39 partials ⚠️
src/excelalchemy/core/alchemy.py 83.39% 33 Missing and 15 partials ⚠️
src/excelalchemy/helper/pydantic.py 79.13% 21 Missing and 8 partials ⚠️
src/excelalchemy/codecs/number_range.py 73.26% 16 Missing and 11 partials ⚠️
src/excelalchemy/codecs/date_range.py 81.81% 14 Missing and 10 partials ⚠️
src/excelalchemy/codecs/number.py 79.16% 13 Missing and 7 partials ⚠️
src/excelalchemy/core/rows.py 78.26% 14 Missing and 6 partials ⚠️
src/excelalchemy/config.py 78.16% 9 Missing and 10 partials ⚠️
src/excelalchemy/core/executor.py 74.62% 9 Missing and 8 partials ⚠️
src/excelalchemy/core/table.py 86.00% 9 Missing and 5 partials ⚠️
... and 21 more
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #49      +/-   ##
==========================================
- Coverage   90.76%   86.04%   -4.73%     
==========================================
  Files          31       46      +15     
  Lines        2188     2931     +743     
  Branches        0      366     +366     
==========================================
+ Hits         1986     2522     +536     
- Misses        202      242      +40     
- Partials        0      167     +167     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@ruicore ruicore merged commit b959da0 into main Mar 28, 2026
10 checks passed
Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector bot left a comment

Choose a reason for hiding this comment

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

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 380119bb54

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

return declared.required
if self.raw_field.default is not PydanticUndefined or self.raw_field.default_factory is not None:
return False
return not self.allows_none
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

P1 Badge Preserve requiredness for Optional fields without defaults

PydanticFieldAdapter.required currently falls back to return not self.allows_none, which marks field: T | None as optional even when no default is provided. In Pydantic v2, T | None without a default is still required (the key must be present), so this misclassification causes template/header validation to treat required columns as optional and defers failures to per-row validation at import time. This regresses required-column detection for common model declarations like address: String | None = FieldMeta(...).

Useful? React with 👍 / 👎.

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