You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Research: which Manifest & dependencies issues are resolved or obsolete? #959
For each open issue in the Manifest & dependencies batch, is it already resolved, obsolete, still valid, or unclear? Find the evidence and propose a closing comment for each one marked resolved or obsolete.
Output: a verdict table on branch research/groom-manifest with these columns: issue, verdict, evidence (PR/commit/code ref/CLI output), proposed close reason (completed / not planned / duplicate-of), and draft 🤖 closing comment. Follow the verdict rules in the map's Notes.
The file has the evidence and draft closing comments for the 4 issues proposed for closing. Nothing in the backlog was commented on, labelled, or closed. That waits for review in #960.
Activity
tdstein commentedon Nov 10, 2026
🤖 Verdict table: https://github.com/posit-dev/rsconnect-python/blob/research/groom-manifest/research/groom-manifest.md
Counts (15 issues):
html/staticto commands forrsconnect write-manifest#611 duplicate of write-manifest lacks html and other-content subcommands #548)--package-installersilently ignored in two commands and unusable as documented on click >= 8.2 #852, Generate a Python version requirement for requirements.txt-only projects #854, write-manifest checksum does not match an existing requirements.txt that lists rsconnect #857)rsconnect deployfails with hierarchicalrequirements.txt#348, which needs a live Connect server to check how it resolves nested-rrequirements)The file has the evidence and draft closing comments for the 4 issues proposed for closing. Nothing in the backlog was commented on, labelled, or closed. That waits for review in #960.