Repository navigation
release: 0.1.0 - #128
Merged
Merged
release: 0.1.0#128
Conversation
- CHANGELOG.md: 0.1.0 section, fragments collected - README and quickstart: pip install dokimi - releasing.md: python_min for the conda-forge recipe Signed-off-by: vchamarthi <venkata.sai.gireesh.chamarthi@intel.com>
vchamarthi
requested review from
antonwolfy,
jharlow-intel,
napetrov and
xaleryb
as code owners
October 19, 2026 16:57
There was a problem hiding this comment.
🔵 Needs a closer look
Prerequisite #126 remains open, so a maintainer must confirm its merge and collect its fragment before final approval.
No open issues 🎉
What changed in this PR
Prepares dokimi’s first PyPI release, 0.1.0, without changing runtime code or publishing the package.
Changes:
- Consolidates release notes and removes 15 collected fragments.
- Lists PyPI installation before source-checkout options.
- Documents conda-forge’s minimum-Python recipe settings.
| File | Description |
|---|---|
| dokimi/README.md | Adds PyPI installation instructions. |
| dokimi/docs/releasing.md | Clarifies conda-forge Python requirements. |
| dokimi/docs/quickstart.md | Lists released-package installation first. |
| dokimi/CHANGELOG.md | Adds consolidated 0.1.0 release notes. |
| dokimi/changelog.d/20261019_120000_antonwolfy_api-reference-package-pages.md | Removes docs-only fragment without an entry. |
| dokimi/changelog.d/20261018_120000_vchamarthi_partial-conflict-not-cleared.md | Collects conflict-coverage fix. |
| dokimi/changelog.d/20261018_120000_napetrov_ci-deptry.md | Collects dependency cleanup. |
| dokimi/changelog.d/20261017_124500_antonwolfy_repo-build-timeout.md | Collects build-timeout options. |
| dokimi/changelog.d/20261017_123000_antonwolfy_judge-provider-default.md | Collects judge-provider defaults. |
| dokimi/changelog.d/20261017_121600_antonwolfy_benchmark-persona-docs.md | Removes docs-only fragment. |
| dokimi/changelog.d/20261017_121500_antonwolfy_tool-preference-cost-cap.md | Consolidates cost-cap fixes. |
| dokimi/changelog.d/20261016_192848_napetrov_feat-questions-v2.md | Collects question-format changes. |
| dokimi/changelog.d/20261016_190100_napetrov_judge_materials.md | Collects stored judging material support. |
| dokimi/changelog.d/20261016_190000_napetrov_empty-question-rule.md | Collects missing-question validation. |
| dokimi/changelog.d/20261016_174000_napetrov_outcome-contracts.md | Collects pinned-question behavior. |
| dokimi/changelog.d/20261016_130000_nikolay.a.petrov_harnesses_on_runner.md | Collects process-timeout handling. |
| dokimi/changelog.d/20261016_122905_napetrov_feat-tool-preference-cost-cap.md | Consolidates cost-cap feature notes. |
| dokimi/changelog.d/20261016_122720_napetrov_refactor-novelty-bundle.md | Collects novelty artifact metadata. |
| dokimi/changelog.d/20261014_000000_versioning.md | Collects versioning and packaging notes. |
Review effort: Balanced
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #128 +/- ##
==========================================
- Coverage 90.30% 90.28% -0.02%
==========================================
Files 206 206
Lines 24356 24356
Branches 3923 3923
==========================================
- Hits 21995 21991 -4
- Misses 1695 1698 +3
- Partials 666 667 +1 🚀 New features to boost your workflow:
|
napetrov
approved these changes
Oct 19, 2026
Signed-off-by: vchamarthi <venkata.sai.gireesh.chamarthi@intel.com>
6 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The release PR for 0.1.0, the first PyPI release. Part of #123.
dokimi/ ├── CHANGELOG.md + ## [0.1.0] section ├── changelog.d/ - 15 fragments (collected) ├── README.md + pip install dokimi └── docs/ ├── quickstart.md + pip install dokimi └── releasing.md + python_min in the conda-forge recipe stepproject.versionis already0.1.0, so nothing is bumped.Changes
CHANGELOG.md:scriv collect --version 0.1.0, then edited to one line per entry. It covers every merged PR since the repository went public, including the ones from before changelog fragments existed (build: versioned releases from 0.1.0 — changelog fragments, working wheel, release workflow #39): new commands, the default-model change, dropped Python 3.10, and the fixes that change scores. CI, test, lint, refactor-only and contributor-docs PRs are left out.pip install dokimifirst, with the checkout installs after it.docs/releasing.md: the conda-forge step says how anoarch: pythonrecipe usespython_min, per conda-forge's noarch guide.Before merge
scriv collect --version 0.1.0here so its fragment lands in the section. Until then, the conda-forge note inreleasing.md("every runtime dependency is on conda-forge") does not hold.## [0.1.0] — 2026-10-19if the tag is created on another day.pypienvironment andPYPI_PUBLISHare not set up yet (Release 0.1.0: PyPI and conda-forge #123). Merging this publishes nothing.Evidence
python scripts/check_release.py v0.1.0: before, it fails with no## [0.1.0]entries and 15 uncollected fragments; after, it passes.release.yml:python -m build(wheel from the sdist),twine check --strictpasses for both files, andscripts/smoke_installed.py --expect-version 0.1.0passes every check on the installed wheel.tests/test_docs_links.py,tests/test_packaging.pyandtests/test_check_release.pypass (38), and so doesmkdocs build --strict.Merge Danger
Door: two-way. Docs and changelog only; the release itself is a separate step (
gh release create v0.1.0).Blast Radius: docs
Open PRs that add fragments after this merges go into the next version's section.
Checklist
pytestpassesruff,mypy, and schema checks pass.github/.licenserc.yaml)