[pull] master from supabase:master#691
Merged
pull[bot] merged 14 commits intocode:masterfrom Feb 19, 2026
Merged
Conversation
* Upgraded `@radix-ui/react-tooltip` from version `^1.1.6` to `^1.2.8` in `package.json` and all relevant entries in `pnpm-lock.yaml` to use the latest release.
<!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Bug Fixes** * Fixed timestamp display in request logs to ensure accurate time representation. <!-- end of auto-generated comment: release notes by coderabbit.ai -->
Updates JS sdk documentation following stable release. Ran `make` in apps/docs/spec to regenerate tsdoc files. **Details:** - **Version:** `2.97.0` - **Source:** `manual` - **Changes:** Regenerated tsdoc files from latest spec files 🤖 Auto-generated from @supabase/supabase-js stable release. Co-authored-by: mandarini <6603745+mandarini@users.noreply.github.com>
https://linear.app/supabase/issue/FE-2595/dashboard-feedback-logarithmic-scale-option-for-custom-report-charts#comment-19c2f27a - adds logarithmic view option to charts <img width="1308" height="866" alt="CleanShot 2026-02-18 at 21 15 56@2x" src="https://github.com/user-attachments/assets/2ed95d0e-ccd0-4cd1-9a3b-ac9ae5628995" />
#42917) ## What kind of change does this PR introduce? Documentation and copy corrections. ## What is the current behavior? Several docs and one Studio file contain grammar, spelling, and capitalization issues: - JS v1 upgrade guide: "we'll continuing" (should be "we'll continue"), "Some the [PR]" (should be "See the [PR]"), extra space before comma - Realtime docs: "PostgresSQL" (should be "PostgreSQL") in 2 files - Kotlin SDK installing docs: "Websockets" (should be "WebSockets"), "Checkout the" (should be "Check out the") - Broadcast guide: "Websockets" (should be "WebSockets") in code comments (5 occurrences) - Prisma troubleshooting: "Checkout this" (should be "Check out this") - Edge function template: "Websocket Server Example" (should be "WebSocket Server Example") ## What is the new behavior? All grammar, spelling, and capitalization issues are corrected: - **Grammar**: "we'll continue" (verb tense), "See the [PR]" (correct word), removed extra space - **Spelling**: "PostgreSQL" (correct product name) - **Capitalization**: "WebSocket" / "WebSockets" follows the official W3C/IETF naming convention - **Word splitting**: "Check out" as a phrasal verb (two words), vs "checkout" the noun ## Files changed (8) - `apps/docs/docs/ref/javascript/v1/upgrade-guide.mdx` — grammar fixes (3 issues) - `apps/docs/docs/ref/self-hosting-realtime/introduction.mdx` — PostgresSQL -> PostgreSQL - `apps/docs/docs/ref/realtime/realtime.mdx` — PostgresSQL -> PostgreSQL - `apps/docs/docs/ref/kotlin/v2/installing.mdx` — WebSockets + Check out - `apps/docs/docs/ref/kotlin/installing.mdx` — WebSockets + Check out (2 occurrences) - `apps/docs/content/guides/realtime/broadcast.mdx` — Websockets -> WebSockets (5 occurrences) - `apps/docs/content/troubleshooting/prisma-error-management-Cm5P_o.mdx` — Check out - `apps/studio/components/interfaces/Functions/Functions.templates.ts` — WebSocket template name
…an RLS) (#42919) ## What kind of change does this PR introduce? Grammar corrections across documentation and test descriptions. ## What is the current behavior? Multiple docs and test files use "a" before acronyms that start with a vowel sound when pronounced: - "a HTTP" (pronounced "aitch-tee-tee-pee") should be "an HTTP" - "a API" (pronounced "ay-pee-eye") should be "an API" - "a RLS" (pronounced "arr-ell-ess") should be "an RLS" - "the all users" is redundant (should be "all users") ## What is the new behavior? All instances corrected to use proper English indefinite articles: ### Docs files (11 files): - `firebase-auth.mdx` — "the all users" -> "all users" (2 occurrences) - `log-drains.mdx` — "a HTTP drain" -> "an HTTP drain" - `securing-your-api.mdx` — "a HTTP 402" and "a HTTP 420" -> "an HTTP" - `scan-error-*.mdx` — "a HTTP 500" -> "an HTTP 500" - `roboflow.mdx` — "a HTTP interface" -> "an HTTP interface" - `auth-hooks.mdx` — "A HTTP Hook" -> "An HTTP Hook", "a HTTP hook" -> "an HTTP hook", "a HTTP error" -> "an HTTP error" - `auth-mfa.mdx` — "a HTTP 401" -> "an HTTP 401" - `password-verification-hook.mdx` — "a HTTP request" -> "an HTTP request" - `before-user-created-hook.mdx` — "a HTTP implementation" -> "an HTTP implementation" - `pgtap-extended.mdx` — "a API exposed schema" -> "an API exposed schema" - `error-codes.mdx` — "a RLS policy" -> "an RLS policy" - `broadcast.mdx` — "a RLS" -> "an RLS" ### Studio files (1 file): - `CronJobs.utils.test.ts` — "a HTTP request" -> "an HTTP request" (9 test descriptions) + "notationa" typo -> "notation" ## Additional context The rule: use "an" before acronyms pronounced with a leading vowel sound. "HTTP" starts with "aitch" (vowel sound), "API" starts with "ay" (vowel sound), and "RLS" starts with "arr" (vowel sound).
- `LintWarningsGuideLoader` was making unauthenticated GitHub API calls (60 req/hr per IP), causing flaky failures on shared CI runners - Uses the same GitHub App auth already in [github-discussion.ts](https://github.com/supabase/supabase/blob/9237db51f8db12e744e68500a4e3f42c43746734/apps/docs/scripts/search/sources/github-discussion.ts#L36) — no new env vars or deps needed Fixes https://github.com/supabase/supabase/actions/runs/22184533189/job/64154440387
## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## What kind of change does this PR introduce? We had these error ignores inside of sentry, doesn't make sense and rather should live next to the code
## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## What kind of change does this PR introduce? This lead to a bad experience where project status was not reachable and caused the query to show zero users. --------- Co-authored-by: Ivan Vasilov <vasilov.ivan@gmail.com>
## What kind of change does this PR introduce? Grammar corrections in comments and user-facing text. ## What is the current behavior? Several files have minor grammar issues: - Missing contraction: "it an error" (should be "it's an error") - Subject-verb disagreement: "a users loads" (should be "a user loads") - Missing possessive apostrophe: "a users organization" and "a users language" (should be "a user's") ## What is the new behavior? All grammar issues are corrected: - `apps/studio/instrumentation-client.ts` — "it's an error" + "a user loads" - `apps/docs/instrumentation-client.ts` — "a user loads" - `apps/www/data/partners/index.tsx` — "a user's organization" - `apps/docs/content/troubleshooting/customizing-emails-by-language-KZ_38Q.mdx` — "a user's language"
This PR updates mgmt api docs automatically. Co-authored-by: phamhieu <689843+phamhieu@users.noreply.github.com>
This pull request upgrades the `react-resizable-panels` dependency from version 2.x to 3.x. It also includes some minor improvements to component props and key usage for React elements. **Dependency upgrade:** * Upgraded `react-resizable-panels` from version 2.1.4 to 3.0.0. **Component improvements:** * Added a `key` prop to the `ResizablePanelGroup` in `LogTable.tsx` and to action buttons in `UnifiedLogs.tsx` to help React identify elements more efficiently. * Ensured unique `key` props for icons rendered in a map in `FilterSideBar.tsx` to prevent React warnings.
) ## I have read the [CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md) file. YES ## What kind of change does this PR introduce? - remove auto complete from filter bar + password manager - Update color of operator
This PR updates @supabase/*-js libraries to version 2.97.1-canary.0. **Source**: manual **Changes**: - Updated @supabase/supabase-js to 2.97.1-canary.0 - Updated @supabase/auth-js to 2.97.1-canary.0 - Updated @supabase/realtime-js to 2.97.1-canary.0 - Updated @supabase/postgest-js to 2.97.1-canary.0 - Refreshed pnpm-lock.yaml This PR was created automatically. Co-authored-by: mandarini <6603745+mandarini@users.noreply.github.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
5 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )