paper/results-frozen/MANIFEST.md's Provenance table says scikit-learn 1.9.0, but its own linked requirements-lock.txt pins 1.8.0
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Newbie friendliness
- 90/100
- Issue type
- Documentation
- Clarity
- Clearly specified
- Activity status
- Active
- Tech stack
- python, scikit-learn
- Domain
- documentation
Research direction
The issue is in the file paper/results-frozen/MANIFEST.md. Open that file, locate the Provenance section around line 13, and change the scikit-learn version from 1.9.0 to 1.8.0 to match the version in paper/results-frozen/requirements-lock.txt. Verify the change by running the grep command from the issue description to ensure the versions now align.
Written by the indexing model from the issue text.
Description
Where: paper/results-frozen/MANIFEST.md, Provenance section (- **scikit-learn:** 1.9.0), vs. paper/results-frozen/requirements-lock.txt.
The gap: MANIFEST.md's "Provenance" section states the frozen snapshot's environment as scikit-learn: 1.9.0, and explicitly says "Full environment: requirements-lock.txt in this folder" - pointing readers at that exact file to reproduce the snapshot. But that file pins a different version:
Repro:
$ grep -n "scikit-learn" paper/results-frozen/MANIFEST.md paper/results-frozen/requirements-lock.txt
paper/results-frozen/MANIFEST.md:13:- **scikit-learn:** 1.9.0
paper/results-frozen/requirements-lock.txt:78:scikit-learn==1.8.0
Every other version MANIFEST.md declares (Python 3.13.2, fairlearn 0.14.0, pandas 3.0.2, numpy 2.4.4) matches its own requirements-lock.txt exactly - only scikit-learn is off. The root repo's current requirements-lock.txt pins scikit-learn==1.9.0, which is almost certainly where the 1.9.0 figure in MANIFEST.md was copied from by mistake, rather than from the frozen snapshot's own lock file.
Fix direction: Change MANIFEST.md's Provenance line to scikit-learn: 1.8.0 to match paper/results-frozen/requirements-lock.txt, the file it tells readers to install from.
- Dominant language
- HTML
- Stars
- 47
- Forks
- 45
- Avg merge
- 1h 53m
- Merged PRs (30d)
- 97
Getting set up
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from yakew7/Fair-Code
-
bug documentation
Difficulty 1/5 Under an hour Newbie friendliness 95/100
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 1/5 Under an hour Newbie friendliness 95/100
Maintainers usually reply within 1 day
-
documentation good first issue
Difficulty 2/5 1-3 hours Newbie friendliness 92/100
yakew7/Fair-Code#731 · 1 comment ·
Maintainers usually reply within 1 day
-
bug documentation
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
enhancement help wanted
Difficulty 4/5 3-5 days Newbie friendliness 58/100
Maintainers usually reply within 1 day
All issues in yakew7/Fair-Code
Similar issues
-
Link Checker ReportOpenautomated issue report
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
supabase/agent-skills#611 ·
-
Difficulty 1/5 1-3 hours Newbie friendliness 75/100
isocpp/CppCoreGuidelines#2338 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
polka-codes/test#345 ·
Maintainers usually reply within 1 day