Before:
There was a bug with middleware rewrites for reference pages without
crawler versions (basically all references except the client SDKs).
There was a branch that was not handled (the requesting user agent is a
a bot, but the reference is not a client SDK), so it failed through to
the base case of NextResponse.next(), which 404s as that page does not
exist for a path like /reference/api/v1-deploy-a-function
After:
Fixed the branch. If all of the following are true:
- Is a reference page
- Requesting user agent is a bot
- Reference is not a client SDK
Then it should follow the same path as a non-bot request, because there
is no bot-specific version. That means it should be rewritten to teh
slugless page: /reference/api/v1-deploya-function => /reference/api
* Support default opt in feature previews via feature flag
* Add notice banner in /org/[slug] and /organizations if user is opted into the changes by default
* Clean up
* Update copy
* Update all docs that make references to the database settings to find the connection strings.
Update all docs that references the database settings for the compute and disk page
* run prettier
* run pnpm format instead of prettier directly.
* first run through, fix grammar and reword awkward sentences
* Fix typos and remove unnecessary whitespace
* Apply suggestions from code review
Co-authored-by: Tyler <dshukertjr@gmail.com>
---------
Co-authored-by: Tyler <dshukertjr@gmail.com>
Updated the email update note in the docs to explain that confirmation emails are still sent due to the Secure Email Change setting. Added a direct link to the relevant dashboard setting to help users better understand and manage the behavior.
* feat: expose pg_upgrade logs to end-users
* chore: don't display database operations group if deployed on the platform
* chore: remove log file from schemas
* chore: bring changes up to date
* Fix layout
* Refactor
* Clean up
* Check if using DefaultPreviewSelectionRenderer is sufficient
* Clean up file
---------
Co-authored-by: Joshen Lim <joshenlimek@gmail.com>
The old JWT generator code provided the anon and authenticated claims as strings. The format of this string is different from the format determined by KJUR if an object is provided (I'm guessing probably a whitespace or quote character thing, but I didn't dive down this rabbit hole.) This leads to incompatibilities when the token is used.
To prevent this, the tokens are now defined as objects and KJUR's own serialization is used.
Before:
Instructions for restoring a backup locally were buried inside the
Upgrading guide.
After:
Instructions for restoring a backup locally are on their own page in the
Local Development section. This page is linked from the Upgrading guide
because it is useful if a paused project has exceeded its restoring time
limit.
* fix(studio): Handle query timeout error
There is a global timeout of about 50s on /query endpoint
This would fail the request independently from the user statement timeout setting
add a case to handle this error and add a CTA to suggest the user of direct
connection for long running queries
* chore: apply pr comments
* Tiny refactor
---------
Co-authored-by: Joshen Lim <joshenlimek@gmail.com>
Jonathan Summers-Muir