Bump version to 0.5.0

[dduugg]

Bumps codeowners-rs to 0.5.0, releasing the two changes merged since v0.4.0.

Why 0.5.0, not 0.4.1

Both changes are visible to consumers:

• fix: write CODEOWNERS annotations after glob-based sections #130 — CODEOWNERS annotations are written last. GitHub applies the last matching line, so this makes review routing agree with for-file. It also means every consumer's generated CODEOWNERS changes on upgrade: validate reports the file out of date until it's regenerated. Plain bin/codeownership validate autocorrects and stages it, but CI that runs validate --skip-autocorrect will fail until someone regenerates and commits.
• perf: cache loaded teams in find_file_owners #129 — loaded teams are cached for the life of the process. Per-file lookups get much faster (~20 ms → ~0.4 ms), but a team file added or edited mid-process isn't seen until clear_team_cache() runs or the process restarts. That matters for long-lived processes such as a Rails dev server or console.

Releasing

Merging publishes. The release job fires when the newest commit on main changes the version, and squash-only merging makes this PR that commit; I checked the detection against it with BSD grep: new_version=v0.5.0. #133 (test-only) can merge before or after this without affecting the release.

After merge

• Edit the generated release notes to call out the CODEOWNERS regeneration (fix: write CODEOWNERS annotations after glob-based sections #130) and the process-lifetime team cache (perf: cache loaded teams in find_file_owners #129); the generated notes only list PR titles.
• code_ownership still pins v0.3.3, so Ruby users get none of 0.4.0 or 0.5.0 until it bumps. That bump must also bind clear_team_cache and call it from CodeOwnership.bust_caches!; otherwise bust_caches! no longer fully resets ownership once perf: cache loaded teams in find_file_owners #129 ships.

Sent with Claude Code