Since the update to v.0.9.3 I can't install internal packages via the Remotes field in the DESCRIPTION using the github action setup-r-dependencies which uses pak.
The AI agent gave me this as the likely reason:
The error originates from pak 0.9.3 (released April 8-9, 2026, bundling pkgdepends 0.9.1). When pak resolves dependencies, it reads the Remotes field from DESCRIPTION files and passes entries like packagename=git :: https://enterprise.ghe.com/ORG/packagename.git to
parse_pkg_refs() -> get_remote_types(). In the new version, this parsing fails with "Cannot parse package".
The critical flow (dep-utils.R:89-95):
resolve_ref_deps() always parses ALL Remotes entries eagerly:
if (!is.na(remotes)) {
remotes <- str_trim(na.omit(remotes))
remotes <- parse(remotes)
remotes packages <- check_names(parse_pkg_refs(remotes)) # <-- fails HERE
...
The commit history between 0.9.0 and 0.9.1 includes a bulk "reformat with air" (85fac3e), which is the most likely source of a subtle regex/parsing regression in how pkg-git :: url is handled.
Cheers
Since the update to v.0.9.3 I can't install internal packages via the Remotes field in the DESCRIPTION using the github action setup-r-dependencies which uses pak.
The AI agent gave me this as the likely reason:
The error originates from pak 0.9.3 (released April 8-9, 2026, bundling pkgdepends 0.9.1). When pak resolves dependencies, it reads the Remotes field from DESCRIPTION files and passes entries like packagename=git :: https://enterprise.ghe.com/ORG/packagename.git to
parse_pkg_refs() -> get_remote_types(). In the new version, this parsing fails with "Cannot parse package".
The critical flow (dep-utils.R:89-95):
resolve_ref_deps() always parses ALL Remotes entries eagerly:
if (!is.na(remotes)) {
remotes <- str_trim(na.omit(remotes))
remotes <- parse(remotes)
remotes packages <- check_names(parse_pkg_refs(remotes)) # <-- fails HERE
...
The commit history between 0.9.0 and 0.9.1 includes a bulk "reformat with air" (85fac3e), which is the most likely source of a subtle regex/parsing regression in how pkg-git :: url is handled.
Cheers