Backward Compatibility

Backward Compatibility

There is no formal backward-compatibility contract for old logme versions at the moment.

This page should be explicit about that instead of pretending that such a layer exists. The project is still actively changing, and recent work has touched configuration parsing, backend behavior, console handling, structured output, runtime control, and formatting internals.

What this means

Some old code may continue to compile or run because the specific API it uses has not changed. That is best-effort continuity, not a documented compatibility guarantee.

When upgrading logme, treat the update as a normal migration: rebuild the project, review configuration files, run the logging tests that matter for your application, and verify produced output. This is especially important if the application depends on exact file names, rotation behavior, structured output, console coloring, dynamic control commands, or backend shutdown behavior.

Future policy

If a future release defines a real compatibility policy, this page should document it. Until then, the honest statement is simple: compatibility with old versions is not guaranteed.