Devotd Github
NewAI agents

ratel-ai/ratel — Raising the macOS CI runner from macos-14 to macos-15

The latest commit in ratel-ai/ratel raises the macOS runner in GitHub Actions from macos-14 to macos-15, touching only the CI and release workflows plus RELEASING.md, with no code changes.

Repositoryratel-ai/ratel ↗

The latest commit in ratel-ai/ratel raises the macOS runner in GitHub Actions from macos-14 to macos-15, touching only the CI and release workflows plus RELEASING.md, with no code changes.

GitHub description: Context engineering for AI agents. ~80% fewer tokens. Fix tool overload. Skills and memory with in-process BM25 and semantic retrieval. Progressive Disclosure. No vector DB.

stars
★ 478
Forks
28
Language
Rust
License
MIT
Latest release
vercel-ai-sdk-v0.5.0
Read original source ↗View on GitHub ↗

ratel-ai/ratel is a context engineering project for AI agents. The repository description says it reduces token usage by roughly 80% and addresses the problem of excessive tool use, and that it manages skills and memory with BM25 and semantic search inside the process, without an external vector DB. The November 2, 2026 commit 8d78e70 (#199) contains nothing but the change that raises this project's macOS build and test runner from macos-14 to macos-15.

What changed is 5 GitHub Actions workflows plus RELEASING.md — 6 files, with 21 lines added and 21 lines deleted. build-binaries.yml, python-binaries.yml, and release.yml produce npm binaries and Python wheels, verify-install.yml checks the behavior after installation, and ci.yml raised the darwin entry of the entire matrix along with them. Because macos-15 runners are Apple Silicon environments, both SDKs are provided together, so cross-compiling to x86_64-apple-darwin with Rust's --target continues to work as before. x64 installation verification is structured to run on top of Rosetta, and RELEASING.md states that the Intel runner (macos-13) is very slow, so it should not be rolled back.

That said, this commit does not touch any runtime code. It includes neither an SDK or search implementation nor a benchmark substantiating the roughly 80% reduction presented in the repository description. Whether the existing cross-compilation still holds on the new runner depends on the results of the release workflow. It is closer to a choice about migrating the build environment than a feature change.