docs: update default region to Portland

[Arjun-Adhikari]

What changed

Updated the default region in the Regions & ACL documentation
from Seattle (sea1) to Portland (pdx1).

Seattle (sea1) remains listed as a supported region.

Why

The documentation was showing Seattle as the default region,
while Portland is currently the default region.

Verification

Verified the change and included before/after screenshots.
--Before


--After

Summary by CodeRabbit

• Documentation
  • Updated the available regions table to add US West – Portland (pdx1) as the default region.
  • Updated US West – Seattle (sea1) to no longer be marked as the default.

[changeset-bot]

⚠️ No Changeset found

Latest commit: c8457b0

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[vercel]

@Arjun-Adhikari is attempting to deploy a commit to the Ping Labs Team on Vercel.

A member of the Team first needs to authorize it.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: a42255aa-fff5-4930-81cd-00ea2391ca98

📥 Commits

Reviewing files that changed from the base of the PR and between e8ffeae and c8457b0.

📒 Files selected for processing (1)

• docs/src/app/(docs)/concepts/regions-acl/page.mdx

Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review.

---

Walkthrough

The regions documentation changes the default region from US West - Seattle (sea1) to US West - Portland (pdx1).

Changes

Regions documentation

Layer / File(s)	Summary
Update documented default region docs/src/app/(docs)/concepts/regions-acl/page.mdx	The table removes the default marker from Seattle and adds Portland as the default region.

Estimated code review effort: 1 (Trivial) | ~2 minutes

Merge Risk: ⚪ Minimal · up to c8457

This localized documentation update changes the displayed default region from Seattle to Portland while retaining Seattle as supported; no actionable merge-blocking risk remains after normal checks and review.

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the main documentation change: moving the default region to Portland.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…
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.

Full details: Docstring Coverage

Explanation

No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0 files. (1 skipped: 1 unsupported.)

✨ Finishing Touches 💡 1

🛠️ Fix failing CI checks 💡

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

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

[greptile-apps]

Confidence Score: 4/5

The SDK region alias contract should be updated alongside this documentation before merging so users can configure the newly documented default.

The new table directs users to pdx1, while the exported SDK region type still excludes that value and therefore rejects the documented configuration.

Files Needing Attention: docs/src/app/(docs)/concepts/regions-acl/page.mdx

Important Files Changed

Filename	Overview
docs/src/app/(docs)/concepts/regions-acl/page.mdx	Changes the documented default to Portland, but advertises an alias that the typed SDK configuration does not accept.

Prompt To Fix All With AI

### Issue 1
docs/src/app/(docs)/concepts/regions-acl/page.mdx:34
**Unsupported Portland region alias**

When a TypeScript user follows this table and configures `experimental_UTRegion` with `"pdx1"`, the SDK rejects it because the exported `UTRegionAlias` type does not include `pdx1`, preventing users from configuring the newly documented default region.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "docs: update default region to Portland" | Re-trigger Greptile}

[greptile-apps]

Unsupported Portland region alias

When a TypeScript user follows this table and configures experimental_UTRegion with "pdx1", the SDK rejects it because the exported UTRegionAlias type does not include pdx1, preventing users from configuring the newly documented default region.

Prompt To Fix With AI

This is a comment left during a code review.
Path: docs/src/app/(docs)/concepts/regions-acl/page.mdx
Line: 34

Comment:
**Unsupported Portland region alias**

When a TypeScript user follows this table and configures `experimental_UTRegion` with `"pdx1"`, the SDK rejects it because the exported `UTRegionAlias` type does not include `pdx1`, preventing users from configuring the newly documented default region.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.