Skip to content

Releases

Nightly build

Nightly build Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 18 Nov 18:37

Automated build of main at 34f0a2a.

Version: 0.11.2-dev.20261118.g34f0a2a. Built: 2026-11-18 18:37 UTC.

These builds are not signed or notarized and are not meant for production use.

Changes since v0.11.1: v0.11.1...34f0a2a

rig 0.11.1

Choose a tag to compare

@gaborcsardi gaborcsardi released this 26 Oct 09:48
  • New rig proj sync --check option to check that the project
    environment is in sync with rproj.lock. It exits with status 1 if sync
    would install, update or remove any package, e.g. after packages were
    installed or removed by hand, and with status 2 on other errors (#495).

  • rig proj lock --check now exits with status 2 on errors, e.g. if there
    is no rproj.toml, and keeps status 1 for a missing or out of date
    rproj.lock.

  • rig proj sync --dry-run no longer fills in a missing .Renviron or
    .rvenvlib, it only says that sync would. It now fails if there is
    neither an rproj.toml nor an rproj.lock, like rig proj sync does.

  • New rig add --no-default option to install an R version without
    making it the default when no default R version is set yet, and
    rig add --without-path to skip putting rig's quick-link directory on
    the PATH (the shell startup files on macOS and Linux, the user PATH on
    Windows). Tools that run rig to install R, like RStudio, can use them to
    leave the user's default R, quick links, PATH and IDE settings alone.

  • rig list, rig add and other commands no longer fail on macOS in user
    mode when ~/.local/bin does not exist yet (#491).

  • rig system clean-registry on Windows now removes all stale R and
    Rtools registry entries and "Add/Remove Programs" entries.

  • rig list, rig add and other commands no longer fail with
    on macOS in user mode when ~/.local/bin does not exist yet (#491).

  • rig on Linux now uses an updated embedded root certificate bundle
    (webpki-root-certs 1.0.10), which drops the compromised
    "emSign ECC Root CA - G3" root (see GHSA-hq85-5cpj-mr62).

  • rig pkg install and rig proj sync now install git, GitHub and
    url:: package sources on Windows again. rig passed \\?\ paths
    to R CMD INSTALL, which R rejected (#485).

  • rig proj import and rig proj lock now handle Remotes and
    Config/Needs/* entries for packages with a dot in their name, e.g.
    Rdatatable/data.table (#476).

  • rig proj lock now keeps relative 'path' dependencies relative in the
    lock file. The root project is saved with path ".", if it is a package.

  • rig proj import and rig proj export now convert all [build] entries
    to and from the ByteCompile, NeedsCompilation, LazyData, Biarch
    and KeepSource DESCRIPTION fields.

  • rig proj status now reports whether rproj.lock is up to date with
    rproj.toml, e.g. after a manual edit of rproj.toml. It runs the same
    check as rig proj lock --check (#466).

  • New prefer-binary and exclude-newer configuration entries (and
    RIG_PREFER_BINARY and RIG_EXCLUDE_NEWER environment variables) set the
    defaults of --prefer-binary and --exclude-newer for rig pkg install
    and the rig proj commands (#441).

  • The project .Renviron now quotes the saved R_LIBS_USER value, so it
    works with Windows paths. Delete .Renviron and call rig proj lock
    to recreate it with the fixed version in existing projects.

  • rig now sends a User-Agent header with its HTTP requests, e.g.
    rig/0.11.1 (+https://github.com/r-lib/rig).

  • rig now supports authenticated repositories and Posit Package Manager
    instances. See the new "Authentication" guide.

  • New rig pkg sync [LOCKFILE] command installs the packages of a lock file
    into a library, without touching the project environment.

  • A new --cache-dir flag, RIG_CACHE_DIR environment variable, and
    cache-dir configuration entry allow overriding the location of rig's cache.
    --no-cache still takes precedence.

  • Packages are now installed with file modes more closely aligned with those
    left by R CMD INSTALL. Existing packages in the cache are left unchanged.

  • An R session that runs a different R minor version than the one the
    project was synced for now really leaves the project library alone.
    Before, rig printed a warning, but still activated the library (#450).
    Call rig proj sync in existing projects to update the activation code.

  • The dependency solver now treats a dash in a package version the same as
    a dot, like R does, so e.g. version 0.3-3 satisfies >= 0.3.3 (#453).

  • New rig proj lock --check and rig proj sync --locked options, to fail
    if rproj.lock is missing or out of date with rproj.toml, e.g. in CI
    (#411).

  • rig pkg install now calls its --no-install-project option
    --no-install-self. The old name still works, as an alias (#442).
    rig proj sync accepts --no-install-self as an alias of
    --no-install-project.

rig 0.11.0

Choose a tag to compare

@gaborcsardi gaborcsardi released this 07 Oct 20:58

Custom repositories

  • New rig repos add and rig repos rm commands to add and remove your
    own CRAN-like package repositories, e.g. an internal CRAN mirror or an
    r-universe. rig stores them in its configuration file, and they work like
    the built-in repositories, e.g. with --with-repos.
    rig repos add --enable --all-versions enables a repository for all
    R versions, including the ones you install later.

  • New rig repos enable and rig repos disable commands to turn
    repositories, built-in or custom, on and off for each R version.

  • rig now remembers the repositories enabled and disabled for each R
    version, with these commands or with --with-repos / --without-repos,
    and applies them again on rig repos setup. rig repos setup now asks
    for administrator rights if the current user cannot update the files of
    the R installations, e.g. in admin mode on Linux and Windows.

  • rig pkg install, rig pkg deps, rig pkg tree, rig pkg available
    and rig pkg info now use the repositories configured for the R
    version, including custom ones. rig pkg deps, rig pkg tree,
    rig pkg available and rig pkg info have a new --r-version option.
    rig pkg search still searches CRAN only.

  • rig pkg install, rig pkg deps, rig pkg tree, rig pkg available
    and rig pkg info have new --with-repos and --without-repos
    options, with aliases --index and --no-index, to use other
    repositories for one command, without changing the setup of the R
    version. --with-repos also takes repository URLs, or name=URL.

  • rig pkg commands now only use Bioconductor packages if the
    Bioconductor repositories are enabled for the R version, e.g. with
    rig repos enable bioconductor.

  • rig now sets up P3M by default on macOS, and on the Linux
    distributions P3M has no binary packages for, where P3M is a CRAN
    mirror of source packages. P3M stays off on aarch64 Windows, because it
    only has x86_64 Windows binaries. Use
    --without-repos=p3m or rig repos disable p3m to turn it off.

  • --without-repos=cran (and rig repos disable cran) now turns off CRAN
    completely.

  • rig proj now implements [[repository]] entries of rproj.toml and repository
    pinning. rig proj lock, rig proj sync, rig proj deps and rig proj tree
    have new --with-repos and --without-repos options to add and remove
    repositories for one command.

Bioconductor

  • rig proj and rig pkg now install Bioconductor packages, besides CRAN
    packages, from the Bioconductor release that belongs to the R version.
    CRAN and Bioconductor share one package namespace, so a bioc::<package>
    entry in Remotes: or Config/Needs/* is the same as <package>. A
    bioc entry in the
    [[repository]] array of rproj.toml pins the Bioconductor release, or
    turns Bioconductor off. rproj.lock is now version 5, and records the
    Bioconductor release of every target.

  • rig pkg info now shows the full DESCRIPTION of the current version
    of a Bioconductor package, e.g. its title, description and maintainer,
    from the VIEWS file of its Bioconductor repository.

Inline scripts

  • rig run now support self-contained scripts, that declare the packages
    and the R version they need in a # /// script comment block. rig then
    runs the script in its own environment, in the cache directory, and
    installs R and the packages as needed. rig run --upgrade and
    rig run --upgrade-package upgrade the packages of a script's
    environment.

  • New rig proj lock --upgrade-package (-P) option, to upgrade only
    some packages, and keep the versions rproj.lock pins for the rest. It
    also takes a version requirement, e.g. -P 'cli@>= 3.6.4', for this
    run only (#410).

  • rig proj lock now keeps the versions rproj.lock pins when it has to
    solve the dependencies again, e.g. after rig proj add, as long as they
    still fit rproj.toml. Use --upgrade to pick the latest versions.

  • rig proj init, rig proj add and rig proj remove have a new
    --script option, to create and edit the # /// script block of an R
    script, instead of a project's rproj.toml (#414).

  • New rig proj lock --script script.R to lock the dependencies of a
    script with a # /// script block into script.R.lock, next to the
    script. rig run then installs the R and package versions of the lock
    file, and updates it if the block changes. rig run --locked fails
    instead of updating it (#422).

  • New rig system script-assoc command on Windows, to run .R files with
    rig from cmd and PowerShell, e.g. hello.R a b.

System requirements

  • rig pkg install, rig proj sync and rig run now install the system
    requirements of R packages on Linux, like pak does. rig matches each
    package's SystemRequirements field against the
    r-system-requirements
    rules, and installs the missing OS packages if it runs as root or if
    sudo needs no password. Otherwise it prints the commands to run.
    Source packages and distribution-specific binaries need this, manylinux
    binaries do not. --no-sysreqs turns this off for one run; the new
    sysreqs, sysreqs-sudo, sysreqs-update and sysreqs-rules-url
    config entries configure it; sysreqs = "print" only shows the commands.

  • rproj.lock now records the SystemRequirements of each package, so it
    is version 5. Run rig proj lock to update an older lock file.

Other new features

  • rig now honors the OS_type field of packages: a Unix-only package is
    not used on Windows, and a Windows-only package is not used on macOS and
    Linux.

  • rig add now has a --json option. It prints information about the
    installed R version (or the already installed version that was kept),
    including whether it is a new installation and whether it is the default.

  • rig rtools add now has a --json option. It prints information about
    the installed (or already installed) Rtools versions, including whether
    each one is a new installation.

  • New rig pkg search command to search CRAN packages, using the same
    web service as the pkgsearch R package.

  • New rig pkg doctor command to find problems with the packages in a
    library: missing or too old dependencies, and packages compiled against
    another version of a LinkingTo dependency (#393).

  • rig proj commands now support path dependencies.

  • rig proj init and rig proj import do not overwrite the project's
    .Renviron file any more. rig now only manages a marked block in it,
    and keeps the rest of the file, so you can add your own environment
    variables to it. An existing .Renviron is not a conflict any more,
    either (#440).

  • rig pkg install <path> is now supported. <path> can be a directory,
    of a source or binary package file.

  • rig pkg install now supports constraints. E.g. to install a specific
    version of a package use rig pkg install '<pkg>@=<ver>'.

  • rig proj import --force now correctly overwrites the existing project
    files.

  • If the root project is a package, rig proj lock now includes it in the
    solution, with a file:// URL.It also calls rig proj export to
    (re)create its DESCRIPTION file and rig proj sync now installs the
    root project if it is a package.

  • rig pkg install --no-install-project installs only the dependencies of
    the named packages, like rig proj sync --no-install-project.

  • rig proj lock now rewrites the lock file if the list of R versions to
    solve for changes.

  • New --exclude-newer option for rig proj lock, rig proj sync and
    rig pkg install, to ignore CRAN package versions published after a
    date, e.g. --exclude-newer 2025-06-01, or in the last few days, e.g.
    --exclude-newer "7 days". Projects can set it in rproj.toml, with
    exclude-newer in [tool.rig].

  • Projects and scripts can now set prefer-binary in [tool.rig].
    rig proj init and rig proj import have a new --prefer-binary
    option, to write the setting into the manifest.

  • Projects can now set the platforms and R versions rig proj lock solves
    for in rproj.toml, with platforms and r-versions in [tool.rig],
    e.g. r-versions = ["4.5", "4.6"]. --platform and --r-version
    override them.

  • rig proj lock now also solves for source packages by default
    rig proj sync uses this target only if no other target matches the
    machine.

  • rig run <script> now passes every argument after the script on to the
    script, including the ones starting with -, and --. A script that
    starts with #!, e.g. #!/usr/bin/env -S rig run, does not need an
    .R extension any more (#413).

  • rig run --rscript does not pass an extra --args argument to scripts
    and -e expressions any more, so commandArgs(TRUE) only has the
    arguments you gave.

Windows specific changes

  • The rig binaries themselves are now signed on Windows, not only the
    rig installer.

rig 0.11.0 beta 2

rig 0.11.0 beta 2 Pre-release
Pre-release

Choose a tag to compare

@gaborcsardi gaborcsardi released this 06 Oct 10:10

Custom repositories

  • New rig repos add and rig repos rm commands to add and remove your
    own CRAN-like package repositories, e.g. an internal CRAN mirror or an
    r-universe. rig stores them in its configuration file, and they work like
    the built-in repositories, e.g. with --with-repos.
    rig repos add --enable --all-versions enables a repository for all
    R versions, including the ones you install later.

  • New rig repos enable and rig repos disable commands to turn
    repositories, built-in or custom, on and off for each R version.

  • rig now remembers the repositories enabled and disabled for each R
    version, with these commands or with --with-repos / --without-repos,
    and applies them again on rig repos setup. rig repos setup now asks
    for administrator rights if the current user cannot update the files of
    the R installations, e.g. in admin mode on Linux and Windows.

  • rig pkg install, rig pkg deps, rig pkg tree, rig pkg available
    and rig pkg info now use the repositories configured for the R
    version, including custom ones. rig pkg deps, rig pkg tree,
    rig pkg available and rig pkg info have a new --r-version option.
    rig pkg search still searches CRAN only.

  • rig pkg install, rig pkg deps, rig pkg tree, rig pkg available
    and rig pkg info have new --with-repos and --without-repos
    options, with aliases --index and --no-index, to use other
    repositories for one command, without changing the setup of the R
    version. --with-repos also takes repository URLs, or name=URL.

  • rig pkg commands now only use Bioconductor packages if the
    Bioconductor repositories are enabled for the R version, e.g. with
    rig repos enable bioconductor.

  • rig now sets up P3M by default on macOS, and on the Linux
    distributions P3M has no binary packages for, where P3M is a CRAN
    mirror of source packages. P3M stays off on aarch64 Windows, because it
    only has x86_64 Windows binaries. Use
    --without-repos=p3m or rig repos disable p3m to turn it off.

  • --without-repos=cran (and rig repos disable cran) now turns off CRAN
    completely.

  • rig proj now implements [[repository]] entries of rproj.toml and repository
    pinning. rig proj lock, rig proj sync, rig proj deps and rig proj tree
    have new --with-repos and --without-repos options to add and remove
    repositories for one command.

Bioconductor

  • rig proj and rig pkg now install Bioconductor packages, besides CRAN
    packages, from the Bioconductor release that belongs to the R version.
    CRAN and Bioconductor share one package namespace, so a bioc::<package>
    entry in Remotes: or Config/Needs/* is the same as <package>. A
    bioc entry in the [[repository]] array of rproj.toml pins the
    Bioconductor release, or turns Bioconductor off. rproj.lock is now
    version 5, and records the Bioconductor release of every target.

  • rig pkg info now shows the full DESCRIPTION of the current version
    of a Bioconductor package, e.g. its title, description and maintainer,
    from the VIEWS file of its Bioconductor repository.

Inline scripts

  • rig run now support self-contained scripts, that declare the packages
    and the R version they need in a # /// script comment block. rig then
    runs the script in its own environment, in the cache directory, and
    installs R and the packages as needed. rig run --upgrade and
    rig run --upgrade-package upgrade the packages of a script's
    environment.

  • New rig proj lock --upgrade-package (-P) option, to upgrade only
    some packages, and keep the versions rproj.lock pins for the rest. It
    also takes a version requirement, e.g. -P 'cli@>= 3.6.4', for this
    run only (#410).

  • rig proj lock now keeps the versions rproj.lock pins when it has to
    solve the dependencies again, e.g. after rig proj add, as long as they
    still fit rproj.toml. Use --upgrade to pick the latest versions.

  • rig proj init, rig proj add and rig proj remove have a new
    --script option, to create and edit the # /// script block of an R
    script, instead of a project's rproj.toml (#414).

  • New rig proj lock --script script.R to lock the dependencies of a
    script with a # /// script block into script.R.lock, next to the
    script. rig run then installs the R and package versions of the lock
    file, and updates it if the block changes. rig run --locked fails
    instead of updating it (#422).

  • New rig system script-assoc command on Windows, to run .R files with
    rig from cmd and PowerShell, e.g. hello.R a b.

System requirements

  • rig pkg install, rig proj sync and rig run now install the system
    requirements of R packages on Linux, like pak does. rig matches each
    package's SystemRequirements field against the
    r-system-requirements
    rules, and installs the missing OS packages if it runs as root or if
    sudo needs no password. Otherwise it prints the commands to run.
    Source packages and distribution-specific binaries need this, manylinux
    binaries do not. --no-sysreqs turns this off for one run; the new
    sysreqs, sysreqs-sudo, sysreqs-update and sysreqs-rules-url
    config entries configure it; sysreqs = "print" only shows the commands.

  • rproj.lock now records the SystemRequirements of each package, so it
    is version 5. Run rig proj lock to update an older lock file.

Other new features

  • rig now honors the OS_type field of packages: a Unix-only package is
    not used on Windows, and a Windows-only package is not used on macOS and
    Linux.

  • rig add now has a --json option. It prints information about the
    installed R version (or the already installed version that was kept),
    including whether it is a new installation and whether it is the default.

  • rig rtools add now has a --json option. It prints information about
    the installed (or already installed) Rtools versions, including whether
    each one is a new installation.

  • New rig pkg search command to search CRAN packages, using the same
    web service as the pkgsearch R package.

  • New rig pkg doctor command to find problems with the packages in a
    library: missing or too old dependencies, and packages compiled against
    another version of a LinkingTo dependency (#393).

  • rig proj commands now support path dependencies.

  • rig pkg install <path> is now supported. <path> can be a directory,
    of a source or binary package file.

  • rig pkg install now supports constraints. E.g. to install a specific
    version of a package use rig pkg install '<pkg>@=<ver>'.

  • rig proj import --force now correctly overwrites the existing project
    files.

  • If the root project is a package, rig proj lock now includes it in the
    solution, with a file:// URL.It also calls rig proj export to
    (re)create its DESCRIPTION file and rig proj sync now installs the
    root project if it is a package.

  • rig pkg install --no-install-project installs only the dependencies of
    the named packages, like rig proj sync --no-install-project.

  • rig proj lock now rewrites the lock file if the list of R versions to
    solve for changes.

  • New --exclude-newer option for rig proj lock, rig proj sync and
    rig pkg install, to ignore CRAN package versions published after a
    date, e.g. --exclude-newer 2025-06-01, or in the last few days, e.g.
    --exclude-newer "7 days". Projects can set it in rproj.toml, with
    exclude-newer in [tool.rig].

  • Projects and scripts can now set prefer-binary in [tool.rig].
    rig proj init and rig proj import have a new --prefer-binary
    option, to write the setting into the manifest.

  • Projects can now set the platforms and R versions rig proj lock solves
    for in rproj.toml, with platforms and r-versions in [tool.rig],
    e.g. r-versions = ["4.5", "4.6"]. --platform and --r-version
    override them.

  • rig proj lock now also solves for source packages by default
    rig proj sync uses this target only if no other target matches the
    machine.

  • rig run <script> now passes every argument after the script on to the
    script, including the ones starting with -, and --. A script that
    starts with #!, e.g. #!/usr/bin/env -S rig run, does not need an
    .R extension any more (#413).

  • rig run --rscript does not pass an extra --args argument to scripts
    and -e expressions any more, so commandArgs(TRUE) only has the
    arguments you gave.

Windows specific changes

  • The rig binaries themselves are now signed on Windows, not only the
    rig installer.

rig 0.10.0

Choose a tag to compare

@gaborcsardi gaborcsardi released this 21 Sep 13:19

Web site

  • rig has a new documentation website at https://rig.r-lib.org/,
    including a full CLI reference and a guide to admin vs. user mode.

User mode

  • rig now supports a user mode on all platforms, in addition to the
    default admin mode. In user mode rig installs everything into the user's
    home directory and never needs sudo or administrator privileges. R goes
    into ~/.local/share/rig/r (%APPDATA%\rig\data\r on Windows) and quick
    links into ~/.local/bin (%USERPROFILE%\.local\bin on Windows). Select
    the mode with the --user / --admin global flags, the RIG_MODE
    environment variable, or the mode key in the rig config file. The new
    rig system user-mode command switches an existing admin-mode setup to
    user mode.

  • On Linux, rig can now install portable R builds, for glibc- and
    musl-based Linux distros. If there is no distro-specific build for your
    platform, rig falls back to a portable build automatically.

R package management

  • New rig pkg subcommand to query and manage R packages. Two subcommands
    from rig repos moved to rig pkg: rig pkg available and
    rig pkg info. rig pkg deps lists the packages a package needs, in a
    table, and rig pkg tree shows the same dependencies as a tree.
    rig pkg list lists the packages installed in a library,
    rig pkg remove deletes packages from a library, and
    rig pkg install installs packages, and their dependencies, into a
    library.

Projects

  • New and redesigned rig proj commands to manage isolated R projects and
    virtual environments: rig proj init, rig proj import, rig proj add,
    rig proj remove, rig proj lock, rig proj sync, rig proj status.

  • New rig proj tree shows the dependency closure of a project as a tree.

  • rig run now uses the project environment, if you call it in a project
    directory: it starts .rvenv/bin/R, with the project's package library
    and the R version the project's lock file names, and it syncs the project
    first if the environment is missing or out of date. Use --no-project
    (or --r-version) to run the default R version instead.

  • rig run <name> now runs a script the project declares in a [[bin]]
    table of its rproj.toml, passing the remaining arguments on to the
    script. rig run --list lists the declared scripts.

  • rig proj sync can now centralize project package libraries outside the
    project directory: set the RIG_PROJ_LIBRARY_ROOT environment variable or
    the proj-library-root config key to a root directory, and each project
    gets its own library under it, keyed by project name and location. A
    compatibility symlink is left at the project's usual .rvenv/lib.
    rig system dirs --library-root reports the effective root (#372).

Windows specific

  • Windows builds of rig are now signed, thanks to the SignPath Foundation,
    https://signpath.org/.

  • On Windows rig now creates .exe shims instead of bat shims.
    With .exe shims it is easier to pass command line arguments to
    R and Rscript. In particular, Rscript -e <code> now works if
    <code> has line breaks. Call rig system make-links to create all
    .exe shims and remove the .bat shims. If you hardcoded shims with
    a .bat extension, change them to .exe or remove the extension
    completely (#362).

  • New rig system fix-r-alias subcommand.

  • rig rtools is now a top-level command (it used to be rig system rtools).

  • On Windows, R CMD config now works without manually putting Rtools on
    the PATH. So do R CMD sh, R CMD make and rig run --cmd config.

macOS specific

Other new features

  • rig add no longer reinstalls a version that is already installed,
    except for R-devel and R-next. Use --reinstall for force a re-install
    (#293).

  • rig add can now install the R version an renv.lock file requires,
    e.g. rig add renv.lock or rig add path/to/renv.lock (#294).

  • New rig system blas commands, to check and switch which BLAS/LAPACK
    library an installed R version uses on macOS, e.g. to switch to Apple's
    faster Accelerate/vecLib BLAS (#212).

  • New rig self update to update rig, new rig self uninstall to remove
    rig, if it was installed via the install script.

  • New rig cache command to inspect and manage rig's download and build
    caches. rig now reflinks or hardlinks packages from the cache when
    possible, instead of copying them, to save disk space and time.

  • New rig ppm command queries Posit Package Manager. New
    rig ppm build-log shows the build log of a package on Posit Package Manager.

  • New rig repos status checks the configured package repositories.

  • New rig system fix-aliases to update R-release, R-oldrel etc.
    aliases (#234).

  • rig library add, rig library default, rig library list and
    rig library rm have a new --r-version (-r) option, to operate on
    the libraries of an R version other than the default one.

  • New rig system dirs command to show the directories rig uses. With
    --r, --binary, --data, --cache, --download, --log, --rtools
    (Windows only) or --fonts (Linux only) it prints a single path, for use
    in scripts.

  • New rig config command to manage the rig configuration file.

  • rig run --cmd <command> [args...] now runs R CMD <command> [args...]
    with the selected R version.

  • rig run -- <flags> now passes raw arguments straight to the R process,
    e.g. rig run -- --vanilla or rig run -e '1+1' -- --vanilla (#249).

  • Plain rig run (i.e. without -e/-f/an app/--cmd) now defaults to
    --no-save --no-restore, so it no longer shows the "Save workspace
    image?" prompt on exit. Use rig run -- --save --restore to get the old
    behavior back (#249).

Other changes

  • rig add --without-p3m works correctly again (#369).

  • macOS user mode: rig default now sets the default R version correctly
    for newer RStudio versions. Also, rig system allow-debugger-rstudio
    now works for newer RStudio versions.

  • rig now uses a user-dependent download directory, to avoid interference
    between users.

  • rig now does not edit the shell startup files in admin mode,
    like rig 0.8.1 did on macOS. rig now only does this in user mode.

  • rig repos available now prints a compact table. New
    rig repos available <name> shows complete information about a single
    repository.

  • rig system setup-user-lib (and its create-lib alias) now works again.

  • rig rstudio --config-path is now implemented on Linux and macOS.

  • rig now warns instead of failing when it encounters a broken R
    installation (#346).

rig 0.10.0 beta 3

rig 0.10.0 beta 3 Pre-release
Pre-release

Choose a tag to compare

@gaborcsardi gaborcsardi released this 14 Sep 14:03

Web site

  • rig has a new documentation website at https://rig.r-lib.org/,
    including a full CLI reference and a guide to admin vs. user mode.

User mode

  • rig now supports a user mode on all platforms, in addition to the
    default admin mode. In user mode rig installs everything into the user's
    home directory and never needs sudo or administrator privileges. R goes
    into ~/.local/share/rig/r (%APPDATA%\rig\data\r on Windows) and quick
    links into ~/.local/bin (%USERPROFILE%\.local\bin on Windows). Select
    the mode with the --user / --admin global flags, the RIG_MODE
    environment variable, or the mode key in the rig config file. The new
    rig system user-mode command switches an existing admin-mode setup to
    user mode.

  • On Linux, rig can now install portable R builds, for glibc- and
    musl-based Linux distros. If there is no distro-specific build for your
    platform, rig falls back to a portable build automatically.

R package management

  • New rig pkg subcommand to query and manage R packages. Two subcommands
    from rig repos moved to rig pkg: rig pkg available and
    rig pkg info. rig pkg deps lists the packages a package needs, in a
    table, and rig pkg tree shows the same dependencies as a tree.
    rig pkg list lists the packages installed in a library,
    rig pkg remove deletes packages from a library, and
    rig pkg install installs packages, and their dependencies, into a
    library.

Projects

  • New and redesigned rig proj commands to manage isolated R projects and
    virtual environments: rig proj init, rig proj import, rig proj add,
    rig proj remove, rig proj lock, rig proj sync, rig proj status.

  • New rig proj tree shows the dependency closure of a project as a tree.

  • rig run now uses the project environment, if you call it in a project
    directory: it starts .rvenv/bin/R, with the project's package library
    and the R version the project's lock file names, and it syncs the project
    first if the environment is missing or out of date. Use --no-project
    (or --r-version) to run the default R version instead.

  • rig run <name> now runs a script the project declares in a [[bin]]
    table of its rproj.toml, passing the remaining arguments on to the
    script. rig run --list lists the declared scripts.

Windows specific

  • Windows builds of rig are now signed, thanks to the SignPath Foundation,
    https://signpath.org/.

  • On Windows rig now creates .exe shims instead of bat shims.
    With .exe shims it is easier to pass command line arguments to
    R and Rscript. In particular, Rscript -e <code> now works if
    <code> has line breaks. Call rig system make-links to create all
    .exe shims and remove the .bat shims. If you hardcoded shims with
    a .bat extension, change them to .exe or remove the extension
    completely (#362).

  • New rig system fix-r-alias subcommand.

  • rig rtools is now a top-level command (it used to be rig system rtools).

  • On Windows, R CMD config now works without manually putting Rtools on
    the PATH. So do R CMD sh, R CMD make and rig run --cmd config.

Other new features

  • New rig cache command to inspect and manage rig's download and build
    caches. rig now reflinks or hardlinks packages from the cache when
    possible, instead of copying them, to save disk space and time.

  • New rig ppm command queries Posit Package Manager. New rig ppm build-log shows the build log of a package on Posit Package Manager.

  • New rig repos status checks the configured package repositories.

  • rig library add, rig library default, rig library list and
    rig library rm have a new --r-version (-r) option, to operate on
    the libraries of an R version other than the default one.

  • New rig system dirs command to show the directories rig uses. With
    --r, --binary, --data, --cache, --download, --log, --rtools
    (Windows only) or --fonts (Linux only) it prints a single path, for use
    in scripts.

  • New rig config command to manage the rig configuration file.

  • rig run --cmd <command> [args...] now runs R CMD <command> [args...]
    with the selected R version.

Other changes

  • rig add --without-p3m works correctly again (#369).

  • macOS user mode: rig default now sets the default R version correctly
    for newer RStudio versions. Also, rig system allow-debugger-rstudio
    now works for newer RStudio versions.

  • rig now uses a user-dependent download directory, to avoid interference
    between users.

  • rig now does not edit the shell startup files in admin mode,
    like rig 0.8.1 did on macOS. rig now only does this in user mode.

  • rig repos available now prints a compact table. New
    rig repos available <name> shows complete information about a single
    repository.

  • rig system setup-user-lib (and its create-lib alias) now works again.

  • rig rstudio --config-path is now implemented on Linux and macOS.

  • rig now warns instead of failing when it encounters a broken R
    installation (#346).

rig 0.10.0 beta 2

rig 0.10.0 beta 2 Pre-release
Pre-release

Choose a tag to compare

@gaborcsardi gaborcsardi released this 02 Sep 18:11
  • macOS user mode: rig default now sets the default R version correctly
    for newer RStudio versions. Also, rig system allow-debugger-rstudio
    now works for newer RStudio versions.

  • On Windows rig now creates .exe shims instead of bat shims.
    With .exe shims it is easier to pass command line arguments to
    R and Rscript. In particular, Rscript -e <code> now works if
    <code> has line breaks. Call rig system make-links to create all
    .exe shims and remove the .bat shims. If you hardcoded shims with
    a .bat extension, change them to .exe or remove the extension
    completely (#362).

  • New rig ppm command queries Posit Package Manager.

  • New rig repos status checks the configured package repositories.

  • New rig pkg subcommand to query and manage R packages. Two subcommands
    from rig repos moved to rig pkg: rig pkg available and
    rig pkg info. rig pkg deps lists the packages a package needs, in a
    table, and rig pkg tree shows the same dependencies as a tree.
    rig pkg list lists the packages installed in a library,
    rig pkg remove deletes packages from a library, and
    rig pkg install installs packages, and their dependencies, into a
    library.

  • rig proj deps has a new --recursive (-r) option, to show the whole
    dependency closure of the project.

  • New rig proj tree shows the dependency closure of a project as a tree.

  • rig library add, rig library default, rig library list and
    rig library rm have a new --r-version (-r) option, to operate on
    the libraries of an R version other than the default one.

  • rig now uses a user-dependent download directory, to avoid interference
    between users.

  • rig now does not edit the shell startup files in admin mode,
    like rig 0.8.1 did on macOS. rig now only does this in user mode.

  • rig repos available now prints a compact table. New
    rig repos available <name> shows complete information about a single
    repository.

  • rig system setup-user-lib (and its create-lib alias) now works again.

  • rig now supports a user mode on all platforms, in addition to the
    default admin mode. In user mode rig installs everything into the user's
    home directory and never needs sudo or administrator privileges. R goes
    into ~/.local/share/rig/r (%APPDATA%\rig\data\r on Windows) and quick
    links into ~/.local/bin (%USERPROFILE%\.local\bin on Windows). Select
    the mode with the --user / --admin global flags, the RIG_MODE
    environment variable, or the mode key in the rig config file. The new
    rig system user-mode command switches an existing admin-mode setup to
    user mode.

  • rig has a new documentation website at https://rig.r-lib.org/,
    including a full CLI reference and a guide to admin vs. user mode.

  • New rig config command to manage the rig configuration file.

  • New rig system dirs command to show the directories rig uses. With
    --r, --binary, --data, --cache, --download, --log, --rtools
    (Windows only) or --fonts (Linux only) it prints a single path, for use
    in scripts.

  • New experimental rig proj command to manage R project dependencies.

  • rig run --cmd <command> [args...] now runs R CMD <command> [args...]
    with the selected R version.

  • rig rtools is now a top-level command (it used to be rig system rtools).

  • On Windows, R CMD config now works without manually putting Rtools on
    the PATH. So do R CMD sh, R CMD make and rig run --cmd config.

  • On Linux, rig can now install portable R builds, for glibc- and
    musl-based Linux distros. If there is no distro-specific build for your
    platform, rig falls back to a portable build automatically.

  • New rig system fix-r-alias subcommand.

  • rig rstudio --config-path is now implemented on Linux and macOS.

  • rig now warns instead of failing when it encounters a broken R
    installation (#346).

rig fallback fonts 1

Choose a tag to compare

@gaborcsardi gaborcsardi released this 11 Aug 16:54

DejaVu 2.37 subset (Sans, Serif, Sans Mono; regular/bold/italic/bold-italic) that rig installs next to the portable Linux R builds, which bundle libfontconfig but no fonts.

Built by tools/make-fonts-asset.sh. Not tied to a rig release: it only changes when the font set changes, and then it gets a new number and a new tag.

rig 0.10.0 beta

rig 0.10.0 beta Pre-release
Pre-release

Choose a tag to compare

@gaborcsardi gaborcsardi released this 10 Aug 11:30
v0.10.0-beta

Bump version to 0.10-0-beta

rig 0.10.0 alpha 2

rig 0.10.0 alpha 2 Pre-release
Pre-release

Choose a tag to compare

@gaborcsardi gaborcsardi released this 01 Aug 10:57
v0.10.0-alpha2

rig 0.10.0-alpha2