However, Posit Connect Cloud always installs commit 73284c4 (version 0.1.5), regardless of what branch or tag I specify in RemoteRef. I have tried main, v0.1.6 (tag), and release-0.1.6 (branch) — all result in the same old commit being installed.
The tag and branch exist on GitHub and point to the correct commit (3a971b0). The renv.lock is committed and pushed correctly.
Is there a way to clear the package cache on Posit Connect Cloud, or force it to respect the RemoteSha in the lockfile?
How are you deploying to connect cloud? Is it through the UI by providing a GitHub org/repo, or is it through something like Posit Publisher (where it installs what you have running on your local machine?)
If its from GitHub, you should check to see what is defined in manifest.json as that is the file used by Connect Cloud to find dependencies.
If its from Publisher (or RStudio) you should double check that you are locally running the version you want to install in Connect Cloud.
If you have a content id, I can take a closer look.
[quote="samp, post:2, topic:213411, full:true"]
How are you deploying to connect cloud? Is it through the UI by providing a GitHub org/repo, or is it through something like Posit Publisher (where it installs what you have running on your local machine?)
If its from GitHub, you should check to see what is defined in manifest.json as that is the file used by Connect Cloud to find dependencies.
If its from Publisher (or RStudio) you should double check that you are locally running the version you want to install in Connect Cloud.
If you have a content id, I can take a closer look.
thanks
sam
[/quoteHi Sam,
Thanks for the pointer — that was indeed the issue. I'm deploying from GitHub (Git-backed publishing, auto-republish on push).
The root cause on my end: manifest.json is generated locally with rsconnect::writeManifest(), and it only picks up the GithubSHA1/RemoteSha info if the package is actually installed via remotes::install_github() at generation time. I was mostly working with pkgload::load_all() locally, so my installed copy never had those Github* fields set — which meant writeManifest() captured a stale (or entirely missing) commit reference for the package itself, even though the surrounding app files were being pulled from the latest commit.
Fix that's working for me now: before running writeManifest(), I make sure to run remotes::install_github("owner/repo", force = TRUE) first (in a fresh R session, since pkgload::load_all() in the same session masks the installed version). That correctly stamps the current commit SHA into the manifest.
Just wanted to close the loop here in case it helps someone else hitting the same "stale commit" symptom. Thanks again for the nudge in the right direction.