chore(main): release 5.21.0

[github-actions]

Lich v5.21.0 (2026-08-21)

---

This PR was generated with Release Please. See documentation.

[ellipsis-dev]

Important

Looks good to me! 👍

Reviewed everything up to 95ff7fb in 6 minutes and 13 seconds. Click for details.

• Reviewed 234 lines of code in 4 files
• Skipped 0 files when reviewing.
• Skipped posting 2 draft comments. View those below.
• Modify your settings and rules to customize what types of comments Ellipsis leaves. And don't forget to react with 👍 or 👎 to teach Ellipsis.

1. lib/version.rb:3

• Draft comment:
  Version bump to '5.13.0' is correctly reflected in LICH_VERSION. Ensure consistency with other release files.
• Reason this comment was not posted:
  Comment looked like it was already resolved.

2. CHANGELOG.md:16

• Draft comment:
  Typo: "Societes" should be spelled "Societies".
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 20% vs. threshold = 50% This is a comment about a typo in a CHANGELOG file. The rules state I should not comment on things that are "obvious or unimportant." A typo in a CHANGELOG is relatively minor - it's documentation, not code. The CHANGELOG appears to be auto-generated based on commit messages (given the format with PR numbers and commit hashes). If it's auto-generated from commit messages, fixing it here might not be the right place, or it might get overwritten. Additionally, while the typo is real, it's in documentation that describes past changes, not in actual code that would affect functionality. This seems like a minor/unimportant issue that doesn't require a code change to fix. However, spelling errors in documentation do matter for professionalism and clarity. If this CHANGELOG is manually maintained or if the suggestion would actually fix it, this could be a valid comment. The comment is clear, actionable, and provides the exact fix needed. While spelling does matter, the rules explicitly say not to make comments that are "obvious or unimportant." A single typo in a CHANGELOG entry is relatively unimportant compared to actual code issues. Additionally, CHANGELOGs are often auto-generated, so this might not even be the right place to fix it. The rule about not commenting on obvious/unimportant things should apply here. This comment should be deleted. It's pointing out a minor typo in documentation (CHANGELOG) which falls under "obvious or unimportant" issues that the rules say not to comment on. While the typo is real, it doesn't affect functionality and is a very minor documentation issue.

Workflow ID: wflow_MNaIAfNCrF2J7uC0

^{You can customize by changing your verbosity settings, reacting with 👍 or 👎, replying to comments, or adding code review rules.}