Skip to content

chore: remove the stale requirements*.txt files - #979

Closed
cemililik wants to merge 2 commits into
developmentfrom
chore/remove-stale-requirements-files
Closed

cemililik wants to merge 2 commits into
developmentfrom
chore/remove-stale-requirements-files

Conversation

@cemililik

@cemililik cemililik commented Oct 17, 2026 •

Copy link
Copy Markdown
Collaborator

Summary

Deletes the three stale requirements*.txt files and the two places that referred to them. Dependabot's first scheduled run is Monday 2026-10-19, and its pip ecosystem scans requirements*.txt, so these files would have received weekly pull requests.

Related issues

Fixes #968

Changes

  • Delete requirements.txt, requirements-eval.txt, requirements-linux.txt.
  • .github/dependabot.yml — drop the note that asked for these files to be removed "when the tracked cleanup lands".
  • .dockerignore — drop the requirements*.txt line, which no longer matches anything.
  • CHANGELOG.md — a ### Removed entry.

How each file was confirmed unreferenced: no match in Dockerfile, docker-compose.yaml, MANIFEST.in, pyproject.toml, any workflow, tests/, tools/, forgelm/ (code), notebooks/, site/ or the documentation (README, CONTRIBUTING, the guides, reference, user manual, standards, QMS, design and roadmap pages). The only other hits are the CHANGELOG entry itself and a generic example inside a bundled chat template's training data (forgelm/templates/code-assistant/data.jsonl).

Left alone on purpose: the requirements.lock comment at the top of pyproject.toml and its decision row in docs/roadmap/risks-and-decisions.md (F-PR29-A6-lock-file). They are about a future lock file, not these three, and stay accurate.

This takes the issue off the good first issue list, which then has 15 open issues.

Type

  • CI / infrastructure

Testing

  • The full CLAUDE.md gauntlet from a clean worktree of this branch: exit 0.

Checklist

  • No documentation page changes, so no Turkish mirror applies
  • CHANGELOG entry under [Unreleased]

🤖 Generated with Claude Code

Summary by Sourcery

Remove stale requirements files to prevent unused dependency manifests from being maintained by Dependabot.

Enhancements:

  • Remove obsolete dependency requirement files and clean up their related configuration references.

Documentation:

  • Document the removal in the unreleased changelog.

Summary by CodeRabbit

  • Installation
    • Removed the standalone dependency lists for standard, evaluation, and Linux installations. Dependencies are now specified through project installation extras, so installation instructions that rely on the former lists may need updating.
  • Build Configuration
    • Matching requirements files are no longer excluded from Docker build contexts by default. This may change which files are included when building an image.

Three requirements files sat at the repository root and nothing used them: the Dockerfile, the
workflows, the tests and the documentation all install through the pyproject.toml extras. Their
floors were far below pyproject's (torch>=2.0.0 against >=2.4.0, transformers>=4.38.0 against
>=5.3.0), and Dependabot, which scans requirements*.txt, would have opened weekly pull requests
against them from its first run.

Also removes the note in .github/dependabot.yml that said they should be deleted when this cleanup
landed, and the requirements*.txt line in .dockerignore, which no longer matches anything. The
requirements.lock comment in pyproject.toml and its decision row in docs/roadmap/risks-and-decisions.md
are about a future lock file, not these three, and stay as they are.

Fixes #968

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@sourcery-ai

sourcery-ai Bot commented Oct 17, 2026 •

Copy link
Copy Markdown
Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Removes three unreferenced requirements manifests, along with stale Dependabot and Docker ignore references, and records the cleanup under the unreleased changelog; dependency installation continues to use pyproject.toml extras.

File-Level Changes

Change Details Files
Remove obsolete standalone dependency manifests now that dependency installation is defined through pyproject.toml extras.
  • Delete the three stale requirements files.
  • Verify the files are not referenced by project code, CI, packaging, tests, or documentation.
  • Preserve unrelated requirements.lock references describing a future lock-file decision.
requirements.txt
requirements-eval.txt
requirements-linux.txt
Clean up repository configuration that referred to the removed manifests.
  • Remove the obsolete Dependabot cleanup note.
  • Remove the unmatched requirements pattern from Docker ignore rules.
