Repository navigation
Closed
11 / 1111 of 11 issues completedClosed
11 / 1111 of 11 issues completed
Copy link
Labels
wayfinder:mapWayfinder map (index of a planning effort)Wayfinder map (index of a planning effort)
Description
Destination
Every open issue (excluding the Python EOL effort) has been checked for whether it is already resolved or obsolete. Those issues are closed with an evidence-backed comment. Everything else is untouched and waits for a later grooming pass.
Notes
- Execution override: this map does its own closing. Each batch's review ticket ends with the approved issues closed. Closing is cheap and reversible.
- Verdicts (one per issue):
- Resolved: a later change fixed it. Cite a PR, commit, code reference, or CHANGELOG entry.
- Obsolete: no longer applies. The feature was removed, a Python or Connect version is unsupported, the workflow was superseded, or it duplicates another issue.
- Still valid: leave open, untouched. This includes "won't do" product calls (e.g. renaming commands), which a later prioritization pass decides.
- Unclear: not enough evidence. Leave open.
- Evidence: researchers read code and git history, and may run the CLI locally (
uv run rsconnect …,write-manifest,--help) against temp dirs. They never call a live Connect, shinyapps.io, or Connect Cloud server. Anything that needs a live server is Unclear. - Duplicates: keep the issue with the clearer spec or more discussion and close the other with
gh issue close --duplicate-of. The researcher proposes and the human decides. - Sign-off: nothing is closed on agent judgment alone. The human approves each batch's verdict table first.
- Closing: comment prefixed with "🤖 ", citing the evidence and inviting a reopen if it still affects the reader. Resolved issues close as
completed, obsolete ones asnot planned. Close immediately, with no waiting period. - Ticket pattern per batch: a research ticket (AFK) writes a verdict table to a
research/<name>branch, then a review-and-close task (HITL), blocked by it, applies the approved verdicts. - shinyapps.io is being decommissioned, so open issues specific to shinyapps.io are obsolete. Close them as
not plannedand link the migration guide. Connect Cloud deploys are still supported, so issues about them are not obsolete by default.
Decisions so far
- Research: which Manifest & dependencies issues are resolved or obsolete?: 15 issues: 2 resolved, 2 duplicates, 10 still valid, 1 unclear (needs a live server). Verdicts
- Research: which Content management, CLI output & shinyapps.io issues are resolved or obsolete?: 27 issues: 3 resolved, 2 obsolete/duplicate, 19 still valid, 3 unclear (2 need a live server). Verdicts
- Research: which Docs, build, CI & dev tooling issues are resolved or obsolete?: 15 issues: 6 resolved, 2 obsolete, 7 still valid, 0 unclear. Verdicts
- Research: which Auth & server config issues are resolved or obsolete?: 14 issues: 2 resolved, 0 obsolete, 12 still valid, 0 unclear. Verdicts
- Research: which Deploy & bundling issues are resolved or obsolete?: 16 issues: 2 resolved, 1 obsolete, 10 still valid, 3 unclear. Verdicts
- Review and close: Docs, build, CI & dev tooling: all 8 verdicts approved. 6 closed as resolved, 2 as obsolete. 7 left open.
- Review and close: Auth & server config: both verdicts approved. stack trace when you have multiple saved servers and don't pick one #541 and Two-step device code login for environments that cannot wait for approval (login and add --connect-cloud) #858 closed as resolved. deploy fails to redeploy due to global config #646/error when existing content gone #542 overlap kept. 12 left open.
- Review and close: Manifest & dependencies: all 4 verdicts approved. Consider supporting additional dependency formats #327 and Unable to specify the installation of the current directory, which causes a ModuleNotFoundError #456 closed as resolved, quarto: write-manifest and deploy should recommend rsconnect when using knitr engine #565 and Add
html/staticto commands forrsconnect write-manifest#611 as duplicates. 11 left open. - Review and close: Deploy & bundling: 2 of 3 verdicts approved. [1.21.1] unable to build from tar.gz file #520 closed as resolved, deploy notebook --static uses default nbconvert timeout #178 as obsolete. Separate bundling from deployment #634 rejected as only partly resolved (no local build-only command) and kept open. 14 left open.
- Review and close: Content management, CLI output & shinyapps.io: all 5 verdicts approved. Need a flag to stop web browser opening a new tab after successful deployment to shinyapps.io #462, Suggestion: rename
rsconnect deploy apicommand torsconnect deploy flask#491,RSConnectExecutor.server_settingsthrows error ifself.clientis aPositClientobject #547 closed as resolved, Set content_category on static outputs and revisions #474 as obsolete, rsconnect and predefined app name/url #357 as a duplicate of [Question] Adding a custom URL to an app during deployment #332. 22 left open. - Verify or defer the Unclear verdicts?: deferred, no verification. shinyapps.io is being decommissioned, so Deployment to shinyapps.io with a shiny app fails with 599 status code #465, Unable to Deploy Shiny for Python app to Shiny Apps IO #455, Raise an error if providing environment variables to shinyapps.io #439, rsconnect deploy --help is wrong? (Suggests shinyapps.io supports non-shiny apps) #481, Add "applications" method to rsconnect-python (already exists on R version) #654 were closed as
not planned.rsconnect deployfails with hierarchicalrequirements.txt#348, No requirements whendeploy giterror handling #516, KeyError: 'id' when deploying jupyter notebook #523, inconsistent file_checksum #382, write-manifest include extras files not working correctly on Windows #419 were left open for triage.
Not yet specified
Out of scope
- Verifying Unclear verdicts against a live server, Windows, or the reporter: even a confirmed repro only makes an issue "still valid". The evidence for the later triage pass is in the batch verdict tables. See Verify or defer the Unclear verdicts?.
- Removing shinyapps.io support from the CLI (deploy target, help text, tests): a code change for a separate effort, not grooming.
- Python EOL effort (Drop support for EOL Python #942–Modernize syntax for Python 3.11 (ruff UP) #951): freshly specified and actively planned, so it has nothing to groom.
- Prioritization,
wontfix,needs-info, and triage labelling of still-valid issues: these are product decisions for a later grooming pass, not "already resolved or no longer an issue".
Metadata
Metadata
Assignees
Labels
wayfinder:mapWayfinder map (index of a planning effort)Wayfinder map (index of a planning effort)
Activity
tdstein commentedon Nov 10, 2026
🤖 Destination reached: every batch has been reviewed and closed, and the Unclear verdicts were deferred. Closing the map.