Packaging 6.16.1

[jslee02]

Describe this pull request. Link to relevant GitHub issues, if any.

Packaging 6.16.1

• bump downstream requirements from 6.16.0 → 6.16.1 (pixi metadata plus all sample/tutorial find_package calls)
• add a 6.16.1 changelog stub capturing the FreeListAllocator assert fix (Fix FreeListAllocator assert build without NDEBUG #2295) and milestone link

---

Before creating a pull request

• Format code using pixi run lint and verify with pixi run check-lint
• Document new methods and classes
• Build with -DDART_TREAT_WARNINGS_AS_ERRORS=ON and resolve warnings

Before merging

• Set milestone
• Update CHANGELOG.md
• Add unit tests
• Add Python bindings (dartpy) if applicable

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 58.68%. Comparing base (84af7f8) to head (35b62e7).
⚠️ Report is 1 commits behind head on release-6.16.

Additional details and impacted files

@@               Coverage Diff                @@
##           release-6.16    #2296      +/-   ##
================================================
+ Coverage         58.67%   58.68%   +0.01%     
================================================
  Files               384      384              
  Lines             32056    32056              
  Branches           3869     3871       +2     
================================================
+ Hits              18808    18812       +4     
+ Misses            13248    13244       -4     

Flag	Coverage Δ
unittests	58.68% <ø> (+0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.
see 2 files with indirect coverage changes

🚀 New features to boost your workflow:

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

[jslee02]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. Swish!

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".