Repository navigation
pkgdown workflow does not run staged dependencies although specified, not sure why?... #301
Description
Hi @walkowif and @llrs-roche
after your recent update on the default installation mechanism, I figured I need to manually specify to run staged dependencies because it seems only with that I can install cmdstanr successfully.
My question is about the pkgdown workflow - I do get an error for a missing package, and somehow the whole package installation step is skipped, and I don't see why.
Please check https://github.com/Genentech/jmpost/actions/runs/26988514096/job/79643775635
(Btw this is important for my work on the Roche/Genentech package jmpost.)
Thanks,
cheers
Daniel
Activity
llrs-roche commentedon Jun 5, 2026
Hi Daniel,
Yes, we changed the default because we were seeing some packages not being installed with the staged dependencies strategy and it is deprecated. This is surprising because the ggplot2.utils package is in Imports and should be available regardless of which strategy is used.
The GHA reports it couldn't be installed on the previous step and the action file describe the staged strategy which we didn't modify. I see you already tried twice to run the action.
What I don't see is the step "Run Staged dependencies 🎦" being run as in other jobs. I think on the yaml file you'll need to inline the option or some other change in order to trigger it back.
Instead of
Try something like
I triggered a check on ggplot2.utils repository just in case.
danielinteractive commentedon Jun 22, 2026
Thanks @llrs-roche ,
ggplot2.utilsI saw some documentation issues, fixing in Fix docs ggplot2.utils#100danielinteractive commentedon Jun 22, 2026
OK I figured it out with Copilot help... the handling of the string option is different between the workflows. The problem was the trailing newline, which was not stripped away here unfortuately. This works:
The - strips away the newline.
llrs-roche commentedon Jun 22, 2026
Thanks for reporting back the fix, I wasn't aware of this issue with
|.