The changelog for an empty version will now be: ``` No user facing changes. ``` And this will appear in the final changelog when there is an actual release. The benefits are that users will see regular release cycles and know how old versions are even if there's no changes for a particular version If we find that we are going months without any user facing changes, but we have non-visible changes, then we can rethink this strategy. But I think this is nicer than having empty sections for a version.
1.4 KiB
1.4 KiB
CodeQL Action and CodeQL Runner Changelog
[UNRELEASED]
No user facing changes.
1.0.2 - 17 Jun 2021
- Fix out of memory in hash computation. #550
- Clean up logging during analyze results. #557
- Add
--finalize-datasettodatabase finalizecall, freeing up some disk space after database creation. #558
1.0.1 - 07 Jun 2021
- Pass the
--sarif-group-rules-by-packargument to CodeQL CLI invocations that generate SARIF. This means the SARIF rule object for each query will now be found underneath its corresponding query pack inruns[].tool.extensions. #546 - Output the location of CodeQL databases created in the analyze step. #543