Publish the tested version
Everything you edit is a draft. Schedules, API calls, events and flows never run a draft — they run the published version, a frozen copy you chose on purpose. Publishing is the line between “I am trying things” and “this runs on its own”, and in this lesson you draw it for daily-report.
- Tell the draft from the published version
- Publish through the review dialog
- Know what publishing freezes: code, packages and imported scripts
- Act on the publish toast
Two versions of every script
A script always has a draft — what the editor shows, what Run uses — and, once published, a published version. You can keep editing and running the draft as much as you like; nothing that runs on its own notices until you publish again. The Code page tells you which state each item is in: Published, Not published, or ◆ changes not published when the draft has moved on since the last publish.
| What | Draft | Published |
|---|---|---|
| Run by | Run in the editor | Schedules, API endpoints, event triggers, flows |
| Changes when | You type and save | You press Publish |
| Packages | Resolved on each run | Frozen at publish |
Publish daily-report
- Save the draft you tested
Open
daily-report, make sure it holds the summary version from Quick start, run it once more and press Save. Publish stays disabled while there are unsaved changes, and when nothing changed since the last publish. - Review and publish
Press Publish. The dialog — Review the changes before publishing — shows the difference between the published code (nothing published the first time) and the new one. Read it, then press Publish.
- Read the toast
A toast says Published v1. If the script has an API endpoint that is on, the toast shows its URL with Copy URL; if not, it says This script is not on the API yet. and offers Turn on endpoint and Open Triggers. Leave the endpoint for the last lesson.
What publishing freezes
- The code. Editing the draft afterwards changes nothing that runs on its own. The Triggers tab reminds you: You have changes that are not published — triggers still run the published version.
- The packages. For Python, the exact version of every package is locked at publish and installed as-is on every published run, so a new release of a package cannot change last week’s script. See Dependencies.
- Imported scripts. If the script imports another one, the library’s published code is frozen with it. A library that was never published blocks the publish — Publish these first. — and the button Publish these first walks you through each one. See Script imports.
Going back
Configuration (the gear beside Publish) → Version history lists every published snapshot; select one to compare it with the latest and, if needed, make it the published one again. Your draft is untouched by that.