.github/dependabot.yml
.dockerignore
Document the removal in the unreleased changelog.
  • Add a Removed entry explaining the stale files, their lack of consumers, and Dependabot implications.
CHANGELOG.md

Assessment against linked issues

Issue Objective Addressed Explanation
#968 Remove the three unreferenced, stale requirements files, or regenerate and reference any that are load-bearing. ✅
#968 Record how the files were confirmed to be unreferenced. ✅
#968 Reconcile the pyproject.toml comment and roadmap decision about requirements.lock with the removal. ✅

Possibly linked issues


Tips and commands

Interacting with Sourcery

  • Trigger a new review: Comment @sourcery-ai review on the pull request.
  • Continue discussions: Reply directly to Sourcery's review comments.
  • Generate a GitHub issue from a review comment: Ask Sourcery to create an
    issue from a review comment by replying to it. You can also reply to a
    review comment with @sourcery-ai issue to create an issue from it.
  • Generate a pull request title: Write @sourcery-ai anywhere in the pull
    request title to generate a title at any time. You can also comment
    @sourcery-ai title on the pull request to (re-)generate the title at any time.
  • Generate a pull request summary: Write @sourcery-ai summary anywhere in
    the pull request body to generate a PR summary at any time exactly where you
    want it. You can also comment @sourcery-ai summary on the pull request to
    (re-)generate the summary at any time.
  • Generate reviewer's guide: Comment @sourcery-ai guide on the pull
    request to (re-)generate the reviewer's guide at any time.
  • Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
    pull request to resolve all Sourcery comments. Useful if you've already
    addressed all the comments and don't want to see them anymore.
  • Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
    request to dismiss all existing Sourcery reviews. Especially useful if you
    want to start fresh with a new review - don't forget to comment
    @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

  • Enable or disable review features such as the Sourcery-generated pull request
    summary, the reviewer's guide, and others.
  • Change the review language.
  • Add, remove or edit custom review instructions.
  • Adjust other review settings.

Getting Help

@coderabbitai

coderabbitai Bot commented Oct 17, 2026 •

Copy link
Copy Markdown
Contributor

Review in Change Stack →

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration
  • Configuration used: defaults
  • Review profile: CHILL
  • Plan: Essentials
  • Run ID: ae758274-0911-447a-887b-9ac173bc6855
📥 Commits

Reviewing files that changed from the base of the PR and between f24ab76 and 95179a7.

📒 Files selected for processing: 1
  • CHANGELOG.md
🚧 Files skipped from review as they are similar to previous changes: 1
  • CHANGELOG.md

Included review availability: This review used your included allowance. 2 included reviews remain after this review. Your included PR review attempts over the past 7 days set your current allowance at 3 reviews per hour.

📝 Walkthrough

The pull request deletes three root requirements files. It removes the matching Docker ignore pattern and a related Dependabot comment. The changelog records the removals and directs installation to pyproject.toml extras.

Changes: Legacy dependency manifests

Layer / File(s) Summary
Remove legacy requirements files
requirements.txt, requirements-eval.txt, requirements-linux.txt, .dockerignore, .github/dependabot.yml, CHANGELOG.md
Deletes the three requirements files and removes the Docker ignore pattern and Dependabot comment. The changelog records the removals and points to pyproject.toml extras for installation.

Priority: ⬇️ Low

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

Change: Other · Severity of issue fixed: Low

Merge Risk: ⚪ Minimal · up to 95179

This change removes stale, unused dependency manifests, and installation continues through pyproject.toml extras. No actionable merge risk was identified.

Pre-merge checks: Passed 5
Check name Status Explanation
Title check Passed The title clearly and concisely describes the main change: removal of the stale requirements files.
Description check Passed The description is mostly complete. It includes the summary, linked issue, changes, type, testing result, checklist items, cleanup rationale, and confirmation that the files were unreferenced.
Linked Issues check Passed Issue #968 requires deletion of the three stale files or regeneration of any load-bearing file. The PR deletes requirements.txt, requirements-eval.txt, and requirements-linux.txt. The PR records…
Out of Scope Changes check Passed The changes stay within issue #968. The .github/dependabot.yml note and .dockerignore pattern are stale references to the deleted files. The CHANGELOG.md entry documents the requested removal. N…
Docstring Coverage Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
Full details: Linked Issues check

