Bumps the Version: header and USC_VERSION from 1.0.0-rc.3 to 1.0.0, and fixes the stale README version line (was still 1.0.0-rc.1).
After merging, tag the merge commit v1.0.0 (Gitea New Release UI or git tag v1.0.0 && git push origin v1.0.0). The release workflow verifies the tag against the header, runs the suite, builds the distributable zip, and attaches it to the release — sites on rc.3 then see the update on their next check.
composer test — 410 tests pass; composer lint (PHPStan level 10) and composer cs clean.
Bumps the `Version:` header and `USC_VERSION` from `1.0.0-rc.3` to `1.0.0`, and fixes the stale README version line (was still `1.0.0-rc.1`).
After merging, tag the merge commit `v1.0.0` (Gitea New Release UI or `git tag v1.0.0 && git push origin v1.0.0`). The release workflow verifies the tag against the header, runs the suite, builds the distributable zip, and attaches it to the release — sites on rc.3 then see the update on their next check.
- `composer test` — 410 tests pass; `composer lint` (PHPStan level 10) and `composer cs` clean.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Version header, USC_VERSION, and the README version line move from
1.0.0-rc.3 (README was stale at rc.1) to 1.0.0. Tag v1.0.0 on the merge
commit to publish the release.
Co-Authored-By: Claude Fable 5 <[email protected]>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Bumps the
Version:header andUSC_VERSIONfrom1.0.0-rc.3to1.0.0, and fixes the stale README version line (was still1.0.0-rc.1).After merging, tag the merge commit
v1.0.0(Gitea New Release UI orgit tag v1.0.0 && git push origin v1.0.0). The release workflow verifies the tag against the header, runs the suite, builds the distributable zip, and attaches it to the release — sites on rc.3 then see the update on their next check.composer test— 410 tests pass;composer lint(PHPStan level 10) andcomposer csclean.🤖 Generated with Claude Code