You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: AGENTS.md
+16Lines changed: 16 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -56,6 +56,10 @@ pnpm test
56
56
57
57
# Run tests with coverage
58
58
pnpm test:coverage
59
+
60
+
# Run the integration tests against a real deepnote-toolkit server (excluded from `pnpm test`).
61
+
# Needs `pip install "deepnote-toolkit[server]"`; point DEEPNOTE_PYTHON at that interpreter.
62
+
pnpm test:integration
59
63
```
60
64
61
65
#### Type Checking
@@ -119,6 +123,7 @@ Always run these checks before considering work complete:
119
123
- Test edge cases, error handling, and special characters
120
124
- For functions that generate code, test the exact output format
121
125
- Tests must not depend on live network calls or real Deepnote Cloud credentials — mock external APIs. Verifying behavior against the real Deepnote Cloud API is a manual, explicitly-requested step outside `pnpm test`, and any resources created that way (projects, notebooks, runs) must be cleaned up afterward
126
+
- Tests that start the real `deepnote-toolkit` server belong in `*.integration.test.ts` files. They are excluded from `pnpm test`, run with `pnpm test:integration`, and are exercised in CI by the "Runtime Integration" job. Run only one integration suite at a time per machine: its leaked-process guard sees every toolkit process of the interpreter, so a concurrent run's servers are reported as leaks
Before opening a pull request, check whether the change makes any documentation stale, and update it in the same pull request:
222
+
223
+
-`docs/` — user-facing product documentation, published at <https://deepnote.com/docs>. This directory is the source of truth for the whole product, including features developed in other repositories. Update it whenever user-visible behavior changes: CLI commands and flags, the `.deepnote` format, hosted MCP, integrations, or app behavior.
224
+
-`packages/<name>/README.md` and `packages/<name>/docs/` — reference for the package you changed.
225
+
-`skills/deepnote/references/` — agent-facing references; see the rules below.
226
+
-`README.md`, `CONTRIBUTING.md`, and `FILES.md` — repository layout, setup, and workflow changes.
227
+
228
+
Update only the pages your change actually affects. An unrelated documentation rewrite belongs in its own pull request.
229
+
214
230
## Keeping the Deepnote Skill in Sync
215
231
216
232
The `skills/deepnote/` directory contains reference documentation used by AI agents. When making changes to any of the following, you **must** also update the corresponding skill files:
Copy file name to clipboardExpand all lines: docs/custom-environment.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -20,7 +20,7 @@ Custom environments are especially valuable for complex projects where dependenc
20
20
21
21
We recommend building your custom Dockerfile on top of our `deepnote/python:3.x` base image to ensure compatibility with all Deepnote features. If you're creating an environment from scratch, your image must meet these requirements:
22
22
23
-
- Python (versions 3.10-3.13) installed and accessible via the `python` command
23
+
- Python (versions 3.10-3.14) installed and accessible via the `python` command
24
24
- Built for the `linux/amd64` platform (M1 Mac users: use `-platform linux/amd64` flag)
25
25
- Functioning `pip` installation that can install packages to Python's path
0 commit comments