https://linear.app/supabase/issue/FE-2226/fix-incorrect-baseline-and-max-iopsthroughput-values
- Centralized compute/disk limits in
packages/shared-data/compute-disk-limits.ts (MB/s, baseline+max
IOPS/throughput) and re-exported from shared-data.
- Hooked Docs compute/disk table into shared data, converted docs
text/table to MB/s baseline/max.
- Removed duplicated compute IOPS/throughput constants from Studio,
Studio now imports shared data.
- Updated Studio disk schema: compute-aware MAX IOPS/throughput
validation (MB/s), defaults computeSize to ci_micro, and gp3/io2 checks
use compute caps.
- Clarified disk update mutation to send throughput as MB/s despite
backend throughput_mbps field name.
- Added tests for compute-size mappings and IOPS helper logic.
- Added Infra ownership for shared compute/disk data in CODEOWNERS.
- Locked zod version via catalog and added zod dep to shared-data.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
* **New Features**
* Added a reusable Compute Disk Limits table and centralized compute
disk limits dataset for dynamic display.
* **Documentation**
* Replaced static per-size tables with a component-driven MB/s view;
clarified baseline vs. burst behavior and updated guides and
troubleshooting.
* **Bug Fixes**
* Validation and UI guidance now honor compute-size limits for IOPS and
throughput.
* **Tests**
* Expanded unit tests for sizing, mappings, and edge cases.
* **Chores**
* Published shared-data exports, added a validation schema, pinned a
dependency, and added ownership entries.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
## I have read the
[CONTRIBUTING.md](https://github.com/supabase/supabase/blob/master/CONTRIBUTING.md)
file.
YES/NO
## What kind of change does this PR introduce?
Bug fix, feature, docs update, ...
## What is the current behavior?
Please link any relevant issues here.
## What is the new behavior?
Feel free to include screenshots if it includes visual changes.
## Additional context
Add any other context or screenshots.
<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit
* **Documentation**
* Updated SSL enforcement guide: changed advisory tone from "note" to
"caution".
* Clarified that enabling SSL enforcement triggers a fast database
reboot and may cause longer interruptions for larger databases.
<sub>✏️ Tip: You can customize this high-level summary in your review
settings.</sub>
<!-- end of auto-generated comment: release notes by coderabbit.ai -->
fix(docs): remove duplicate Pricing header from storage-image-transformations page
Removes the redundant '## Pricing' heading from the main document since
the partial already includes this heading. This fixes the double header
issue on the Storage Image Transformations usage page.
Fixes#41316
Co-authored-by: 2003nayan <nayan@ai4mtech.com>
I think the existing sentence may cause people to believe that they can access one-click restore if they upgrade to a paid plan outside the 90 day restore window - I do not believe this is accurate.
I added the mention that if you upgrade within the 90 days period, they you may have one-click restore options
* docs: update link for Row Level Security documentation in JWT guide
* docs: update Figma sign-in link in Flutter guide
* docs: force link to Supabase Login with Apple to work (existing relative URL generates incorrect link in live site).
* docs: update link for Postgres UUID tutorial
* docs: update link for deprecated Android One Tap. Fix broken link to dart signInWithOAuth (the hydrated link on the live site is broken)
* docs: update links for MFA enforcement and backup documentation
* Update apps/docs/content/guides/auth/quickstarts/with-expo-react-native-social-auth.mdx
* Update apps/docs/content/guides/auth/social-login/auth-google.mdx
---------
Co-authored-by: Chris Chinchilla <chris@chrischinchilla.com>
* Add a grace period heading
* Cleanup
* docs(billing-faq): clarify clears after several cycles
* docs(billing-faq): update grace period explanation in billing FAQ
---------
Co-authored-by: Pamela Chia <pamelachiamayyee@gmail.com>
* make section language consistent
minor style and language tweaks on Infrastructure page
* improved Postgres upgrade instructions
* fix: language
* add top border
for better scan-ability, since Manage button is far away from related text
* Added new solutions pages and a new case study
* ci: Autofix updates from GitHub workflow
* Fixed solution page navigation
* Updated th e Soshi case study
* improve solutions navigation
* fix prettier
* rebase
* refine single quote
* add firebase hero visuals
* fix z layer for sticky nav
* animate results graph
* animated counter
* prettier
* fix quote on hackathon
* nits
* remove visuals from heros
* gs
* fix
* improve graph label
---------
Co-authored-by: Alan Daniel <stylesshjs@gmail.com>
Co-authored-by: Jonathan Summers-Muir <MildTomato@users.noreply.github.com>
* fix: rewrite relative URLs when syncing to GitHub discussion
Relative URLs back to supabse.com won't work in GitHub discussions, so
rewrite them back to absolute URLs starting with https://supabase.com
* fix: replace all supabase urls with relative urls
* chore: add linting for relative urls
* chore: bump linter version
* Prettier
---------
Co-authored-by: Chris Chinchilla <chris.ward@supabase.io>
* Update clone-project.mdx to show whats transferred clearer
* Added updates to include auth data and change the navigation bar
* adding beta version
* The formatted commit
---------
Co-authored-by: Rodrigo Mansueli <rodrigo@mansueli.com>
Jordi Enric