Repository navigation
chore(release): php-fast-forward/code-standards v0.9.2 → v0.10.0 - #98
github-actions[bot] wants to merge 2 commits into
Conversation
Changelog-Plan: f24f60d9d0398dfb01ec1f2c1ea3d0a9c2bd2ca13dbff94fa97f5e42b9fa20f2 Changelog-Base: 93e27aa Changelog-Output: 5064fb0bf46ab5ed3b8ebe6303173ef241fd84c43fcf7e451d2f41af08e74b2b Changelog-Options: 2e75539a540196ef265b24046749a39457478e53258444a9c5119e62724e5903
|
Important Review skippedBot user detected. To trigger a single review, invoke the
|
Changelog❌ Contribution check failed. Head: Base: Contribution: 0 new valid fragment(s). Policy: ordinary. Diagnostics
Add or correct a unique |
Prepare release 0.10.0.
Plan:
f24f60d9d0398dfb01ec1f2c1ea3d0a9c2bd2ca13dbff94fa97f5e42b9fa20f2Base:
93e27aa2344d39c5612441e135acd51655b678d9Consumed fragments: 1
Updates the changelog and removes the consumed fragments.
Preparing this PR does not publish a tag or release.
After the approved merge, the full lifecycle publishes its tag and GitHub release by default.
An explicit
publish: falsecreates neither; later plans still continue from the consolidated history.Older consolidations without publication are not published retroactively.