coeftable 0.2.1__tar.gz → 0.3.1__tar.gz

{coeftable-0.2.1 → coeftable-0.3.1}/.github/workflows/publish.yml

@@ -11,11 +11,6 @@ on:
         description: "Git ref to build. Defaults to the triggering ref."
         required: false
         type: string
-      publish:
-        description: "Upload the built package to PyPI."
-        required: false
-        default: false
-        type: boolean
   workflow_dispatch:
 
 jobs:
@@ -40,21 +35,33 @@ jobs:
 
   publish:
     runs-on: ubuntu-latest
-    # A tag pushed by a workflow using the default token does not raise a
-    # push event, so a release cut by automation asks for the upload
-    # explicitly. Any other run sitting on a tag -- a hand-pushed tag, or a
-    # manual run selecting one, which is how a stranded release gets
-    # published -- is also a release build. A run on a branch never is.
-    if: inputs.publish || startsWith(github.ref, 'refs/tags')
+    # PyPI Trusted Publishing does not support reusable workflows
+    # (https://github.com/pypa/gh-action-pypi-publish/issues/166): a
+    # `workflow_call` invocation of this job would present the *caller's*
+    # workflow identity, not this one, and fail to match the Trusted
+    # Publisher entry registered for this workflow. So this job never
+    # publishes when called reusably -- release.yml calls this workflow
+    # for `build-package` only and does its own top-level publish. This
+    # job runs only for a direct trigger of this workflow sitting on a
+    # tag: a tag push, or a manual run selecting a tag ref (how a
+    # stranded release gets republished). A run on a branch never does.
+    if: startsWith(github.ref, 'refs/tags')
     environment:
       name: publish
       url: https://pypi.org/p/coeftable
     needs: build-package
     permissions:
+      contents: read
       id-token: write
     steps:
       - uses: actions/download-artifact@v8
         with:
           name: Packages
           path: dist
+      # Must be invoked straight from the job, never via a local composite
+      # action. This action builds a Docker trampoline whose image it names
+      # from `github.action_repository`/`github.action_ref`, and both are
+      # empty for an action nested inside another composite action
+      # (actions/runner#2473). It then falls back to this repository and its
+      # branch, and tries to pull an image that was never published.
       - uses: pypa/gh-action-pypi-publish@release/v1

{coeftable-0.2.1 → coeftable-0.3.1}/.github/workflows/release.yml

@@ -90,10 +90,12 @@ jobs:
           GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
         run: gh release create "${{ steps.version.outputs.tag }}" --generate-notes
 
-  publish:
-    # Called directly rather than left to the tag-push trigger on the publish
-    # workflow: the tag above is pushed with the workflow token, and GitHub
-    # does not raise workflow-triggering events for it.
+  build:
+    # Called reusably for the build step only: `publish.yml`'s own
+    # `publish` job is gated on `startsWith(github.ref, 'refs/tags')`,
+    # which is false here (`github.ref` reflects this run's own
+    # branch/dispatch ref, not the `ref:` input below), so it no-ops --
+    # only `build-package` executes.
     needs: tag
     uses: ./.github/workflows/publish.yml
     permissions:
@@ -102,7 +104,37 @@ jobs:
       id-token: write
     with:
       ref: ${{ needs.tag.outputs.tag }}
-      publish: true
+
+  publish:
+    # A real top-level job, not delegated via `uses:`: PyPI Trusted
+    # Publishing does not support reusable workflows -- the OIDC
+    # certificate's Build Config URI reflects the top-level caller
+    # (release.yml) for a `uses:`-invoked job, which then fails to match
+    # a Trusted Publisher entry registered for the *called* workflow.
+    # See https://github.com/pypa/gh-action-pypi-publish/issues/166 and
+    # the "Non-goals" section of that action's README: "keep the job
+    # calling pypi-publish in a top-level [workflow]". `build-package`
+    # itself has no such restriction and stays reusable above.
+    needs: build
+    runs-on: ubuntu-latest
+    environment:
+      name: publish
+      url: https://pypi.org/p/coeftable
+    permissions:
+      contents: read
+      id-token: write
+    steps:
+      - uses: actions/download-artifact@v8
+        with:
+          name: Packages
+          path: dist
+      # Must be invoked straight from the job, never via a local composite
+      # action. This action builds a Docker trampoline whose image it names
+      # from `github.action_repository`/`github.action_ref`, and both are
+      # empty for an action nested inside another composite action
+      # (actions/runner#2473). It then falls back to this repository and its
+      # branch, and tries to pull an image that was never published.
+      - uses: pypa/gh-action-pypi-publish@release/v1
 
   changelog:
     # Same reason as the publish job above: the release is created with the

