PyMetaAnalysis 0.1.0__tar.gz → 0.2.1__tar.gz

{pymetaanalysis-0.1.0 → pymetaanalysis-0.2.1}/.github/workflows/release.yml

@@ -116,6 +116,7 @@ jobs:
       - name: Create release
         env:
           GH_TOKEN: ${{ github.token }}
+          GH_REPO: ${{ github.repository }}
         run: |
           args=("$GITHUB_REF_NAME" dist/* release-benchmark.json --verify-tag --generate-notes)
           version="${GITHUB_REF_NAME#v}"

{pymetaanalysis-0.1.0 → pymetaanalysis-0.2.1}/CHANGELOG.md

@@ -6,6 +6,29 @@ Changes planned for the next release accumulate under `Unreleased`.
 
 ## Unreleased
 
+## 0.2.1 - 2026-07-17
+
+### Fixed
+
+- README documentation and repository links use absolute URLs so they resolve
+  correctly when the project description is rendered on PyPI.
+
+## 0.2.0 - 2026-07-16
+
+### Added
+
+- generic `meta_analysis()` accepts either sampling variances or standard
+  errors, with explicit validation and auditable conversion provenance.
+
+### Changed
+
+- package author metadata identifies the project maintainer directly.
+
+### Fixed
+
+- GitHub Release creation receives explicit repository context in tag-driven
+  release jobs.
+
 ## 0.1.0 - 2026-07-15
 
 ### Added

{pymetaanalysis-0.1.0 → pymetaanalysis-0.2.1}/CITATION.cff

@@ -5,9 +5,11 @@ message: >-
 title: PyMetaAnalysis
 type: software
 authors:
-  - name: PyMetaAnalysis contributors
-version: 0.1.0
-date-released: 2026-07-15
+  - family-names: Ding
+    given-names: Zhaobo
+    email: ding.zb@yahoo.com
+version: 0.2.1
+date-released: 2026-07-17
 repository-code: https://github.com/ZhaoboDing/PyMetaAnalysis
 url: https://zhaoboding.github.io/PyMetaAnalysis/
 license: MIT

{pymetaanalysis-0.1.0 → pymetaanalysis-0.2.1}/PKG-INFO

@@ -1,12 +1,12 @@
 Metadata-Version: 2.4
 Name: PyMetaAnalysis
-Version: 0.1.0
+Version: 0.2.1
 Summary: A pandas-first, auditable meta-analysis library for Python
 Project-URL: Documentation, https://zhaoboding.github.io/PyMetaAnalysis/
 Project-URL: Source, https://github.com/ZhaoboDing/PyMetaAnalysis
 Project-URL: Issues, https://github.com/ZhaoboDing/PyMetaAnalysis/issues
 Project-URL: Changelog, https://github.com/ZhaoboDing/PyMetaAnalysis/blob/main/CHANGELOG.md
-Author: PyMetaAnalysis contributors
+Author-email: Zhaobo Ding <ding.zb@yahoo.com>
 Maintainer-email: Zhaobo Ding <ding.zb@yahoo.com>
 License-Expression: MIT
 License-File: LICENSE
@@ -51,7 +51,7 @@ Description-Content-Type: text/markdown
 
 [![CI](https://github.com/ZhaoboDing/PyMetaAnalysis/actions/workflows/ci.yml/badge.svg)](https://github.com/ZhaoboDing/PyMetaAnalysis/actions/workflows/ci.yml)
 [![Documentation](https://github.com/ZhaoboDing/PyMetaAnalysis/actions/workflows/pages.yml/badge.svg)](https://zhaoboding.github.io/PyMetaAnalysis/)
-[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
+[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://github.com/ZhaoboDing/PyMetaAnalysis/blob/main/LICENSE)
 
 PyMetaAnalysis is an early-stage, pandas-first Python library for conventional
 study-level meta-analysis. It accepts DataFrames, NumPy arrays, and ordinary
@@ -115,7 +115,7 @@ subgroup differences.
 
 | Input | Effects | Pooling/models |
 | --- | --- | --- |
-| Effect + sampling variance | Generic | Common/random inverse variance |
+| Effect + sampling variance or standard error | Generic | Common/random inverse variance |
 | Two-group events + totals | OR, RR, RD | Common MH OR/RR; common/random IV |
 | Two-group means + SDs + sizes | MD, Hedges' g | Common/random inverse variance |
 
@@ -124,6 +124,10 @@ and DerSimonian-Laird tau-squared estimators. Mean confidence intervals support
 the normal default plus unmodified and safeguarded Hartung-Knapp variants.
 Eligible random-effects fits include an HTS prediction interval.
 
+Generic analyses accept exactly one of `variance=` or `standard_error=`.
+Standard errors are squared internally and the conversion is recorded in the
+result provenance.
+
 Sparse binary behavior is explicit: study-level and Mantel-Haenszel continuity
 corrections are separate, relative-effect double-zero/double-all rows remain
 visible as exclusions, and RD exposes
@@ -174,18 +178,18 @@ are descriptive small-study-effect diagnostics, not proof of publication bias.
 The complete documentation is published at
 [zhaoboding.github.io/PyMetaAnalysis](https://zhaoboding.github.io/PyMetaAnalysis/).
 
-- [Installation](docs/installation.md)
-- [Getting started](docs/getting-started.md)
-- [Input data and row decisions](docs/guides/input-data.md)
-- [Generic](docs/guides/generic-effects.md), [binary](docs/guides/binary-outcomes.md), and [continuous](docs/guides/continuous-outcomes.md) guides
-- [Choosing methods](docs/guides/method-selection.md) and [statistical formulas](docs/methods/statistical-methods.md)
-- [Sensitivity analysis](docs/guides/sensitivity-analysis.md) and [plotting](docs/guides/plotting.md)
-- [Public API](docs/reference/api.md), [result objects](docs/reference/results.md), and [report schema](docs/reference/report-schema.md)
-- [Validation strategy](docs/validation.md) and [scope/limitations](docs/limitations.md)
-- [Citation guidance](docs/citation.md)
-- [R `meta`/`metafor` mapping](docs/guides/r-interoperability.md)
-
-An executable [end-to-end notebook](examples/quickstart.ipynb) uses synthetic
+- [Installation](https://zhaoboding.github.io/PyMetaAnalysis/installation/)
+- [Getting started](https://zhaoboding.github.io/PyMetaAnalysis/getting-started/)
+- [Input data and row decisions](https://zhaoboding.github.io/PyMetaAnalysis/guides/input-data/)
+- [Generic](https://zhaoboding.github.io/PyMetaAnalysis/guides/generic-effects/), [binary](https://zhaoboding.github.io/PyMetaAnalysis/guides/binary-outcomes/), and [continuous](https://zhaoboding.github.io/PyMetaAnalysis/guides/continuous-outcomes/) guides
+- [Choosing methods](https://zhaoboding.github.io/PyMetaAnalysis/guides/method-selection/) and [statistical formulas](https://zhaoboding.github.io/PyMetaAnalysis/methods/statistical-methods/)
+- [Sensitivity analysis](https://zhaoboding.github.io/PyMetaAnalysis/guides/sensitivity-analysis/) and [plotting](https://zhaoboding.github.io/PyMetaAnalysis/guides/plotting/)
+- [Public API](https://zhaoboding.github.io/PyMetaAnalysis/reference/api/), [result objects](https://zhaoboding.github.io/PyMetaAnalysis/reference/results/), and [report schema](https://zhaoboding.github.io/PyMetaAnalysis/reference/report-schema/)
+- [Validation strategy](https://zhaoboding.github.io/PyMetaAnalysis/validation/) and [scope/limitations](https://zhaoboding.github.io/PyMetaAnalysis/limitations/)
+- [Citation guidance](https://zhaoboding.github.io/PyMetaAnalysis/citation/)
+- [R `meta`/`metafor` mapping](https://zhaoboding.github.io/PyMetaAnalysis/guides/r-interoperability/)
+
+An executable [end-to-end notebook](https://github.com/ZhaoboDing/PyMetaAnalysis/blob/main/examples/quickstart.ipynb) uses synthetic
 data to demonstrate analysis, provenance, reporting, sensitivity, and plotting.
 
 Build the complete site locally with:
@@ -203,16 +207,22 @@ edge cases, and committed R `metafor` reference fixtures. CI covers Python
 distribution builds.
 
 This is independent cross-software validation, not a formal external
-statistical audit. See [validation](docs/validation.md) for exact coverage.
+statistical audit. See
+[validation](https://zhaoboding.github.io/PyMetaAnalysis/validation/) for exact
+coverage.
 
 ## Contributing
 
-See [CONTRIBUTING.md](CONTRIBUTING.md) and the full
-[development guide](docs/development.md). Statistical changes require formula
+See
+[CONTRIBUTING.md](https://github.com/ZhaoboDing/PyMetaAnalysis/blob/main/CONTRIBUTING.md)
+and the full
+[development guide](https://zhaoboding.github.io/PyMetaAnalysis/development/).
+Statistical changes require formula
 documentation, boundary tests, and an independent comparison where available.
 
-Security-sensitive reports should follow [SECURITY.md](SECURITY.md).
+Security-sensitive reports should follow
+[SECURITY.md](https://github.com/ZhaoboDing/PyMetaAnalysis/blob/main/SECURITY.md).
 
 ## License
 
-[MIT](LICENSE)
+[MIT](https://github.com/ZhaoboDing/PyMetaAnalysis/blob/main/LICENSE)

{pymetaanalysis-0.1.0 → pymetaanalysis-0.2.1}/README.md

@@ -2,7 +2,7 @@
 
 [![CI](https://github.com/ZhaoboDing/PyMetaAnalysis/actions/workflows/ci.yml/badge.svg)](https://github.com/ZhaoboDing/PyMetaAnalysis/actions/workflows/ci.yml)
 [![Documentation](https://github.com/ZhaoboDing/PyMetaAnalysis/actions/workflows/pages.yml/badge.svg)](https://zhaoboding.github.io/PyMetaAnalysis/)
-[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)
+[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](https://github.com/ZhaoboDing/PyMetaAnalysis/blob/main/LICENSE)
 
 PyMetaAnalysis is an early-stage, pandas-first Python library for conventional
 study-level meta-analysis. It accepts DataFrames, NumPy arrays, and ordinary
@@ -66,7 +66,7 @@ subgroup differences.
 
 | Input | Effects | Pooling/models |
 | --- | --- | --- |
-| Effect + sampling variance | Generic | Common/random inverse variance |
+| Effect + sampling variance or standard error | Generic | Common/random inverse variance |
 | Two-group events + totals | OR, RR, RD | Common MH OR/RR; common/random IV |
 | Two-group means + SDs + sizes | MD, Hedges' g | Common/random inverse variance |
 
@@ -75,6 +75,10 @@ and DerSimonian-Laird tau-squared estimators. Mean confidence intervals support
 the normal default plus unmodified and safeguarded Hartung-Knapp variants.
 Eligible random-effects fits include an HTS prediction interval.
 
+Generic analyses accept exactly one of `variance=` or `standard_error=`.
+Standard errors are squared internally and the conversion is recorded in the
+result provenance.
+
 Sparse binary behavior is explicit: study-level and Mantel-Haenszel continuity
 corrections are separate, relative-effect double-zero/double-all rows remain
 visible as exclusions, and RD exposes
@@ -125,18 +129,18 @@ are descriptive small-study-effect diagnostics, not proof of publication bias.
 The complete documentation is published at
 [zhaoboding.github.io/PyMetaAnalysis](https://zhaoboding.github.io/PyMetaAnalysis/).
 
-- [Installation](docs/installation.md)
-- [Getting started](docs/getting-started.md)
-- [Input data and row decisions](docs/guides/input-data.md)
-- [Generic](docs/guides/generic-effects.md), [binary](docs/guides/binary-outcomes.md), and [continuous](docs/guides/continuous-outcomes.md) guides
-- [Choosing methods](docs/guides/method-selection.md) and [statistical formulas](docs/methods/statistical-methods.md)
-- [Sensitivity analysis](docs/guides/sensitivity-analysis.md) and [plotting](docs/guides/plotting.md)
-- [Public API](docs/reference/api.md), [result objects](docs/reference/results.md), and [report schema](docs/reference/report-schema.md)
-- [Validation strategy](docs/validation.md) and [scope/limitations](docs/limitations.md)
-- [Citation guidance](docs/citation.md)
-- [R `meta`/`metafor` mapping](docs/guides/r-interoperability.md)
-
-An executable [end-to-end notebook](examples/quickstart.ipynb) uses synthetic
+- [Installation](https://zhaoboding.github.io/PyMetaAnalysis/installation/)
+- [Getting started](https://zhaoboding.github.io/PyMetaAnalysis/getting-started/)
+- [Input data and row decisions](https://zhaoboding.github.io/PyMetaAnalysis/guides/input-data/)
+- [Generic](https://zhaoboding.github.io/PyMetaAnalysis/guides/generic-effects/), [binary](https://zhaoboding.github.io/PyMetaAnalysis/guides/binary-outcomes/), and [continuous](https://zhaoboding.github.io/PyMetaAnalysis/guides/continuous-outcomes/) guides
+- [Choosing methods](https://zhaoboding.github.io/PyMetaAnalysis/guides/method-selection/) and [statistical formulas](https://zhaoboding.github.io/PyMetaAnalysis/methods/statistical-methods/)
+- [Sensitivity analysis](https://zhaoboding.github.io/PyMetaAnalysis/guides/sensitivity-analysis/) and [plotting](https://zhaoboding.github.io/PyMetaAnalysis/guides/plotting/)
+- [Public API](https://zhaoboding.github.io/PyMetaAnalysis/reference/api/), [result objects](https://zhaoboding.github.io/PyMetaAnalysis/reference/results/), and [report schema](https://zhaoboding.github.io/PyMetaAnalysis/reference/report-schema/)
+- [Validation strategy](https://zhaoboding.github.io/PyMetaAnalysis/validation/) and [scope/limitations](https://zhaoboding.github.io/PyMetaAnalysis/limitations/)
+- [Citation guidance](https://zhaoboding.github.io/PyMetaAnalysis/citation/)
+- [R `meta`/`metafor` mapping](https://zhaoboding.github.io/PyMetaAnalysis/guides/r-interoperability/)
+
+An executable [end-to-end notebook](https://github.com/ZhaoboDing/PyMetaAnalysis/blob/main/examples/quickstart.ipynb) uses synthetic
 data to demonstrate analysis, provenance, reporting, sensitivity, and plotting.
 
 Build the complete site locally with:
@@ -154,16 +158,22 @@ edge cases, and committed R `metafor` reference fixtures. CI covers Python
 distribution builds.
 
 This is independent cross-software validation, not a formal external
-statistical audit. See [validation](docs/validation.md) for exact coverage.
+statistical audit. See
+[validation](https://zhaoboding.github.io/PyMetaAnalysis/validation/) for exact
+coverage.
 
 ## Contributing
 
-See [CONTRIBUTING.md](CONTRIBUTING.md) and the full
-[development guide](docs/development.md). Statistical changes require formula
+See
+[CONTRIBUTING.md](https://github.com/ZhaoboDing/PyMetaAnalysis/blob/main/CONTRIBUTING.md)
+and the full
+[development guide](https://zhaoboding.github.io/PyMetaAnalysis/development/).
+Statistical changes require formula
 documentation, boundary tests, and an independent comparison where available.
 
-Security-sensitive reports should follow [SECURITY.md](SECURITY.md).
+Security-sensitive reports should follow
+[SECURITY.md](https://github.com/ZhaoboDing/PyMetaAnalysis/blob/main/SECURITY.md).
 
 ## License
 
-[MIT](LICENSE)
+[MIT](https://github.com/ZhaoboDing/PyMetaAnalysis/blob/main/LICENSE)

{pymetaanalysis-0.1.0 → pymetaanalysis-0.2.1}/docs/getting-started.md

@@ -20,9 +20,10 @@ See [installation](installation.md) for all extras and development checks.
 
 ## 2. Prepare a DataFrame
 
-The generic API expects one effect estimate and one strictly positive sampling
-variance per study. A standard error is not a variance; square it before using
-it as `variance=`.
+The generic API expects one effect estimate and either a strictly positive
+sampling variance or standard error per study. Supply `variance=` or
+`standard_error=`; standard errors are squared internally and recorded in
+provenance.
 
 ```python
 import pandas as pd

{pymetaanalysis-0.1.0 → pymetaanalysis-0.2.1}/docs/guides/generic-effects.md

@@ -1,8 +1,8 @@
 # Generic effects
 
 Use `meta_analysis()` when each study already has an effect estimate and its
-sampling variance. This is the generic inverse-variance workflow; it does not
-calculate an outcome-specific effect size.
+sampling variance or standard error. This is the generic inverse-variance
+workflow; it does not calculate an outcome-specific effect size.
 
 The pooling, tau-squared, confidence-interval, prediction-interval, and
 heterogeneity equations are specified under
@@ -49,22 +49,29 @@ result = ma.meta_analysis(
 All array-like arguments must be one-dimensional and have equal lengths.
 Generated row labels start at zero when no study labels are supplied.
 
-## Variance, not standard error
+## Variance or standard error
 
-`variance=` must contain finite, strictly positive sampling variances. Convert
-reported standard errors explicitly:
+Supply exactly one of `variance=` or `standard_error=`. Both must contain
+finite, strictly positive values. A reported standard-error column can be used
+directly:
 
 ```python
-data["vi"] = data["standard_error"] ** 2
+result = ma.meta_analysis(
+    data,
+    effect="yi",
+    standard_error="standard_error",
+)
 ```
 
-Do not pass confidence-interval widths or study sample variances unless they
-have first been converted to the sampling variance of the effect estimate.
+PyMetaAnalysis squares standard errors internally, retains both uncertainty
+columns in the study table, and records the conversion in provenance. Do not
+pass confidence-interval widths or study sample standard deviations as
+standard errors; they describe different quantities.
 
 ## Missing values
 
-The default `missing="raise"` rejects missing effects or variances. To
-retain incomplete rows as structured exclusions:
+The default `missing="raise"` rejects missing effects or values in the selected
+uncertainty input. To retain incomplete rows as structured exclusions:
 
 ```python
 result = ma.meta_analysis(

{pymetaanalysis-0.1.0 → pymetaanalysis-0.2.1}/docs/guides/input-data.md

@@ -30,6 +30,8 @@ result = ma.meta_analysis(
 
 Column names must exist. Array-like inputs may be mixed with DataFrame columns,
 but every array must contain exactly one value for every DataFrame row.
+Generic analyses require exactly one uncertainty input: `variance=` or
+`standard_error=`.
 
 ## Array-like inputs
 
@@ -38,7 +40,7 @@ Lists, tuples, pandas Series, and one-dimensional NumPy arrays are accepted:
 ```python
 result = ma.meta_analysis(
     effect=[0.1, 0.3, -0.2],
-    variance=[0.02, 0.04, 0.03],
+    standard_error=[0.14, 0.20, 0.17],
     study=["A", "B", "C"],
 )
 ```

{pymetaanalysis-0.1.0 → pymetaanalysis-0.2.1}/docs/guides/provenance-reporting.md

@@ -38,6 +38,10 @@ document.
 Each `TransformationRecord` has a stable name, resolved parameters, and the
 original row IDs it affected.
 
+Generic analyses supplied through `standard_error=` record a
+`standard_error_to_variance` transformation for every non-missing standard
+error that was squared before fitting.
+
 Binary analyses record:
 
 - the OR, RR, or RD effect-size transformation and its scales;

{pymetaanalysis-0.1.0 → pymetaanalysis-0.2.1}/docs/guides/r-interoperability.md

@@ -139,7 +139,19 @@ rma.uni(
 ```
 
 The corresponding R `meta` configuration starts from standard errors rather
-than variances:
+than variances. PyMetaAnalysis can accept that uncertainty column directly as
+`standard_error=`; no manual squaring step is required:
+
+```python
+result = ma.meta_analysis(
+    studies,
+    effect="yi",
+    standard_error="sei",
+    model="random",
+    tau2_method="REML",
+    ci_method="hartung_knapp_adhoc",
+)
+```
 
 ```r
 metagen(

{pymetaanalysis-0.1.0 → pymetaanalysis-0.2.1}/docs/index.md

@@ -82,9 +82,11 @@ lists unsupported methods explicitly.
 
 ## Project status
 
-PyMetaAnalysis 0.1.0 is the initial public release and has not undergone a
-formal external statistical audit. Pin the package version for consequential
-work and independently check important analyses. See the repository
+PyMetaAnalysis 0.2.1 fixes documentation and repository links in the PyPI
+project description. Version 0.2.0 added direct generic standard-error input
+to the initial public analysis scope. The project has not undergone a formal
+external statistical audit. Pin the package version for consequential work
+and independently check important analyses. See the repository
 [changelog](https://github.com/ZhaoboDing/PyMetaAnalysis/blob/main/CHANGELOG.md)
 and [contribution guide](development.md). For manuscripts and archived
 analyses, see [citing PyMetaAnalysis](citation.md).

{pymetaanalysis-0.1.0 → pymetaanalysis-0.2.1}/docs/limitations.md

@@ -27,8 +27,7 @@ deferred functionality explicit.
 - multilevel, multivariate, network, dose-response, diagnostic-accuracy, or
   individual-participant-data meta-analysis;
 - robust variance estimation or dependent-effect clustering;
-- single proportions, incidence rates, correlations, survival outcomes, or
-  generic standard-error input helpers;
+- single proportions, incidence rates, correlations, or survival outcomes;
 - Knapp-Hartung variants beyond the two documented choices;
 - alternative prediction-interval methods;
 - formal funnel-asymmetry, trim-and-fill, selection-model, or publication-bias
@@ -70,7 +69,7 @@ workflow must version those artifacts separately.
 
 ## Stability and review status
 
-The package version is currently `0.1.0`. Public APIs and serialized schemas
+The package version is currently `0.2.1`. Public APIs and serialized schemas
 may change during the 0.x series. Pin versions in analysis environments and
 inspect changelog/schema updates before upgrading.
 

{pymetaanalysis-0.1.0 → pymetaanalysis-0.2.1}/docs/reference/api.md

@@ -47,7 +47,8 @@ ma.meta_analysis(
     data=None,
     *,
     effect,
-    variance,
+    variance=None,
+    standard_error=None,
     study=None,
     subgroup=None,
     model="random",
@@ -66,7 +67,8 @@ Fits generic study effects using inverse-variance pooling.
 | --- | --- |
 | `data` | Optional DataFrame used by string-valued input selectors |
 | `effect` | Study effect column or array on a consistent model scale |
-| `variance` | Finite, strictly positive sampling variances—not standard errors |
+| `variance` | Finite, strictly positive sampling variances |
+| `standard_error` | Finite, strictly positive standard errors, squared internally |
 | `study` | Optional label column/array; defaults to index or row number |
 | `subgroup` | Optional subgroup column/array |
 | `model` | `"common"` or `"random"` |
@@ -77,6 +79,10 @@ Fits generic study effects using inverse-variance pooling.
 | `atol` | Strictly positive iterative-estimator tolerance |
 | `max_iter` | Positive iterative-estimator iteration limit |
 
+Supply exactly one of `variance` or `standard_error`. The selected argument
+supports the same DataFrame-column and array-like conventions as `effect`.
+Standard-error conversion is recorded in result provenance.
+
 ## `meta_binary()`
 
 ```text

{pymetaanalysis-0.1.0 → pymetaanalysis-0.2.1}/docs/releasing.md

@@ -44,7 +44,7 @@ and its
    `CITATION.cff`. Hatchling reads the package version dynamically from
    `_version.py`.
 4. Move the relevant `CHANGELOG.md` entries from `Unreleased` to a dated
-   heading such as `## 0.1.0 - 2026-07-15`.
+   heading such as `## X.Y.Z - YYYY-MM-DD`.
 5. Run the complete validation suite.
 
 The local consistency check is:
@@ -56,7 +56,7 @@ python tools/check_release.py
 For a proposed tag, add:
 
 ```console
-python tools/check_release.py --tag v0.1.0
+python tools/check_release.py --tag vX.Y.Z
 ```
 
 The tag check rejects development versions, version mismatches, and releases
@@ -90,8 +90,8 @@ commit:
 ```console
 git switch main
 git pull --ff-only
-git tag -a v0.1.0 -m "PyMetaAnalysis 0.1.0"
-git push origin v0.1.0
+git tag -a vX.Y.Z -m "PyMetaAnalysis X.Y.Z"
+git push origin vX.Y.Z
 ```
 
 The release workflow then:

{pymetaanalysis-0.1.0 → pymetaanalysis-0.2.1}/pyproject.toml

@@ -11,7 +11,7 @@ requires-python = ">=3.10"
 license = "MIT"
 license-files = ["LICENSE"]
 authors = [
-  { name = "PyMetaAnalysis contributors" },
+  { name = "Zhaobo Ding", email = "ding.zb@yahoo.com" },
 ]
 maintainers = [
   { name = "Zhaobo Ding", email = "ding.zb@yahoo.com" },

{pymetaanalysis-0.1.0 → pymetaanalysis-0.2.1}/src/meta_analyze/_version.py

@@ -1,3 +1,3 @@
 """Single source of truth for the package version."""
 
-__version__ = "0.1.0"
+__version__ = "0.2.1"