Explanation

Issue #968 requires deletion of the three stale files or regeneration of any load-bearing file. The PR deletes requirements.txt, requirements-eval.txt, and requirements-linux.txt. The PR records repository-wide checks that confirmed each file was unreferenced. The pyproject.toml comment and roadmap decision row remain accurate because they describe a future requirements.lock workflow, not the deleted files. The existing pyproject.toml dependencies and extras cover the deleted dependency entries.

Full details: Out of Scope Changes check

Explanation

The changes stay within issue #968. The .github/dependabot.yml note and .dockerignore pattern are stale references to the deleted files. The CHANGELOG.md entry documents the requested removal. No unrelated implementation or dependency behavior change is shown.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

@sourcery-ai sourcery-ai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hey - I've reviewed your changes and they look great!

Sourcery assessment

Approved.


Sourcery is free for open source - if you like our reviews please consider sharing them ✨

@cemililik

Copy link
Copy Markdown
Collaborator Author

Superseded by #996: the wave-0 fixes are combined by theme into five pull requests to cut the review load. This branch's commits are included there unchanged apart from the CHANGELOG.md merge; the branch stays on the remote.

@cemililik cemililik closed this Oct 18, 2026
cemililik added a commit that referenced this pull request Oct 18, 2026
…medical template row (#996)

## Summary

Three small, already-reviewed fixes combined into one pull request,
replacing #979, #980 and #981 (which will be closed as superseded). Each
was green on its own and the bot findings on #980 and #981 are already
folded in.

## Related issues

Fixes #968. Refs #91, #75, #97.

## Changes

| Was | What it does |
|---|---|
| #979 | Deletes the stale `requirements.txt`, `requirements-eval.txt`
and `requirements-linux.txt`. Nothing referenced them, their floors were
far below `pyproject.toml`'s, and Dependabot would have opened weekly
PRs against them. Merging this **before Monday 2026-10-19** avoids those
PRs. |
| #980 | Roadmap/strategy corrections: `forgelm chat` does not screen
for safety and reads no YAML (#91); live risk rows no longer name a past
"August 2026" deadline and now limit the dates to Chapter III Sections
1–3 as CodeRabbit asked (#75); `docs/product_strategy.md` (EN+TR) names
the real `evaluation.auto_revert` field. |
| #981 | The `medical-qa-tr` row of the YAML templates reference
(EN+TR): the template enables no safety evaluation and has no
`risk_assessment` metadata; it is not for clinical decision support, and
the row says to set `evaluation.safety.enabled: true` and fill in
`risk_assessment` accurately (Sourcery and CodeRabbit findings applied).
|

## Type

- [x] Documentation
- [x] Chore

## Testing

- The full `CLAUDE.md` gauntlet from a clean worktree of this branch:
exit 0.

## Checklist

- [x] English and Turkish mirrors updated together
- [x] CHANGELOG entries under `[Unreleased]`

🤖 Generated with [Claude Code](https://claude.com/claude-code)

## Summary by Sourcery

Remove stale dependency files and correct safety, compliance, and
medical-template documentation across the project.

Bug Fixes:
- Correct roadmap, risk, and strategy documentation to accurately
describe chat safety behavior, EU AI Act timelines, and the current
evaluation auto-revert configuration.
- Clarify the medical QA template’s safety limitations and required
evaluation and risk-assessment settings in English and Turkish
references.

Enhancements:
- Remove the obsolete requirements files and direct installation
guidance through pyproject.toml extras.

Documentation:
- Update the English and Turkish documentation mirrors and record the
housekeeping and documentation corrections in the unreleased changelog.

---------

Co-authored-by: Claude Sonnet 5.5 <noreply@anthropic.com>
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.

Remove the unreferenced, stale requirements*.txt files (Dependabot will keep bumping them)

1 participant