Posit's shinyapps.io shutdown hands R teams a dated migration, not an optional upgrade

The break is narrow and mechanical, which is why it tends to sit untouched until a deploy fails. The pattern published on r-bloggers three years ago was a commit hook: push to the repository, and a GitHub Actions job bundled the Shiny source and sent it to shinyapps.io ^[6]. Most of that machinery survives, because the deployment methods that worked against shinyapps.io still work against Posit Connect Cloud ^[7]. What changes is the paperwork at each end. The Actions route now begins by obtaining a Content ID ^[8]. The Git-backed route wants a manifest.json committed alongside the code, which in R is usually one call to `rsconnect::writeManifest()` ^[9]. Neither is difficult. Both are edits to a workflow file nobody has opened since it was written, on content Posit will move for you in early 2027 whether the edit happened or not ^[2].

The post's own recommendation is to stop deploying from Actions and let Connect Cloud watch the branch, on the grounds that the deployment work no longer consumes your GitHub Actions allowance ^[10]. That saves compute minutes, and it also moves where trust sits, since the platform is granted access to the GitHub account ^[9]. The same post lists the cases where that trade does not close, and they are not exotic for anyone with a review process. You give up deploying only after earlier pipeline checks have passed ^[11]. You may be barred from granting a third-party tool access to an account that holds sensitive code elsewhere ^[12]. On the free tier with a private repository, the option is not on the table ^[13].

The migration therefore sorts teams by how their deployment was built rather than by what their app does. Anyone who shipped by clicking Deploy in RStudio and thinking no further about packages or containers ^[21] has little to do beyond noting that a free tier survived ^[4]. Anyone with a gated pipeline has a small rewrite with a deadline attached. On price the direction is not uniform: paid plans sit above their nearest shinyapps.io equivalents ^[5], while the custom domain that used to require the $349 per month Professional tier now appears on the $59 per month Enhanced tier with an SSL certificate ^[15][16].

The schedule is the part worth writing down. According to the r-bloggers account, Posit gave roughly eleven months between the January 2026 announcement and the end-of-2026 close to new apps ^[18], then named a part of a year rather than a date for the automatic migration ^[2]. A pipeline that breaks during that migration breaks at a moment somebody else picked.