Skip to content

chore: prepare v0.1.1 release - #27

Merged
AdishAssain merged 1 commit into
mainfrom
chore/release-0.1.1
Sep 14, 2026
Merged

AdishAssain merged 1 commit into
mainfrom
chore/release-0.1.1

Conversation

@AdishAssain

@AdishAssain AdishAssain commented Sep 14, 2026 •

Copy link
Copy Markdown
Member

Bumps the version to 0.1.1 across packaging metadata, the lockfile, and the
fallback version strings used when the package is not installed.

The published 0.1.0 release predates the fix that keeps every factor of a
coupled infection rate expression, so it computes those flows with factors
dropped. This release carries that fix.

Citation metadata moves to 0.1.1. The DOI fields hold the concept DOI, which
resolves to the newest archive, because Zenodo mints a version DOI only after
the release is published. Both are updated to the 0.1.1 version DOI once it
exists.

The release count is dropped from the paper so the sentence stays accurate
across future releases.

Verification: ruff clean, 183 tests pass, CITATION.cff valid per CFF schema
1.2.0, paper.md 1705 words.

Summary by CodeRabbit

  • Release

    • Updated the package to version 0.1.1.
    • Updated displayed version information and release dates across project metadata.
  • Documentation

    • Added the 0.1.1 changelog entry.
    • Updated citation and publication metadata for version 0.1.1.
    • Updated the research impact statement to reflect three tagged releases.

Bump the version across packaging metadata, the lockfile, and the fallback
version strings used when the package is not installed.

v0.1.0 predates the fix that keeps every factor of a coupled infection rate
expression, so the currently published release computes those flows with
factors dropped. This release carries that fix.

Citation metadata moves to 0.1.1. The DOI fields hold the concept DOI, which
resolves to the newest archive, because Zenodo mints a version DOI only after
the release is published; both are updated to the 0.1.1 version DOI once it
exists.

Drop the release count from the paper so the sentence stays accurate across
future releases.
@coderabbitai

coderabbitai Bot commented Sep 14, 2026 •

Copy link
Copy Markdown

Review Change StackReview Change Stack

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Advanced

Run ID: 397099bc-e806-47ce-a8d5-3acbc6b17815

📥 Commits

Reviewing files that changed from the base of the PR and between 7f8ed01 and f9f3fac.

⛔ Files ignored due to path filters (1)
  • uv.lock is excluded by !**/*.lock
📒 Files selected for processing (7)
  • CHANGELOG.md
  • CITATION.cff
  • paper.bib
  • paper.md
  • pyproject.toml
  • src/patchsim/__init__.py
  • src/patchsim/calibration.py

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.


📝 Walkthrough

Walkthrough

The project version changed to 0.1.1. Runtime fallback values, changelog data, citation metadata, DOI references, and the reported PyPI release count were updated to match the release.

Changes

Release 0.1.1 version and metadata

Layer / File(s) Summary
Package version alignment
pyproject.toml, src/patchsim/__init__.py, src/patchsim/calibration.py
The declared project version and runtime fallback values changed from 0.1.0 to 0.1.1.
Release records
CHANGELOG.md, CITATION.cff, paper.bib, paper.md
Release 0.1.1 was added to the changelog. Citation metadata and DOI references were updated. The research statement now reports three tagged PyPI releases.

Priority: ⬇️ Low

Estimated code review effort: 1 (Trivial) | ~5 minutes

Change: Other

Merge Risk: ⚪ Minimal · up to f9f3f

The release metadata is internally consistent and no merge-blocking risk is established.

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 2 files. (5 skipped: 5 … Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely describes the main change: preparing the project for the v0.1.1 release. This matches the version, citation, packaging, and documentation updates.
Linked Issues check ✅ Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check ✅ Passed Check skipped because no linked issues were found for this pull request.
Full details: Docstring Coverage

Explanation

Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 1 functions across 2 files. (5 skipped: 5 unsupported.)

  • Fix all pre-merge checks with AI
✨ Finishing Touches 💡 1
📝 Generate docstrings 💡
  • Create stacked PR
  • Commit on current branch
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch chore/release-0.1.1

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@AdishAssain
AdishAssain merged commit 6067277 into main Sep 14, 2026
4 checks passed
@AdishAssain
AdishAssain deleted the chore/release-0.1.1 branch September 14, 2026 10:43
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