v1.0.0

What's Changed

• Use trimja-action by @elliotgoodrich in #87
• Rewrite EvalString by @elliotgoodrich in #94
• Swap to boost::unordered_flat_map by @elliotgoodrich in #95
• Remove fixed_string temporaries by @elliotgoodrich in #96
• Replace std::set with std::vector in graph by @elliotgoodrich in #97
• Simplify EdgeScope by @elliotgoodrich in #98
• Support variables in subninja statements by @elliotgoodrich in #99
• Add allocation profiling on Windows by @elliotgoodrich in #100
• Remove roundtrip to std::filesystem::path by @elliotgoodrich in #101
• Use gch::small_vector in the graph by @elliotgoodrich in #102
• Reused objects to avoid allocations by @elliotgoodrich in #103
• Move to MacOS 13 on Action Runner by @elliotgoodrich in #106
• Support subninja fully by @elliotgoodrich in #105
• Add link time optimization by @elliotgoodrich in #107
• Add --memory argument on Windows by @elliotgoodrich in #108
• Print allocations on --builddir by @elliotgoodrich in #109
• Tidy up casting code by @elliotgoodrich in #110
• Add --cpu-stats flag by @elliotgoodrich in #111
• Improve EvalString by @elliotgoodrich in #113
• Release v1.0.0 by @elliotgoodrich in #114
• Fix build directory when building releases by @elliotgoodrich in #115

Full Changelog: v0.5.4...v1.0.0

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