outdated stable version gets installed on Windows per README instructions

[dpprdan]

https://r-lib.github.io/p/pak/stable/win.binary/mingw32/x86_64 seems to point to outdated version, namely 0.2.0.9000.

(repo <- sprintf("https://r-lib.github.io/p/pak/stable/%s/%s/%s", .Platform$pkgType, R.Version()$os, R.Version()$arch))
#> [1] "https://r-lib.github.io/p/pak/stable/win.binary/mingw32/x86_64"
install.packages("pak", repos = repo)
#> Installing package into 'C:/Users/Daniel/Documents/R/win-library/4.1'
#> (as 'lib' is unspecified)
#> package 'pak' successfully unpacked and MD5 sums checked
#> 
#> The downloaded binary packages are in
#>  C:\Users\Daniel\AppData\Local\Temp\Rtmpwx7G5c\downloaded_packages
pak::pak_sitrep()
#> * pak version:
#> - 0.2.0.9000
#> * Version information:
#> - pak platform: x86_64-w64-mingw32 (current: x86_64-w64-mingw32, compatible)
#> - pak sha: 629a94a2afb708ffcb42fca53075eb146b0090f2
#> * Optional packages installed:
#> - tibble
#> * Library path:
#> - C:/Users/Daniel/Documents/R/win-library/4.1
#> - C:/Program Files/R/R-4.1.2/library
#> * Private library is embedded.

^{Created on 2022-03-21 by the reprex package (v2.0.1)}

I also see this message when I run install.packages("pak", repos = repo) outside {reprex}:

Installing package into ‘C:/Users/Daniel/Documents/R/win-library/4.1’
(as ‘lib’ is unspecified)
trying URL 'https://r-lib.github.io/p/pak/stable/win.binary/mingw32/x86_64/bin/windows/contrib/4.1/../../../../../../../mingw32/x86_64/pak_0.2.0.9000_R-4-1_x86_64-mingw32.zip'

[gaborcsardi]

The dev version is now called nightly build: https://github.com/r-lib/pak#nightly-builds

[dpprdan]

Sorry, I meant the installation instructions for the stable version. I would assume that at least to be v0.2.1 as per the CRAN version? Is my assumption wrong?

[gaborcsardi]

Yes, that is confusing, it will be sorted out soon.

[dpprdan]

Relatedly, pak_update() updates within the same "channel", so it wouldn't pick up 0.2.1 at the moment, IIUC. (Nothing to fix there IMHO, just observing that the above (may? - I did not check) cause this "downstream" issue).

[gaborcsardi]

I thinks this has been sorted out now.