Switch the windows-11-arm job back to the stable pak after next pak release
Maintainers usually reply within 1 day
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
Research direction
Read .github/workflows/R-CMD-check.yaml and check whether a pak release newer than 0.11.1 is available, as specified in the issue. Once it is, remove pak-version: devel from the windows-11-arm matrix entry and run or inspect that job; done means setup-r-dependencies completes in a couple of minutes.
Written by the indexing model from the issue text.
Description
In #1304 we set pak-version: devel on the windows-11-arm matrix entry in .github/workflows/R-CMD-check.yaml because the stable pak (0.11.1, 2026-07-22) predates pkgcache's support for the clang-aarch64 package type (r-lib/pkgcache#142, 2026-07-30) and builds every dependency from source there (27 minutes instead of 2). Once a pak release newer than 0.11.1 is out, we should drop the pak-version line and check that the ARM job's setup-r-dependencies step still takes a couple of minutes. More details in r-lib/pkgdepends#486.
- Dominant language
- R
- Stars
- 161
- Forks
- 69
- Avg merge
- 1d 8h
- Merged PRs (30d)
- 40
Getting set up
- No Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from stan-dev/cmdstanr
-
documentation
Difficulty 2/5 1-3 hours Newbie friendliness 64/100
stan-dev/cmdstanr#506 · 6 comments · 1 reaction ·
Maintainers usually reply within 1 day
-
Let fits compress their own output CSVsPossibly taken @VisruthSK claimed this 10 days ago. Openfeature
Difficulty 5/5 Over a week Newbie friendliness 42/100
stan-dev/cmdstanr#1276 · 1 comment · 1 assignee ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 25/100
Maintainers usually reply within 1 day
-
internal-code
Difficulty 5/5 Over a week Newbie friendliness 30/100
Maintainers usually reply within 1 day
-
feature
Difficulty 4/5 3-5 days Newbie friendliness 35/100
stan-dev/cmdstanr#1175 · 1 comment · 2 reactions ·
Maintainers usually reply within 1 day
All issues in stan-dev/cmdstanr
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
eduaguilera/whep#1489 ·
Maintainers usually reply within 4 days
-
Difficulty 2/5 1-3 hours Newbie friendliness 65/100
-
bug code cleaning
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
furrer-lab/abn#272 ·
-
R CMD check red on main: load_* loader tests fail (2026-season release assets not published yet)Open
Difficulty 2/5 1-3 hours Newbie friendliness 69/100
sportsdataverse/hoopR#227 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 92/100
philchalmers/SimDesign#106 ·