[tdstein]

Summary

• Preserve the resolved requirements source when writing framework manifests so --force-generate uses pip freeze.
• Add CLI regression coverage for generated and explicitly supplied requirements files.

Validation

• Focused manifest and environment tests (69 tests).
• Ruff lint and formatting checks; committed diff check.

Closes #888

[github-actions]

PR Preview Action v1.8.1
Preview removed because the pull request was closed.
2026-10-28 13:25 UTC

[github-actions]

☂️ Python Coverage

current status: ✅

Overall Coverage

Lines	Covered	Coverage	Threshold	Status
11019	9681	88%	0%	🟢

New Files

No new covered files...

Modified Files

File	Coverage	Status
rsconnect/main.py	85%	🟢
TOTAL	85%	🟢

updated for commit: 577cb37 by action🐍

[tdstein]

@amol- it looks like you originally introduced the behavior that I'm undoing in this change. Mind taking a look to confirm this change is appropriate?

[amol-]

I think this looks good manifest_writer is already resolving the requirements file option, so _write_framework_manifest has no need to resolve it again.

To be honest, given that _write_framework_manifest is only ever used by manifest_writer I'm not even sure the reason why it should exist as a separate entity. Having them separated increases the risk of this type of errors by making harder to keep track of the interactions between the two.