coeftable-0.3.1/CHANGELOG.md

@@ -0,0 +1,101 @@
+<a id="v0.3.1"></a>
+# [v0.3.1](https://github.com/kylejcaron/coeftable/releases/tag/v0.3.1) - 2026-08-14
+
+<!-- Release notes generated using configuration in .github/release.yml at v0.3.1 -->
+
+## What's Changed
+### Bug Fixes
+* Fix row-group handling: labels spanning groups, row striping, and layout key collisions by [@kylejcaron](https://github.com/kylejcaron) in [#26](https://github.com/kylejcaron/coeftable/pull/26)
+* Build core metadata 2.4 so releases pass validation by [@kylejcaron](https://github.com/kylejcaron) in [#27](https://github.com/kylejcaron/coeftable/pull/27)
+### Maintenance
+* Update changelog for v0.3.0 by [@github-actions](https://github.com/github-actions)[bot] in [#21](https://github.com/kylejcaron/coeftable/pull/21)
+* Fix automated releases: PyPI Trusted Publishing rejects reusable workflows by [@kylejcaron](https://github.com/kylejcaron) in [#22](https://github.com/kylejcaron/coeftable/pull/22)
+
+
+**Full Changelog**: https://github.com/kylejcaron/coeftable/compare/v0.3.0...v0.3.1
+
+[Changes][v0.3.1]
+
+
+<a id="v0.3.0"></a>
+# [v0.3.0](https://github.com/kylejcaron/coeftable/releases/tag/v0.3.0) - 2026-08-05
+
+<!-- Release notes generated using configuration in .github/release.yml at v0.3.0 -->
+
+## What's Changed
+### Maintenance
+* Update changelog for v0.2.1 by [@github-actions](https://github.com/github-actions)[bot] in [#13](https://github.com/kylejcaron/coeftable/pull/13)
+* Document the PyPI trusted-publisher requirement for both entry points by [@kylejcaron](https://github.com/kylejcaron) in [#14](https://github.com/kylejcaron/coeftable/pull/14)
+* Add collapsible group sections by [@kylejcaron](https://github.com/kylejcaron) in [#18](https://github.com/kylejcaron/coeftable/pull/18)
+* Allow ref=None on Sparkline to drop the reference line and its domain constraint by [@kylejcaron](https://github.com/kylejcaron) in [#19](https://github.com/kylejcaron/coeftable/pull/19)
+* Support multiple overlaid series in one sparkline cell by [@kylejcaron](https://github.com/kylejcaron) in [#20](https://github.com/kylejcaron/coeftable/pull/20)
+
+
+**Full Changelog**: https://github.com/kylejcaron/coeftable/compare/v0.2.1...v0.3.0
+
+[Changes][v0.3.0]
+
+
+<a id="v0.2.1"></a>
+# [v0.2.1](https://github.com/kylejcaron/coeftable/releases/tag/v0.2.1) - 2026-08-05
+
+<!-- Release notes generated using configuration in .github/release.yml at v0.2.1 -->
+
+## What's Changed
+### Maintenance
+* Update changelog for v0.2.0 by [@github-actions](https://github.com/github-actions)[bot] in [#11](https://github.com/kylejcaron/coeftable/pull/11)
+* Publish releases to PyPI automatically by [@kylejcaron](https://github.com/kylejcaron) in [#12](https://github.com/kylejcaron/coeftable/pull/12)
+
+## New Contributors
+* [@github-actions](https://github.com/github-actions)[bot] made their first contribution in [#11](https://github.com/kylejcaron/coeftable/pull/11)
+
+**Full Changelog**: https://github.com/kylejcaron/coeftable/compare/v0.2.0...v0.2.1
+
+[Changes][v0.2.1]
+
+
+<a id="v0.2.0"></a>
+# [v0.2.0](https://github.com/kylejcaron/coeftable/releases/tag/v0.2.0) - 2026-08-04
+
+<!-- Release notes generated using configuration in .github/release.yml at v0.2.0 -->
+
+## What's Changed
+### Maintenance
+* ci: add workflow_dispatch release workflow with semver bump by [@kylejcaron](https://github.com/kylejcaron) in [#7](https://github.com/kylejcaron/coeftable/pull/7)
+* Sparkline column: inline line plots with uncertainty by [@kylejcaron](https://github.com/kylejcaron) in [#10](https://github.com/kylejcaron/coeftable/pull/10)
+
+
+**Full Changelog**: https://github.com/kylejcaron/coeftable/compare/v0.1.0...v0.2.0
+
+[Changes][v0.2.0]
+
+
+<a id="v0.1.0"></a>
+# [v0.1.0](https://github.com/kylejcaron/coeftable/releases/tag/v0.1.0) - 2026-07-28
+
+<!-- Release notes generated using configuration in .github/release.yml at main -->
+
+## What's Changed
+### Maintenance
+* chore: install pre-commit hooks during setup by [@kylejcaron](https://github.com/kylejcaron) in [#1](https://github.com/kylejcaron/coeftable/pull/1)
+* ci: drop redundant lint and typecheck jobs by [@kylejcaron](https://github.com/kylejcaron) in [#2](https://github.com/kylejcaron/coeftable/pull/2)
+* Theming by [@kylejcaron](https://github.com/kylejcaron) in [#3](https://github.com/kylejcaron/coeftable/pull/3)
+* docs patch: restore Parameters section header on Forest docstring by [@kylejcaron](https://github.com/kylejcaron) in [#4](https://github.com/kylejcaron/coeftable/pull/4)
+* chore: complete package metadata for PyPI publishing by [@kylejcaron](https://github.com/kylejcaron) in [#5](https://github.com/kylejcaron/coeftable/pull/5)
+* docs: add hero image, fix stale theming section in README by [@kylejcaron](https://github.com/kylejcaron) in [#6](https://github.com/kylejcaron/coeftable/pull/6)
+
+## New Contributors
+* [@kylejcaron](https://github.com/kylejcaron) made their first contribution in [#1](https://github.com/kylejcaron/coeftable/pull/1)
+
+**Full Changelog**: https://github.com/kylejcaron/coeftable/commits/v0.1.0
+
+[Changes][v0.1.0]
+
+
+[v0.3.1]: https://github.com/kylejcaron/coeftable/compare/v0.3.0...v0.3.1
+[v0.3.0]: https://github.com/kylejcaron/coeftable/compare/v0.2.1...v0.3.0
+[v0.2.1]: https://github.com/kylejcaron/coeftable/compare/v0.2.0...v0.2.1
+[v0.2.0]: https://github.com/kylejcaron/coeftable/compare/v0.1.0...v0.2.0
+[v0.1.0]: https://github.com/kylejcaron/coeftable/tree/v0.1.0
+
+<!-- Generated by https://github.com/rhysd/changelog-from-release v3.9.1 -->

{coeftable-0.2.1 → coeftable-0.3.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: coeftable
-Version: 0.2.1
+Version: 0.3.1
 Summary: Publication-quality summary tables for estimates with uncertainty.
 Project-URL: Homepage, https://github.com/kylejcaron/coeftable
 Project-URL: Repository, https://github.com/kylejcaron/coeftable
@@ -87,10 +87,11 @@ ct.CoefTable(df, rows="metric", estimate="est", ci=("lb", "ub"))
 ```
 
 A `CoefTable` renders itself in marimo, Jupyter, and any other `_repr_html_`-aware viewer —
-leave it as the last expression in a cell, no extra call needed. Outside a notebook, use
-`.gt()` to reach the underlying [great_tables](https://posit-dev.github.io/great-tables/)
-object: `table.gt().as_raw_html()` for an HTML string, `table.gt().save("t.png")` for an
-image, `table.gt().tab_options(...)` to keep styling with great_tables' own API.
+leave it as the last expression in a cell, no extra call needed. Outside a notebook,
+`table.as_raw_html()` is the HTML string entry point. `.gt()` remains the escape hatch to the
+underlying [great_tables](https://posit-dev.github.io/great-tables/) object itself:
+`table.gt().save("t.png")` for an image, `table.gt().tab_options(...)` to keep styling with
+great_tables' own API.
 
 ## Data shape
 
@@ -103,7 +104,15 @@ a `parameter` column.
 **Dimensions:**
 - `rows` — the label for each row in the table (e.g. a metric name).
 - `nest` — an optional secondary label stacked below each row.
-- `groups` — an optional column whose values produce section headers.
+- `groups` — an optional column whose values produce section headers. A row
+  label may appear under more than one group, in which case it renders once per
+  section — so the same set of metrics can be reported per region without
+  inventing a `nest` column to tell them apart. Pass
+  `collapsible_groups=True` to make those sections collapsible in the rendered
+  HTML — a pure CSS toggle (relies on `:has()`, Baseline since late 2023; on an
+  older browser without it the toggle no-ops and sections stay expanded), no
+  JavaScript, sections start expanded. Applies to `as_raw_html()`/`_repr_html_`;
+  `.gt()` is unaffected.
 - `split_columns` — an optional column whose values produce repeated column
   groups side by side, useful for comparing methods.
 
@@ -172,8 +181,35 @@ methods = pl.DataFrame(
 (
     ct.CoefTable(
         methods, rows="metric", split_columns="method", estimate="est", ci=("lb", "ub")
+    ).header("Cohort Revenue by Method")
+)
+```
+
+## Repeating metrics across sections
+
+A row label may appear under more than one `groups` value. The same metrics can
+therefore be reported per region, each section repeating the full set:
+
+```python
+import polars as pl
+import coeftable as ct
+
+regions = pl.DataFrame(
+    {
+        "metric": ["Revenue", "Signups", "Revenue", "Signups"],
+        "region": ["US", "US", "EU", "EU"],
+        "est": [1.2, 0.4, 2.1, 0.9],
+        "lb": [0.8, 0.1, 1.5, 0.5],
+        "ub": [1.6, 0.7, 2.7, 1.3],
+    }
+)
+
+(
+    ct.CoefTable(
+        regions, rows="metric", groups="region", collapsible_groups=True
     )
-    .header("Cohort Revenue by Method")
+    .estimate("Effect", "est", ci=("lb", "ub"))
+    .forest("Effect Plot", of="Effect", ref=0.0, symmetric=True)
 )
 ```
 
@@ -184,11 +220,11 @@ Four built-in themes are available from `coeftable.theme`:
 ```python
 from coeftable.theme import BLUE, COLORBLIND, DEFAULT, MONO, TEXTUAL
 
-DEFAULT       # Alias for TEXTUAL -- what CoefTable uses if you don't set a theme
-TEXTUAL       # Minimal, publication-style: muted colours, light chrome
-BLUE          # The original blue-grey palette
-COLORBLIND    # Colourblind-safe palette
-MONO          # Grayscale for mono journals
+DEFAULT  # Alias for TEXTUAL -- what CoefTable uses if you don't set a theme
+TEXTUAL  # Minimal, publication-style: muted colours, light chrome
+BLUE  # The original blue-grey palette
+COLORBLIND  # Colourblind-safe palette
+MONO  # Grayscale for mono journals
 ```
 
 Apply one with `.with_theme(...)`:
@@ -209,9 +245,8 @@ Use `with_direction` to mark rows where lower values are favourable (reusing
 the `df` frame from [Quick start](#quick-start)):
 
 ```python
-table = (
-    ct.CoefTable(df, rows="metric", estimate="est", ci=("lb", "ub"))
-    .with_direction({"Latency": "lower_is_better"})
+table = ct.CoefTable(df, rows="metric", estimate="est", ci=("lb", "ub")).with_direction(
+    {"Latency": "lower_is_better"}
 )
 ```
 
@@ -232,8 +267,13 @@ companion-frame choice used elsewhere in coeftable:
 arrives in: a SQL export, a dbt model, an experimentation platform's daily
 metrics table. Pass `data=` a separate frame with one row per point, and
 `value` / `ci` / `x` name *scalar* columns on it. coeftable groups the
-companion frame by the table's `rows` (+ `nest`, + `split_columns`) keys
-and collapses each group into a series internally:
+companion frame by the table's `rows` (+ `nest`, + `groups`, +
+`split_columns`) keys and collapses each group into a series internally.
+`groups` participates only when `data` actually carries that column, so a
+companion frame keyed on the row alone stays valid. The one case that needs
+it is a row label appearing under more than one group: without the group
+column in `data` those rows are indistinguishable, so coeftable reports it
+rather than serving every section the same merged series.
 
 ```python
 import datetime as dt
@@ -373,3 +413,29 @@ trend = pl.DataFrame(
     .sparkline("Override", value="lift", ref=1.0, ylim=(0.9, 1.1))
 )
 ```
+
+**No reference, or a hidden one.** `ref` also drives the dashed line and
+colour resolution; two ways to opt out, for data with no meaningful
+zero (revenue, durations, absolute counts):
+
+```python
+absolute = pl.DataFrame(
+    {
+        "metric": ["Revenue", "Latency"],
+        "value": [[282.3, 300.1, 320.0], [900.0, 910.0, 920.0]],
+    }
+)
+
+(
+    ct.CoefTable(absolute, rows="metric")
+    # ref=None: no reference at all. No dashed line, no forced domain
+    # inclusion of 0, and every cell colours neutral -- "favorable" has
+    # no meaning without something to compare against.
+    .sparkline("No reference", value="value", ref=None)
+    # ref=0.0, show_ref=False: the reference is real and still drives
+    # colour (favorable/unfavorable against 0), it just isn't drawn or
+    # forced into the domain. Opt in deliberately: a mark can then claim
+    # "above the reference" while the reference sits off-canvas.
+    .sparkline("Hidden reference", value="value", ref=0.0, show_ref=False)
+)
+```

{coeftable-0.2.1 → coeftable-0.3.1}/README.md

@@ -33,10 +33,11 @@ ct.CoefTable(df, rows="metric", estimate="est", ci=("lb", "ub"))
 ```
 
 A `CoefTable` renders itself in marimo, Jupyter, and any other `_repr_html_`-aware viewer —
-leave it as the last expression in a cell, no extra call needed. Outside a notebook, use
-`.gt()` to reach the underlying [great_tables](https://posit-dev.github.io/great-tables/)
-object: `table.gt().as_raw_html()` for an HTML string, `table.gt().save("t.png")` for an
-image, `table.gt().tab_options(...)` to keep styling with great_tables' own API.
+leave it as the last expression in a cell, no extra call needed. Outside a notebook,
+`table.as_raw_html()` is the HTML string entry point. `.gt()` remains the escape hatch to the
+underlying [great_tables](https://posit-dev.github.io/great-tables/) object itself:
+`table.gt().save("t.png")` for an image, `table.gt().tab_options(...)` to keep styling with
+great_tables' own API.
 
 ## Data shape
 
@@ -49,7 +50,15 @@ a `parameter` column.
 **Dimensions:**
 - `rows` — the label for each row in the table (e.g. a metric name).
 - `nest` — an optional secondary label stacked below each row.
-- `groups` — an optional column whose values produce section headers.
+- `groups` — an optional column whose values produce section headers. A row
+  label may appear under more than one group, in which case it renders once per
+  section — so the same set of metrics can be reported per region without
+  inventing a `nest` column to tell them apart. Pass
+  `collapsible_groups=True` to make those sections collapsible in the rendered
+  HTML — a pure CSS toggle (relies on `:has()`, Baseline since late 2023; on an
+  older browser without it the toggle no-ops and sections stay expanded), no
+  JavaScript, sections start expanded. Applies to `as_raw_html()`/`_repr_html_`;
+  `.gt()` is unaffected.
 - `split_columns` — an optional column whose values produce repeated column
   groups side by side, useful for comparing methods.
 
@@ -118,8 +127,35 @@ methods = pl.DataFrame(
 (
     ct.CoefTable(
         methods, rows="metric", split_columns="method", estimate="est", ci=("lb", "ub")
+    ).header("Cohort Revenue by Method")
+)
+```
+
+## Repeating metrics across sections
+
+A row label may appear under more than one `groups` value. The same metrics can
+therefore be reported per region, each section repeating the full set:
+
+```python
+import polars as pl
+import coeftable as ct
+
+regions = pl.DataFrame(
+    {
+        "metric": ["Revenue", "Signups", "Revenue", "Signups"],
+        "region": ["US", "US", "EU", "EU"],
+        "est": [1.2, 0.4, 2.1, 0.9],
+        "lb": [0.8, 0.1, 1.5, 0.5],
+        "ub": [1.6, 0.7, 2.7, 1.3],
+    }
+)
+
+(
+    ct.CoefTable(
+        regions, rows="metric", groups="region", collapsible_groups=True
     )
-    .header("Cohort Revenue by Method")
+    .estimate("Effect", "est", ci=("lb", "ub"))
+    .forest("Effect Plot", of="Effect", ref=0.0, symmetric=True)
 )
 ```
 
@@ -130,11 +166,11 @@ Four built-in themes are available from `coeftable.theme`:
 ```python
 from coeftable.theme import BLUE, COLORBLIND, DEFAULT, MONO, TEXTUAL
 
-DEFAULT       # Alias for TEXTUAL -- what CoefTable uses if you don't set a theme
-TEXTUAL       # Minimal, publication-style: muted colours, light chrome
-BLUE          # The original blue-grey palette
-COLORBLIND    # Colourblind-safe palette
-MONO          # Grayscale for mono journals
+DEFAULT  # Alias for TEXTUAL -- what CoefTable uses if you don't set a theme
+TEXTUAL  # Minimal, publication-style: muted colours, light chrome
+BLUE  # The original blue-grey palette
+COLORBLIND  # Colourblind-safe palette
+MONO  # Grayscale for mono journals
 ```
 
 Apply one with `.with_theme(...)`:
@@ -155,9 +191,8 @@ Use `with_direction` to mark rows where lower values are favourable (reusing
 the `df` frame from [Quick start](#quick-start)):
 
 ```python
-table = (
-    ct.CoefTable(df, rows="metric", estimate="est", ci=("lb", "ub"))
-    .with_direction({"Latency": "lower_is_better"})
+table = ct.CoefTable(df, rows="metric", estimate="est", ci=("lb", "ub")).with_direction(
+    {"Latency": "lower_is_better"}
 )
 ```
 
@@ -178,8 +213,13 @@ companion-frame choice used elsewhere in coeftable:
 arrives in: a SQL export, a dbt model, an experimentation platform's daily
 metrics table. Pass `data=` a separate frame with one row per point, and
 `value` / `ci` / `x` name *scalar* columns on it. coeftable groups the
-companion frame by the table's `rows` (+ `nest`, + `split_columns`) keys
-and collapses each group into a series internally:
+companion frame by the table's `rows` (+ `nest`, + `groups`, +
+`split_columns`) keys and collapses each group into a series internally.
+`groups` participates only when `data` actually carries that column, so a
+companion frame keyed on the row alone stays valid. The one case that needs
+it is a row label appearing under more than one group: without the group
+column in `data` those rows are indistinguishable, so coeftable reports it
+rather than serving every section the same merged series.
 
 ```python
 import datetime as dt
@@ -319,3 +359,29 @@ trend = pl.DataFrame(
     .sparkline("Override", value="lift", ref=1.0, ylim=(0.9, 1.1))
 )
 ```
+
+**No reference, or a hidden one.** `ref` also drives the dashed line and
+colour resolution; two ways to opt out, for data with no meaningful
+zero (revenue, durations, absolute counts):
+
+```python
+absolute = pl.DataFrame(
+    {
+        "metric": ["Revenue", "Latency"],
+        "value": [[282.3, 300.1, 320.0], [900.0, 910.0, 920.0]],
+    }
+)
+
+(
+    ct.CoefTable(absolute, rows="metric")
+    # ref=None: no reference at all. No dashed line, no forced domain
+    # inclusion of 0, and every cell colours neutral -- "favorable" has
+    # no meaning without something to compare against.
+    .sparkline("No reference", value="value", ref=None)
+    # ref=0.0, show_ref=False: the reference is real and still drives
+    # colour (favorable/unfavorable against 0), it just isn't drawn or
+    # forced into the domain. Opt in deliberately: a mark can then claim
+    # "above the reference" while the reference sits off-canvas.
+    .sparkline("Hidden reference", value="value", ref=0.0, show_ref=False)
+)
+```

{coeftable-0.2.1 → coeftable-0.3.1}/pyproject.toml

@@ -44,8 +44,14 @@ Homepage = "https://github.com/kylejcaron/coeftable"
 Repository = "https://github.com/kylejcaron/coeftable"
 Issues = "https://github.com/kylejcaron/coeftable/issues"
 
+# PyPI rejects core metadata 2.5, which hatchling 1.30 defaults to.
+# Drop once https://github.com/pypi/warehouse/issues/19083 ships.
 [tool.hatch.build.targets.wheel]
 packages = ["src/coeftable"]
+core-metadata-version = "2.4"
+
+[tool.hatch.build.targets.sdist]
+core-metadata-version = "2.4"
 
 [tool.hatch.version]
 source = "vcs"

{coeftable-0.2.1 → coeftable-0.3.1}/src/coeftable/_version.py

@@ -18,7 +18,7 @@ version_tuple: tuple[int | str, ...]
 commit_id: str | None
 __commit_id__: str | None
 
-__version__ = version = '0.2.1'
-__version_tuple__ = version_tuple = (0, 2, 1)
+__version__ = version = '0.3.1'
+__version_tuple__ = version_tuple = (0, 3, 1)
 
 __commit_id__ = commit_id = None