Skip to content

Commit df87f7d

Browse files
lucacasonatolucacasonato
committed
Deploy EA changelog for 21 July 2025
1 parent 981b896 commit df87f7d

File tree

3 files changed

+139
-6
lines changed

3 files changed

+139
-6
lines changed

‎deploy/early-access/changelog.md

Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -10,6 +10,49 @@ Deploy Classic documentation? [View it here](/deploy/).
1010

1111
:::
1212

13+
## July 21st, 2025
14+
15+
### Features
16+
17+
- New: Database support for Deno Deploy<sup>EA</sup> apps, allowing you to
18+
easily connect to and use Postgres databases in your applications.
19+
- Provision a Postgres database instance on AWS RDS, Neon, Supabase, or any
20+
other provider and then link it to your Deno Deploy<sup>EA</sup>
21+
organization.
22+
- Assign the database instance to an application, making it available in the
23+
application's environment.
24+
- Every timeline (production, each git branch, and previews) has their own
25+
isolated database with a separate schema and data, allowing you to test
26+
migrations and changes without affecting production data.
27+
- Use any Postgres client library to connect, including `npm:pg`,
28+
`npm:drizzle`, or `npm:kysely`.
29+
- Applications and playgrounds can now be renamed. Note, old `deno.net` URLs
30+
will no longer work after renaming, but custom domains will continue to
31+
function.
32+
- Applications and playgrounds can now be deleted.
33+
- Playgrounds now have an HTTP Explorer tab that allows you to make arbitrary
34+
HTTP requests to any URL served by the playground. This is useful for testing
35+
APIs or other services that do not serve a web page.
36+
- You can now delete entire folders in the playground file explorer by pressing
37+
the delete button next to the folder name.
38+
- You can now drag a zip file onto the playground file explorer to upload all
39+
files in the zip file to the playground.
40+
41+
### Bug fixes
42+
43+
- `DENO_` prefixed environment variables such as `DENO_CONDITIONS`,
44+
`DENO_COMPAT`, and `DENO_AUTH_TOKENS` can now be set without error.
45+
- The `DENO_REVISION_ID` environment variable is now correctly exposed to
46+
applications and playgrounds.
47+
- The custom domain assignment drawer now does shows custom domains that are
48+
already assigned to another application or playground as disabled.
49+
- The network usage graph on the metrics page now correctly shows incoming and
50+
outgoing traffic. Previously, the data shown was incorrect.
51+
- For newly created organizations the first build now waits until the
52+
`<org>.deno.net` domain is provisioned before the routing step.
53+
- Pressing `Ctrl-S` / `Cmd-S` in the playground now saves the current file and
54+
triggers a build, instead of opening the browser's save dialog.
55+
1356
## July 9th, 2025
1457

1558
### Features

‎deploy/early-access/reference/apps.md

Lines changed: 32 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -41,11 +41,40 @@ Environment Variables". For more details on environment variables, see the
4141
[Environment Variables and Contexts](/deploy/early-access/reference/env-vars-and-contexts/)
4242
documentation.
4343

44-
## Limitations
44+
## Renaming an application
45+
46+
Applications can be renamed by editing the app slug on the app settings page.
47+
This will update the default domain names associated with the app, as they are
48+
based on the app slug. The new slug must be unique within the organization (i.e.
49+
must not be in use by another app or playground in the same organization).
50+
51+
:::warning
52+
53+
Any previous `deno.net` URLs pointing to the app will no longer work after
54+
renaming.
55+
56+
Custom domains will continue to work, as they are not tied to the app slug.
57+
58+
:::
59+
60+
## Deleting an application
4561

46-
> ⚠️ Apps cannot currently be deleted.
62+
Applications can be deleted from the app settings page. This will remove the app
63+
and all its revisions from the organization. All existing deployments will
64+
immediately stop serving traffic, and all custom domain associations will be
65+
removed.
4766

48-
> ⚠️ Apps cannot currently be renamed.
67+
No traffic will be served from the app after deletion, and it will not be
68+
possible to access the app or its revisions. Deleted apps cannot be restored
69+
through the Deno Deploy UI.
70+
71+
:::info
72+
73+
Deleted an app by mistake? Contact Deno support within 30 days to restore it.
74+
75+
:::
76+
77+
## Limitations
4978

5079
> ⚠️ Apps cannot currently be transferred to another organization.
5180

‎deploy/early-access/reference/playgrounds.md

Lines changed: 64 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -53,10 +53,71 @@ The playground editor consists of five main sections:
5353
The playground content automatically saves when you click the "Deploy" button or
5454
when the editor loses focus.
5555

56-
## Current limitations
56+
## Uploading files
5757

58-
> ⚠️ Playgrounds cannot currently be deleted.
58+
You can upload a zip file containing files and directories to the playground by
59+
dragging into the file browser area. The contents of the zip file will be
60+
extracted into the playground, preserving the directory structure.
5961

60-
> ⚠️ Playgrounds cannot currently be renamed.
62+
> ⚠️ The playground editor does not support uploading individual files or
63+
> directories.
64+
65+
## Using the HTTP explorer
66+
67+
The HTTP Explorer tab in the playground allows you to make arbitrary HTTP
68+
requests to any URL served by the playground. This is useful for testing APIs or
69+
other services that do not serve a web page.
70+
71+
To use the HTTP Explorer enter the path and query parameters for the request you
72+
want to make, select the HTTP method (GET, POST, etc.), and click on the button
73+
labeled with the selected method.
74+
75+
Additional request headers can be added by clicking the "Set Headers" button.
76+
77+
After the response has been made, the HTTP Explorer will display the response
78+
status, headers, and body.
79+
80+
To view the trace for the request, click on the "Trace" button in the response
81+
section. This will open the request trace for the request in a drawer overtop
82+
the playground editor. From there you can also view any `console.log` output
83+
that was captured during the request.
84+
85+
## Renaming a playground
86+
87+
You can rename a playground by editing the playground slug on the playground
88+
settings page. This will update the default domain names associated with the
89+
playground, as they are based on the playground slug. The new slug must be
90+
unique within the organization (i.e. must not be in use by another app or
91+
playground in the same organization).
92+
93+
:::warning
94+
95+
Any previous `deno.net` URLs pointing to the playground will no longer work
96+
after renaming.
97+
98+
Custom domains will continue to work, as they are not tied to the playground
99+
slug.
100+
101+
:::
102+
103+
## Deleting a playground
104+
105+
Playgrounds can be deleted from the playground settings page. This will remove
106+
the playground and all its revisions from the organization. All existing
107+
deployments will immediately stop serving traffic, and all custom domain
108+
associations will be removed.
109+
110+
No traffic will be served from the playground after deletion, and it will not be
111+
possible to access the playground or its revisions. Deleted playgrounds cannot
112+
be restored through the Deno Deploy UI.
113+
114+
:::info
115+
116+
Deleted a playground by mistake? Contact Deno support within 30 days to restore
117+
it.
118+
119+
:::
120+
121+
## Limitations
61122

62123
> ⚠️ Playgrounds cannot currently be transferred to another organization.

0 commit comments

Comments
 (0)