build: changelog

[andyMrtnzP]

v1.5.1 - 2026-05-27

• Add destructive hints for tools
• Enable OpenAI connectors in OAuth

Summary by CodeRabbit

• Documentation
  • Updated changelog for v1.5.1 release, documenting destructive hints for tools and OpenAI connector OAuth enablement.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: bab6b26c-3df6-489b-8edc-03eb8a680df2

📥 Commits

Reviewing files that changed from the base of the PR and between b21484f and fedf541.

📒 Files selected for processing (1)

• CHANGELOG.md

---

Walkthrough

CHANGELOG.md is updated with a new v1.5.1 release entry dated 2026-05-27, documenting two changes: destructive hints for tools and enabling OpenAI connectors in OAuth.

Changes

v1.5.1 Release Notes

Layer / File(s)	Summary
v1.5.1 release entry CHANGELOG.md	CHANGELOG.md documents the v1.5.1 release with two feature updates: destructive hints for tools and OpenAI OAuth connector enablement.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• browserless/browserless-mcp#85: Both PRs update CHANGELOG.md with new version documentation without source code changes.

Poem

🐰 A changelog grows, so shiny and new,
With v1.5.1 and features to pursue,
Tools hint destructive, OAuth flows free,
The history marches, for all to see! 📝✨

🚥 Pre-merge checks | ✅ 3 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The description omits the required template sections entirely (Summary, Related issues, Changes, Test plan, Checklist) and only lists the changelog content without explaining context.	Follow the repository's PR template by adding sections for Summary, Related issues, Test plan, and Checklist; explain why the changelog was updated.
Title check	❓ Inconclusive	The title 'build: changelog' is vague and generic, using non-descriptive terms that don't convey meaningful information about what changelog entry was added.	Use a more descriptive title that indicates the version being released, e.g., 'chore: add v1.5.1 changelog entry' or 'docs: add v1.5.1 release notes'.

✅ Passed checks (3 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release/1.5.1

---

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