fix: Correct bug number for badge movement in CHANGELOG.md.

[terabytesoftw]

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

Summary by CodeRabbit

• Documentation
  • Updated the changelog to correct a bug reference from fix: Update installation instructions and add version badge in README.md. #140 to fix: Move badges for latest stable version and total downloads in README.md to Installation section. #141, keeping all other entries unchanged.
  • Clarified that this update introduces no functional or behavioral changes to the product.
  • No action required for end-users; the release content and usage remain the same.
  • This is a documentation-only maintenance adjustment to ensure accuracy and consistency in release notes.

[coderabbitai]

Walkthrough

Updated CHANGELOG.md to reference Bug #141 instead of Bug #140. No code, API, or behavioral changes.

Changes

Cohort / File(s)	Summary
Changelog update CHANGELOG.md	Corrected bug reference number from 140 to 141; no other content changes.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• fix: Move badges for latest stable version and total downloads in README.md to Installation section. #141 — Appears to be the bug referenced; aligns with updating the CHANGELOG to point to Bug fix: Move badges for latest stable version and total downloads in README.md to Installation section. #141 about moving README badges.

Suggested labels

bug

Poem

I twitch my nose at numbers neat,
From 140 to 141—complete!
No code to hop, no tests to run,
Just tidy trails beneath the sun.
Thump, thump—changelog’s right on track,
A carrot-check, then bounce right back! 🥕🐇

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch fix-mini-56

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore or @coderabbit ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

CHANGELOG.md (1)

5-5: Optional: linkify the bug reference for quick navigation.
Consider turning “Bug #141” into a GitHub link (e.g., [#141]) for consistency and usability.

- - Bug #141: Move badges for latest stable version and total downloads in `README.md` to `Installation` section (@terabytesoftw)
+ - Bug [#141]: Move badges for latest stable version and total downloads in `README.md` to `Installation` section (@terabytesoftw)

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

💡 Knowledge Base configuration:

• MCP integration is disabled by default for public repositories
• Jira integration is disabled by default for public repositories
• Linear integration is disabled by default for public repositories

You can enable these sources in your CodeRabbit configuration.

📥 Commits

Reviewing files that changed from the base of the PR and between f643d9e and 2083916.

📒 Files selected for processing (1)

• CHANGELOG.md (1 hunks)

🧰 Additional context used

🧠 Learnings (1)

📚 Learning: 2025-08-31T15:34:39.060Z

Learnt from: terabytesoftw
PR: yii2-extensions/app-basic#142
File: README.md:0-0
Timestamp: 2025-08-31T15:34:39.060Z
Learning: In yii2-extensions/app-basic project, the dev-road-runner branch is treated as the main configuration branch with no stable releases available. Static badges pointing to dev branches are intentionally used to direct users to the development version.

Applied to files:

• CHANGELOG.md

🪛 LanguageTool

CHANGELOG.md

[grammar] ~5-~5: There might be a mistake here.
Context: ... Installation section (@terabytesoftw) - Bug #143: Add Available stacks section...

(QB_NEW_EN)

🔇 Additional comments (2)

CHANGELOG.md (2)

5-5: LGTM — bug number correction is accurate and low risk.
No functional impact; changelog entry now references the intended issue.

---

5-5: Verify badge policy alignment with project conventions.
Per prior note that dev-branch badges are intentional for this repo, ensure the referenced change (moving “latest stable” badges) kept dev-branch badges prominent and stable links correct.