v0.5.4

• Fix an issues where if we can't find --affected files in the graph
  we didn't look up the absolute or relative paths either.

v0.5.3

• Print more output when failing to find affected paths in the Ninja
  build file.

v0.5.2

• Fix default statements not being printed out correctly when all
  their inputs are not marked as affected.

v0.5.1

• Fix issues when empty lines are passed in --affected and we try to
  convert them to an absolute path on Linux.

v0.5.0

• Check the absolute path of affected files from the current working
  directory instead of the path of the ninja build file. In most
  situations we are building these affected files from the root of the
  project rather than whatever subfolder the ninja build file resides.

v0.4.0

• Fix $in variable containing order-only dependencies
• Do not include outputs if only their order-only dependencies have
  been affected

v0.3.0

• Create a MacOS release
• Build on Ubuntu 20.04 instead of 24.04 to work with older version of
  glibc

v0.2.0

• Add --builddir flag for finding the output ninja directory
• Fix parsing of pool if multiple variables are supplied

v0.1.1

• Fix include and subninja paths not working if trimja is not run
  from the same directory as the ninja build file

v0.1.0

This is the first public release of trimja!

trimja is able to handle ninja build files and to cut them down to only
a small subset of build commands that are affected by a supplied list of
files.

There are a few areas in which trimja can be improved.

• subninja support
• warning on using depfile without deps = gcc
• additional error checking to cover cases such as recursive variable
  references and malformed .ninja_log and .ninja_deps