R CMD check now succeeds without internet access
or GitHub API availability.osrm_install() now validates the manual install
arguments file_path and download_url first. A
missing, unreadable or malformed value fails immediately, before any
version resolution, destination directory creation or GitHub
request.file_path or
download_url no longer contact GitHub to resolve or verify
a version, and no longer apply the macOS compatibility check, since
neither applies to a user supplied archive.X-RateLimit-Remaining: 0,
now fails at once and reports when the limit resets and how to set
GITHUB_PAT, instead of retrying four times. API errors
again say which request failed.osrm_install() rejects file_path and
download_url supplied together instead of silently
preferring file_path.dest_dir is
NULL, such an archive is now installed into a subdirectory
named manual rather than one named after a version looked
up online, and supplementary v6 runtime libraries are not installed
automatically. Passing an explicit version tag alongside
the archive restores both behaviours without any network lookup.DESCRIPTION.osrm_binaries_provider argument to
osrm_install() (default: “default”). This automatically
fetches static, highly-compatible binaries built directly by this
package’s maintainer (e-kotov/osrm-binaries). These
binaries provide native arm64 and x86_64 builds where available across
Linux, macOS (Apple Silicon and Intel) and Windows, and bundle required
runtime libraries (e.g., Intel TBB) to avoid legacy runtime hacks and
reduce overhead by dropping unnecessary NodeJS wrappers. The original
upstream binaries remain fully supported via
osrm_binaries_provider = "official".download_url and file_path
parameters to osrm_install() to support advanced/manual
installations from a supplied archive URL or a local tarball path. These
parameters are intended for advanced users who need explicit control
over the installation source.checksums.txt as a fallback, ensuring
installation security without requiring R package updates when new
binary builds are released.v26.7.3 as validated by
osrm.backend.tests/testthat/test-compatibility.R) to automatically
verify that custom binaries produce identical routing results and are
fully cross-compatible with official releases.osrm_gui(), an interactive Shiny web application
for exploring and visualizing the loaded OSRM routing network. It comes
with auto-centering logic to reliably detect the source OSM PBF file or
retrieve the extent from the server registry or server object for auto
extent.Improved osrm_servers() with a custom S3 print
method for better interactive readability and a new output
argument to return raw metadata as a list.
Simplified server IDs in the registry to
osrm-{port}-{pid} format for better readability and
programmatic access.
OSRM servers and running OSRM servers registry maintained by the
package pre-save the extent info for osrm_gui() to use it
for auto-centering.
Added a helpful hint to osrm_start() error messages
when a graph is detected to be incompatible with the currently installed
OSRM version.
Validated and added official support for OSRM
v26.4.0 and v26.4.1 releases, ensuring the
necessary runtime libraries (TBB and BZip2) are correctly fetched and
patched across all supported platforms (macOS, Windows, and
Linux).
Weekly live tests to check for potential regressions, successful OSRM binaries installation and possible issues when new versions of OSRM backend binaries.
The osrm.server.log_file option no longer accepts a
list for separate stdout/stderr files. This feature has been removed due
to potential deadlock issues. Use a single character path instead:
options(osrm.server.log_file = "path/to/logfile.log"). If a
list is provided, it will silently fall back to the default temporary
file behavior.
Default logging behavior changed:
osrm_start_server() now writes logs to a temporary file by
default instead of using pipes. This prevents deadlocks in R’s
single-threaded environment while preserving logs for debugging. Use
verbose = TRUE to see output in the console.