Reference

Release notes

Distinguish CLI v2.0.0 behavior from unreleased compatibility fixes.

Upcoming release

The following changes exist in the local CLI source but have not been released to npm in this update. Do not assume npm install -g @ricko-v/l includes them. The next version number has not been assigned yet.
ChangeGuide
l init uses an exclusive copy when hard links are rejected in Termux or other filesystemsTermux troubleshooting
Profiles reject Windows device names such as con, nul, and com1 on every OSMultiple profiles
Windows preserves executable modes from the baseline/remote package during pull and pushExecutable permissions
Login keeps waiting for the callback when the browser cannot be opened automaticallyManual login URL

Testing status

The CLI changes passed 92 local tests on macOS, type-checking, and build. Tests include simulated Windows behavior and hard link fallback; they are not native Windows, Linux, or Android tests.

A CI workflow is prepared for Ubuntu, Windows, and macOS with Node.js 22/24, covering installation, tests, build, CLI help, and npm package checks. Windows/Linux runner results have not been confirmed in this update. These tests do not perform real AWS login or deployment.

On Windows, file symlink tests require permission to create symlinks. Contributor details are in docs/Development.md in the CLI source.

v2.0.0

The website's baseline guides cover CLI v2.0.0: browser login, l init, per-project profiles, Lambda list/info, and pull/push for one or many functions with change previews.

Sections labeled upcoming release describe changes after that version. Once the next release is actually available, update these notes and the labels on related pages together.