fix(docs): Update Rector command in composer.json to remove unnecessary 'src' argument.

[terabytesoftw]

Pull Request

Q	A
Is bugfix?	✔️
New feature?	❌
Breaks BC?	❌

[coderabbitai]

📝 Walkthrough

Summary by CodeRabbit

• Documentation

  • Updated changelog entries with new version identifiers and refreshed issue references.

• Chores

  • Adjusted build script command configuration to remove an explicit path argument.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

Walkthrough

CHANGELOG.md entries were updated (issue identifiers and version notes adjusted). composer.json's "rector" script was changed to remove the explicit src argument from the rector process command.

Changes

Cohort / File(s)	Summary
Documentation CHANGELOG.md	Updated version entries: 0.3.2 now references Enh #22 and Bug #23; 0.3.1 references Bug #19–#21; 0.3.0 references Enh #18.
Configuration composer.json	scripts.rector changed from ./vendor/bin/rector process src to ./vendor/bin/rector process (removed explicit src path).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Poem

🐰 Changelog hops, numbers neatly spun,
Rector trims its path — a line undone,
Versions hum and entries realign,
A tidy hop, a small design. 🥕

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly describes the main change: updating the Rector command in composer.json to remove the unnecessary 'src' argument, which matches the changeset.
Description check	✅ Passed	The description confirms the pull request is a bugfix that doesn't break backward compatibility, which aligns with the changelog and composer.json changes.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

📜 Recent review details

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between f646466 and 7934ffb.

📒 Files selected for processing (1)

• CHANGELOG.md

🧰 Additional context used

🧠 Learnings (1)

📓 Common learnings

Learnt from: terabytesoftw
Repo: php-forge/actions PR: 67
File: .github/workflows/phpstan.yml:13-16
Timestamp: 2025-09-29T14:58:04.095Z
Learning: In the php-forge/actions repository, the maintainer prefers using "composer update" as the default command in CI workflows to ensure the latest dependencies are always installed, rather than using "composer install" for reproducibility.

Learnt from: terabytesoftw
Repo: php-forge/foxy PR: 115
File: tests/Fallback/AssetFallbackTest.php:158-189
Timestamp: 2026-01-23T11:22:07.261Z
Learning: User terabytesoftw prefers not to use aliases when importing classes in PHP. They are comfortable with either fully-qualified class names or direct imports without aliases.

Learnt from: terabytesoftw
Repo: php-forge/support PR: 12
File: src/TestSupport.php:0-0
Timestamp: 2025-08-18T20:13:33.518Z
Learning: User terabytesoftw prefers clean trait-based designs over maintaining backward compatibility wrappers when refactoring utility classes in the php-forge/support project.

Learnt from: terabytesoftw
Repo: php-forge/actions PR: 65
File: .github/workflows/composer-require-checker.yml:80-83
Timestamp: 2025-09-28T15:12:48.345Z
Learning: The user terabytesoftw prefers using floating tags like v1 for third-party actions in GitHub workflows instead of pinning to specific commit SHAs, even when it's a security best practice to pin to immutable commits.

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)

• GitHub Check: phpunit / PHP 8.1-ubuntu-latest
• GitHub Check: linter / Super Linter
• GitHub Check: mutation / PHP 8.5-ubuntu-latest
• GitHub Check: linter / Super Linter

🔇 Additional comments (1)

CHANGELOG.md (1)

5-6: Changelog updates look consistent.

Entries are clear, formatted correctly, and align with the stated changes.

Also applies to: 10-12, 16-16

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Fix all issues with AI agents

In `@CHANGELOG.md`:
- Line 6: The changelog entry "Bug `#23`:Update Rector command in `composer.json`
to remove unnecessary 'src' argument (`@terabytesoftw`)" is missing a space after
the colon; update the line so it reads "Bug `#23`: Update Rector command..."
(i.e., insert a space after the colon in the string "Bug `#23`:Update Rector
command in `composer.json`...") to fix the formatting typo.

📜 Review details

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9805af1 and f646466.

📒 Files selected for processing (2)

• CHANGELOG.md
• composer.json

🧰 Additional context used

🧠 Learnings (2)

📓 Common learnings

Learnt from: terabytesoftw
Repo: php-forge/foxy PR: 115
File: tests/Fallback/AssetFallbackTest.php:158-189
Timestamp: 2026-01-23T11:22:07.261Z
Learning: User terabytesoftw prefers not to use aliases when importing classes in PHP. They are comfortable with either fully-qualified class names or direct imports without aliases.

Learnt from: terabytesoftw
Repo: php-forge/support PR: 12
File: src/TestSupport.php:0-0
Timestamp: 2025-08-18T20:13:33.518Z
Learning: User terabytesoftw prefers clean trait-based designs over maintaining backward compatibility wrappers when refactoring utility classes in the php-forge/support project.

Learnt from: terabytesoftw
Repo: php-forge/actions PR: 65
File: .github/workflows/composer-require-checker.yml:80-83
Timestamp: 2025-09-28T15:12:48.345Z
Learning: The user terabytesoftw prefers using floating tags like v1 for third-party actions in GitHub workflows instead of pinning to specific commit SHAs, even when it's a security best practice to pin to immutable commits.

📚 Learning: 2025-09-29T14:58:04.095Z

Learnt from: terabytesoftw
Repo: php-forge/actions PR: 67
File: .github/workflows/phpstan.yml:13-16
Timestamp: 2025-09-29T14:58:04.095Z
Learning: In the php-forge/actions repository, the maintainer prefers using "composer update" as the default command in CI workflows to ensure the latest dependencies are always installed, rather than using "composer install" for reproducibility.

Applied to files:

• composer.json

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (13)

• GitHub Check: easy-coding-standard / PHP 8.5-ubuntu-latest
• GitHub Check: phpunit / PHP 8.4-ubuntu-latest
• GitHub Check: linter / Super Linter
• GitHub Check: phpunit / PHP 8.3-windows-2022
• GitHub Check: phpunit / PHP 8.2-windows-2022
• GitHub Check: phpunit / PHP 8.4-windows-2022
• GitHub Check: phpunit / PHP 8.1-ubuntu-latest
• GitHub Check: phpunit / PHP 8.5-windows-2022
• GitHub Check: phpunit / PHP 8.5-ubuntu-latest
• GitHub Check: phpunit / PHP 8.2-ubuntu-latest
• GitHub Check: phpunit / PHP 8.3-ubuntu-latest
• GitHub Check: composer-require-checker / PHP 8.5-ubuntu-latest
• GitHub Check: linter / Super Linter

🔇 Additional comments (1)

composer.json (1)

52-52: No action required. The rector.php configuration file properly defines target paths (src and tests), confirming that the removal of the explicit path from the CLI command in composer.json is appropriate. Rector will correctly process only the intended directories based on the configured paths.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}