Skip to content

chore: release main - #373

Open
supabase-releaser[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main
Open

chore: release main#373
supabase-releaser[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main

Conversation

@supabase-releaser

@supabase-releaser supabase-releaser Bot commented Aug 21, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

mcp-server-supabase: 0.11.1

0.11.1 (2026-08-28)

Bug Fixes

  • make server instructions intent-based instead of naming tools (#372) (fc54ea2)

This PR was generated with Release Please. See documentation.

@coveralls

coveralls commented Aug 21, 2026

Copy link
Copy Markdown

Coverage Report for CI Build 33184226672

Coverage remained the same at 96.52%

Details

  • Coverage remained the same as the base build.
  • Patch coverage: No coverable lines changed in this PR.
  • No coverage regressions found.

Uncovered Changes

No uncovered changes found.

Coverage Regressions

No coverage regressions found.


Coverage Stats

Coverage Status
Relevant Lines: 3036
Covered Lines: 2951
Line Coverage: 97.2%
Relevant Branches: 384
Covered Branches: 350
Branch Coverage: 91.15%
Branches in Coverage %: Yes
Coverage Strength: 50.92 hits per line

💛 - Coveralls

@supabase-releaser
supabase-releaser Bot force-pushed the release-please--branches--main branch 2 times, most recently from ea41ed0 to dff0bd6 Compare August 27, 2026 09:48
@supabase-releaser
supabase-releaser Bot force-pushed the release-please--branches--main branch from dff0bd6 to 67ee4c1 Compare August 28, 2026 15:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant