chore: See what CodeQL does

[geeknoid]

No description provided.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.0%. Comparing base (1f453b8) to head (0755ca8).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #223   +/-   ##
=======================================
  Coverage   100.0%   100.0%           
=======================================
  Files         105      105           
  Lines        6761     6761           
=======================================
  Hits         6761     6761           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[github-actions]

⚠️ Breaking Changes Detected

error: unsupported rustdoc format v57 for file: /home/runner/work/oxidizer/oxidizer/target/semver-checks/local-bytesbuf-0_2_2-default-fee6ca6725f06642/target/doc/bytesbuf.json
(supported formats are v53, v55, v56)

Stack backtrace:
   0: anyhow::error::<impl core::convert::From<E> for anyhow::Error>::from
   1: cargo_semver_checks::data_generation::request::load_rustdoc_with_optional_metadata
   2: cargo_semver_checks::data_generation::request::CrateDataRequest::resolve
   3: cargo_semver_checks::rustdoc_gen::StatefulRustdocGenerator<cargo_semver_checks::rustdoc_gen::ReadyState>::load_rustdoc
   4: cargo_semver_checks::Check::check_release::{{closure}}
   5: cargo_semver_checks::Check::check_release
   6: cargo_semver_checks::exit_on_error
   7: cargo_semver_checks::main
   8: std::sys::backtrace::__rust_begin_short_backtrace
   9: main

If the breaking changes are intentional then everything is fine - this message is merely informative.

Remember to apply a version number bump with the correct severity when publishing a version with breaking changes (1.x.x -> 2.x.x or 0.1.x -> 0.2.x).