docs: promote both composer package changelogs to 1.0.0 - #48
Merged
Conversation
Dates the existing Unreleased sections ahead of tagging v1.0.0, so the tag contains its own release notes rather than an open Unreleased heading. Both packages already ship a README (103 and 63 lines) and a populated changelog, so the split will carry real documentation to rtcamp/wp-phpcs and rtcamp/wp-phpstan — nothing else is needed for them to stand alone. Note the tag should be created directly (git tag -a v1.0.0), not via `monorepo-builder release`. Its PushNextDevReleaseWorker pushes a dev-bump commit to the current branch, and main requires a pull request, so that push is rejected — after the tag has already been pushed, leaving a half-finished release. The workers it would run first are no-ops here anyway: neither package requires the other, so the mutual-dependency and replace workers have nothing to update, and AddTagToChangelogReleaseWorker has no root CHANGELOG.md to write to.
pratik-londhe4
approved these changes
Jul 29, 2026
There was a problem hiding this comment.
Pull request overview
Note
Copilot couldn't run its full agentic review because it didn't start before the timeout. Make sure your repository has a runner available, or add a copilot-code-review.yml file specifying one with the runs-on attribute. See the docs for more details.
This PR updates the per-package changelogs to turn the current “Unreleased” section into a dated 1.0.0 release entry ahead of tagging v1.0.0.
Changes:
- Replace
## Unreleasedwith## [1.0.0] - 2026-07-30in both Composer package changelogs
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| composer-packages/phpstan/CHANGELOG.md | Renames the current release section to 1.0.0 with a specific release date. |
| composer-packages/phpcs/CHANGELOG.md | Renames the current release section to 1.0.0 with a specific release date. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
+7
to
9
| ## [1.0.0] - 2026-07-30 | ||
|
|
||
| ### Added |
Comment on lines
+7
to
9
| ## [1.0.0] - 2026-07-30 | ||
|
|
||
| ### Added |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Dates the existing
## Unreleasedsections in both Composer packages as## [1.0.0] - 2026-07-30, ahead of taggingv1.0.0. Documentation only.This has to land before the tag, so
v1.0.0contains its own release notes rather than an openUnreleasedheading — the mirrors are cut from the tagged tree.Your other two asks are already covered
Both packages already ship real documentation, which the split carries to the mirrors automatically:
composer-packages/phpcscomposer-packages/phpstanSo
rtcamp/wp-phpcsandrtcamp/wp-phpstanwill stand alone as documented packages with no further work.Important: tag directly, not with
monorepo-builder releasegit tag -a v1.0.0 -m "v1.0.0" git push origin v1.0.0vendor/bin/monorepo-builder release v1.0.0will fail partway. ItsPushNextDevReleaseWorkerpushes a dev-bump commit to the current branch, butmainhas a ruleset requiring a pull request, so that push is rejected — and it happens afterPushTagReleaseWorker, so you'd get the tag and the split, then an error and a dirty local state.Nothing is lost by skipping it. The workers that would run first are all no-ops here:
SetCurrentMutualDependencies/SetNextMutualDependencies/UpdateReplace— neither package requires the other (rtcamp siblings required: nonefor both), so there are no mutual dependencies to pin or bump.AddTagToChangelogReleaseWorker— there is no rootCHANGELOG.md; the per-package ones are updated here instead.Worth revisiting the worker list separately if the packages ever depend on each other, or if a root changelog is added.
Sequencing
force_push, because theirInitial commits are not ancestors of any subtree splitv1.0.0→release-php.ymlsplits and pushes both mirrors, fast-forward from then on