[ci] Enabled changelog bot from openwisp-utils

[pushpitkamboj]

Checklist

• I have read the OpenWISP Contributing Guidelines.
• I have manually tested the changes proposed in this pull request.
• I have written new test cases for new code and/or updated existing tests for changes to existing code.
• I have updated the documentation.

Description of Changes

Added a changelog bot workflow to automatically update changelogs when PRs are approved.

[kilo-code-bot]

Code Review Summary

Status: No Issues Found | Recommendation: Merge

The changelog bot workflow implementation is well-structured and follows security best practices.

Files Reviewed (2 files)

• .github/workflows/bot-changelog-runner.yml - Runner workflow that triggers on completion of the trigger workflow, downloads PR metadata, and calls the reusable changelog workflow
• .github/workflows/bot-changelog-trigger.yml - Trigger workflow that runs on PR approval, checks if the PR title matches noteworthy prefixes ([feature], [fix], [change]), and uploads PR metadata as an artifact

Security observations:

• Minimal permissions are granted (actions: read for the trigger workflow, contents: read, pull-requests: write, issues: write for the runner)
• Proper validation of PR number before passing to reusable workflow
• Author association check ensures only maintainers (OWNER, MEMBER, COLLABORATOR) can trigger
• Uses GitHub secrets properly for API keys and bot credentials

Functionality:

• The trigger workflow correctly filters PRs by title prefix (case-insensitive)
• Artifact retention is set to 1 day (appropriate for temporary data)
• The runner workflow validates the PR number format before proceeding

---

_{Reviewed by kimi-k2.5 · 79,312 tokens}

[coderabbitai]

Warning

Rate limit exceeded

@pushpitkamboj has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 51 minutes and 32 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: d01659a3-8142-4a12-82d1-1497e39bff06

📥 Commits

Reviewing files that changed from the base of the PR and between 72c280f and c6a7425.

📒 Files selected for processing (2)

• .github/workflows/bot-changelog-runner.yml
• .github/workflows/bot-changelog-trigger.yml

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch ci/changelog_bot

---

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.}