The move's fork gate checked only the workspace's forking rule. A role
missing a capability would get the default role in a fork it creates, so
the gate also refuses restricted roles, as the workspace picker does.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Creating the fork takes seconds, during which an edit in the session's
preview can save a draft in the parent that the move's list did not have.
The move now flushes and lists the drafts again before the transfer, and
reopens the dialog on the created fork when they changed.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
A turn started while the move dialog was open owns the cross-tab hold the
move would take, and the move would release it while the turn still runs.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
- Move stays enabled while the dialog lists conflicts; confirming re-reads
them, so a draft discarded in the fork meanwhile no longer blocks it.
- A dialog left open while another tab moved the session closes instead of
moving from the old workspace.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
- replace_existing deletes only the fork drafts the transfer replaces, so a
draft discarded in the parent after the clone does not take the fork's
copy with it.
- Confirming a move lists the session's drafts again once no turn can
start, and sends the user back to the dialog if the list changed.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
- The tab doing a move disables its composer until the move ends, and the
move checks again for a running turn once a new fork exists.
- Saves still pending in editors open in an existing fork are flushed
before the transfer, so they surface as conflicts instead of landing on
the moved draft later.
- The transfer copies, conflict-checks and removes only the source rows it
locked and validated; a draft saved at a requested key after the lock is
left out.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* feat: name the previewed item in an empty session's composer instead of greeting
* feat: name the item's kind in the empty session's composer placeholder
* fix: name the previewed item as its tab does, so view tabs get the summary
- A new fork now gets the same transfer as an existing one, with
replace_existing set only when this move created the fork, so a draft
saved after the clone reaches the fork and an existing fork's own drafts
still go through the conflict check.
- The transfer runs the operator composition check on each draft in the
target workspace, the same check as a direct save there.
- Editors already open on a moved item in the fork reload it from the
server.
- Other tabs on the session hold their composer during a move and adopt
the session's new workspace when it ends.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: add job_id, step_id and flow_path to every executor's step error
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: take the step error's flow_path from the pulled job, not a query
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: add step context to native ts errors in the executor instead of process_result
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat: add a home setting to hide empty folders
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: keep empty folders listed in a workspace holding nothing else
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: keep a folder created from home listed while empty folders are hidden
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: say which kinds keep a folder listed when hiding empty folders
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: hide the empty-folders toggle where it has no effect, honour it beside pipelines
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: keep empty folders listed when the item count request fails
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: keep the tree when only non-empty folders remain past the loaded window
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* refactor: hide empty folders inside the tree only, keep main's empty-state choice
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: stop starred items showing a starred removal in the editor diff
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: ignore starred in every value diff
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* docs(readme): modernize the code examples, cover in-browser AI building, trim the env var table
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs(license): move the re-expose and internal-use terms from the README into LICENSE, summarize them in the README
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs(readme): use a data table in the script example, add a data section (data tables, DuckDB, DuckLake, pipelines)
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* docs(readme): drop the local dev setup section, point to README_DEV.md
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs(readme): drop the contributors section
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* docs(readme): lead with code-first workflows, apps and AI agents, and the review guardrails for AI-built code
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs(readme): name Lovable among the alternatives
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs(readme): name n8n among the alternatives
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat: authenticate Windmill AI to Anthropic with per-user Workload Identity Federation
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: reject WIF-only Anthropic resources in agent steps, scale token refresh margin
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor: move Anthropic WIF to a separate anthropic_federated resource type
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: point agent steps at an anthropic resource instead of a federated one
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: report a federated resource missing a field instead of reading it as standard
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat: count Anthropic federated token exchanges in feature_usage
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: update ee-repo-ref to 747336910e5c7498544613ad7863cea59f4db6a1
This commit updates the EE repository reference after PR #923 was merged in windmill-ee-private.
Previous ee-repo-ref: 3ea70adff288448f7318ff20b41225fd726ca8d1
New ee-repo-ref: 747336910e5c7498544613ad7863cea59f4db6a1
Automated by sync-ee-ref workflow.
* feat: authenticate AI agent steps with anthropic_federated resources (#11999)
* feat: authenticate AI agent steps with anthropic_federated resources
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: keep get_id_token's signature for its EE callers
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: update ee-repo-ref to 747336910e5c7498544613ad7863cea59f4db6a1
This commit updates the EE repository reference after PR #923 was merged in windmill-ee-private.
Previous ee-repo-ref: 3ea70adff288448f7318ff20b41225fd726ca8d1
New ee-repo-ref: 747336910e5c7498544613ad7863cea59f4db6a1
Automated by sync-ee-ref workflow.
* feat: switch between anthropic and anthropic_federated when adding a resource
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: keep registryCcCapable's doc comment on it
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: windmill-internal-app[bot] <windmill-internal-app[bot]@users.noreply.github.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: windmill-internal-app[bot] <windmill-internal-app[bot]@users.noreply.github.com>
* chore: update node to 26 in the docker image and CI
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: pin node to 24.22.1 in the worker image for CVE-2026-111497
The unpinned NodeSource install was served from the build cache, so images
built after the security release still shipped 24.22.0. Reverts the node 26
bump.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* chore: tighten file handling in deno/bun, stricter codebase tarball, executor isolation
* fix(worker): gate now-unused extract_tar behind its enterprise+parquet caller
Removing the codebase-bundle caller of global_cache::extract_tar left its only
remaining caller, pull_from_tar, gated on enterprise+parquet, so under other
feature sets the function (and its tokio::time::Instant import) became dead code
and failed CI's -D warnings build. Gate the definition and the import with the
same cfg as the caller so they appear and disappear together.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
812ff6ea5e was squashed from a branch based before 8af48429 and reverted its
changes to these three files. Restore them as they were in 8af48429.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The database name of a Postgres resource was the bare positional argument of
pg_dump and the value of psql's --dbname. Both forms are interpreted: as a
positional argument a name opening with `-` is read as an option of pg_dump
(`--file=`, `--restrict-key=`), and in both forms a name holding `=` is
expanded as a libpq connection string that overrides the host, port and user
Windmill passed before it. libpq reads PGDATABASE as a plain name, neither
parsed nor expanded, so the name now goes there.
The change is in the shared helpers, so it covers every caller:
import_pg_database, export_pg_schema, datatable_clone::make_copy,
generate_initial_datatable_migration and pg_import_dump. pg_dump's invocation
is extracted into pg_dump_command() beside the existing psql_command() so the
argument vector can be asserted on directly.
Beside that:
- resolve_pg_source_checked_with_kind() now refuses a name opening with `-`
for every source and target it resolves, where validate_dbname() only ever
reached a target. The check is deliberately narrower than validate_dbname():
a source is any database a user already has, and `2024_archive`, `my.db` or
a non-ASCII name are all names Postgres accepts and resources carry today.
- export_pg_schema and import_pg_database now require the `code` capability,
the one the data table migration endpoints next door already ask for. Both
make the API server run pg_dump/psql as children of its own process against
a database the request names, so the role that may not run code should not
reach them; they stay open to every author, who can run pg_dump in a job
anyway. The frontend offers both only from the database manager.
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
Recognise the worker's own init and periodic scripts through a single helper shared by the bash and PowerShell executors, based on the workspace, identity and tag they are queued with.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Set `keep_caps: false` in the python, ruby and R dependency install/lock profiles, matching the run profiles, and build the uv argument list in `download_deps.py.sh` directly instead of through a command string.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Run `cargo sweep` and `cargo generate-lockfile` from a worker-owned scratch directory instead of the job directory, pointing at the crate with `--manifest-path`.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
A PR whose body contains `[skip-ai-review]` no longer triggers the
automatic Codex, Pi and Claude reviews on open/ready/synchronize, and is
left out of the weekly merged-PR summary. Explicit requests (workflow_call
from the review commands) still run.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* oauth: linkedin OIDC default scopes + scope_options, quickbooks asks isSandBox
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: leave quickbooks connect fields to #11960
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
The change-versions job on the release PR failed to push after the branch
was deleted on merge, so v1.848.0 shipped with only version.txt bumped.
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat: run a workspace handler when a secret variable expires
Secret variables gain an optional `value_expires_at`, and a workspace can point
at a script or flow to run once that date passes, so a rotation is driven by the
platform instead of tracked out of band.
The secret never leaves the database. The sweep selects the path, description and
expiry and nothing else, so the handler is given a reference to rotate rather than
a value to handle. Job results are stored in cleartext and shown in Runs, which is
what makes that a boundary rather than a preference; a test asserts the job's args
never contain the value.
Each row is claimed by writing `expiration_dispatched_for` in the same transaction
as the push, so a failed push un-claims it and a lost race claims nothing. Moving
the date re-arms the row; re-saving the same date does not. A pass takes at most
100 rows under a transaction-scoped advisory lock, and orders so that one broken
workspace cannot starve the rest.
Dispatch runs as `g/variable_expiration_handler`, exempt from the CE group limit
and from non-premium exec metering the way the error and schedule handlers already
are. A handler that keeps failing backs off and raises a critical alert instead of
retrying every pass, and the back-off ends when the handler is repointed.
The expiry travels with the variable through workspace clone, tarball export and
workspace comparison. The dispatch marker deliberately does not, so a fork re-arms
on its own copy.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* feat(frontend): expose variable value expiration in the UI
The variable drawer takes an optional expiry on a secret value, and the variables
list badges it, turning red once the date has passed. A workspace settings tab
picks the handler, its extra args, and whether variables under `u/` are skipped.
That mute flag is stored inside the handler setting, so the toggle stays disabled
until a handler is picked: saving it on its own would clear the setting it lives
in and still report success.
The expiry is carried as a tri-state through the draft deploy and copilot paths —
absent leaves the remote value alone, an explicit null clears it — so deploying a
draft cannot silently drop a date someone set elsewhere.
The settings tab names the one case where the configured identity does not apply:
a handler script carrying `on_behalf_of` runs as that user rather than as
`g/variable_expiration_handler`, which matters because the same tab asks the admin
to grant that group write access to the variables it rotates.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* feat(cli): sync variable expiry and the workspace expiration handler
`wmill sync` carries `value_expires_at` on variables in both directions, and
pushes the workspace handler alongside the error and success handlers in the
grouped settings format. Dropping the key from a variable's yaml clears the
remote expiry, so the file stays canonical rather than accumulating fields that
can only ever be added.
The handler follows the same rule, with the caveat recorded where the type is
declared: an omitted handler only reaches the clear when some other setting
differs, because the push short-circuits on a comparison that walks the local
object's keys and so never sees a missing one. That gate is shared with the two
existing handlers and is left as it is here.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix(frontend): open the variable expiration handler template in a new tab
The "Create a handler" button hands its script template to /scripts/add through
the URL hash, which `load` reads from `window.location`. A client-side navigation
leaves the previous page's hash in place, so the payload was dropped and the
editor opened on the default template at a `u/` path. `target="_blank"` forces a
full page load, matching the success handler's "Create from template" button.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix(frontend): make the variable expiry field state its own status
The expiry field rendered a DateTimeInput whose time defaults to 12:00 when it
holds no value, so a variable with no expiry looked like one already configured,
and "cleared" looked identical to "never set". Setting an expiry is optional, so
the field has to say which it is.
Rebuild it on the shape ScriptAdvancedSettings already uses for Timeout, Cache and
Concurrency limits: a toggle whose checked state is the stored value being present,
seeding a date on enable rather than revealing an empty picker, with the input
under its own label. Drop `clearable` with it, so the toggle is the single way to
mean "no expiry" instead of competing with an X.
Stop the surrounding copy promising a run that may not happen. A handler is only
dispatched if the workspace has one configured and does not skip u/ paths, so the
list tooltip now states the date alone, and the form hedges both conditions,
naming the u/ mute only on personal paths where it can apply.
Also anchor the mute toggle's tooltip: Popover's trigger is a span around a
block-level label, which stretched to the full width of its SettingCard and left
the popup floating beside the card rather than under the control.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix(rust-client): initialize value_expires_at in the variable models
The generated `CreateVariable` / `EditVariable` structs gain the field from
openapi.yaml, and client.rs builds both with exhaustive literals.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix(frontend): drop extra_args when the variable expiration handler is cleared
Clearing the handler nulls the whole setting server-side, extra_args included,
but the tab kept its loaded copy. A handler picked afterwards without reloading
was persisted with the cleared one's arguments, which the tab does not display.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* feat: back the variable expiration handler's built-in Slack and Teams destinations
Backfills the Slack bot token grant for g/variable_expiration_handler, mirroring
20231016142659 for g/error_handler: the slack_bot folder's extra_perms is written
once at Slack connect and never refreshed, and disconnecting leaves the folder
behind, so workspaces that already connected Slack cannot pick the grant up from
the creation-time list alone.
Adds run_variable_expiration_test_job so an admin can exercise the handler on
demand rather than waiting for a real expiry, which may be months away. It goes
through push_variable_expiration_handler so the test run proves what matters:
the handler resolves, and the group can read what it needs, under the same
identity and argument shape the sweep uses.
Also covers extra_args on the edit endpoint, which the settings tab now writes
for the built-ins' channel. The endpoint rebuilds the setting from the request,
so an omitted extra_args erases it.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Do7wJTnL6MG6ngFpCGW4DG
* feat(frontend): offer Slack and Teams as variable expiration handlers
Gives the variable expiration tab the same no-code destinations the workspace
error handler has, so "tell #ops before this credential expires" no longer
requires writing a script.
A sibling component rather than a fourth mode of ErrorOrRecoveryHandler: that
one is shared with the workspace error handler and the three schedule handlers,
and its stripped-args list, hub path suffixes and Email tab are all
error-shaped. This reuses the pieces that are already generic
(SlackConnectionStatus, TeamsConnectionStatus, ChannelSelector, ScriptPicker,
SchemaForm) and leaves those five call sites untouched.
extra_args stops being an API/CLI-only escape hatch now that the built-ins write
their channel into it, so it joins the unsaved-changes comparison and the
discard path, normalised through the existing helper that drops the two
auto-managed keys.
The two hub ids are placeholders until the scripts are pushed to the hub.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Do7wJTnL6MG6ngFpCGW4DG
* fix(frontend): scope the handler identity notice to the chosen destination
The notice told every admin to grant g/variable_expiration_handler write access
to the variables it rotates. That is right for a custom handler and wrong for
the built-ins, which only post a message and are granted the Slack bot token by
migration. Following it for a Slack handler would hand a group write access to
the workspace's secrets for no reason.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Do7wJTnL6MG6ngFpCGW4DG
* feat(frontend): flag the Slack and Teams handlers as EE
Connecting a workspace to Slack or Teams is EE-only (oauth2_oss.rs returns
"Slack only available on enterprise"), so on CE those two tabs can never be
completed. Says so up front, the way the error/success handler tab does,
instead of leaving the user at a "not connected" badge with no working path.
Only on those two tabs: a custom script or flow handler is CE.
Drops the "Connect Slack first" alert, now that the banner and the connection
badge above it already say it twice.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Do7wJTnL6MG6ngFpCGW4DG
* chore(backend): regenerate the sqlx cache after the merge
The merged workspace_settings column list in change_workspace_id is a new
query text, so it needs a new cached entry. Drops the two pre-merge entries
it supersedes; both had been left with conflict markers by the merge, since
rename/rename markers are eight characters and escape the usual scan.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Do7wJTnL6MG6ngFpCGW4DG
* fix(cli): narrow the expiry-clear check to a variable that exists remotely
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01Do7wJTnL6MG6ngFpCGW4DG
* feat(frontend): point the built-in handlers at their published hub scripts
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* chore(backend): regenerate the sqlx cache after the merge
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* fix(frontend): disable the Slack and Teams handler controls without a license
Matches the workspace error handler, which greys out its built-in destinations
and hides the test button on an unlicensed instance. The custom destination stays
editable: unlike the error handler, the variable expiration handler itself is not
an EE feature.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* feat: record which destination a variable expiration handler uses
handler_configured now counts slack, teams, custom or cleared instead of
set or cleared, so usage shows whether the built-in destinations are picked.
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix(frontend): let the variable expiration handler template run on any worker
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: guard the variable expiration test endpoint and correct its help text
* fix: reuse the error handler's slack arg and built-in path helpers
* docs: trim variable expiration sweep and backfill comments
* feat: put the variable value expiration under an advanced section
* fix: restrict the expiration test job to built-ins and keep expiry on conflict reload
* fix: link the expiry hint to the variable's workspace and document built-in test paths
* fix: give the expiration sweep its own lock id and reuse double_option
* fix: pin the variable expiration presets so the hub-paths test accepts them
* feat: let the variable expiration handler set how far ahead it runs
* fix: give the notify before expiry setting its own card
* feat: remind the variable expiration handler at a set interval
* fix: tighten the gap between the Slack channel field and its test button
* feat: refuse a value expiry on variables linked to an OAuth account
* refactor: reuse the shared handler form for variable expiration
* refactor: sweep expiring variables round-robin and check the handler exists
* chore: trim comments to the constraints they record
* fix: compare expiry dates by moment when deploying a variable draft
* refactor: rename value_expires_at to value_valid_until
* fix: neutralize variable fields in expiration handler args
* fix: reserve the variable_expiration_handler group name for admins
* fix: send first expiry notices before reminders
* test: pin that a handler failing to start leaves its rows unclaimed
* chore: say any hub handler path skips the existence check
* fix: empty a pre-existing handler group before granting it the Slack token
* docs: correct the registered feature usage counts
* fix: let a workspace whose handler failed to start sit out for an hour
* fix: send first notices before reminders across workspaces
* fix: end a failed handler's wait as soon as it is redeployed
* fix: show an expiry-only variable change in the AI fork diff
* chore: regenerate workspace tool schemas
* test: keep one variable expiration guard per behavior
* fix: use the renamed hub expiration handlers and template
* feat: carry the variable expiry in windmill-utils-internal 1.8.4
* fix: keep the variable expiry through MCP drafts
* chore: bump windmill-utils-internal to 1.8.4
* fix: keep the variable expiry through mcp deploys
* fix: disable saving a slack or teams expiry handler without ee
* fix: skip the failure mark when the expiry handler was saved mid-sweep
* fix: count expiry telemetry only where the expiry changed
* test: assert the exact variable expiry in export and cli push tests
* fix: stamp an expiry handler failure with the pass's read time
* fix: wait for a pending handler lock instead of marking it failed
* test: isolate expiry handler tests from the deployed-script cache
* fix: retry a failing expiry handler every pass instead of waiting an hour
* chore: update ee-repo-ref to b6e23d229966cf0019c0a1926a254fda658d8def
This commit updates the EE repository reference after PR #744 was merged in windmill-ee-private.
Previous ee-repo-ref: c52c06d145b13a6fb04459e85ca5818bf3c1bff4
New ee-repo-ref: b6e23d229966cf0019c0a1926a254fda658d8def
Automated by sync-ee-ref workflow.
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: windmill-internal-app[bot] <windmill-internal-app[bot]@users.noreply.github.com>
Co-authored-by: hugocasa <hugo@casademont.ch>
* fix: home's acting-on follows the workspace home switches to
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: say home's draft also follows its workspace on mount
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: home leaves a draft picked onto another workspace to the session page
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: home keeps its own draft across a workspace switch made on another page
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: home lets go of its draft once the session page takes it
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* feat: fill docusign account_id and base_uri on connect
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat: fill salesforce and quickbooks connect fields through connect_fields
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: note connect_fields source trust and pin sandbox inheritance
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: update ee-repo-ref to 5517ff637a675aee66d4e417d3f37266045f0e0c
This commit updates the EE repository reference after PR #913 was merged in windmill-ee-private.
Previous ee-repo-ref: ba98803b236f018ed45199344f744ea1387afe2d
New ee-repo-ref: 5517ff637a675aee66d4e417d3f37266045f0e0c
Automated by sync-ee-ref workflow.
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: windmill-internal-app[bot] <windmill-internal-app[bot]@users.noreply.github.com>
Co-authored-by: Ruben Fiszel <ruben@windmill.dev>
* fix: fork a raw app into the raw app builder, in its session when there
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: keep the source's sandbox and sdk scopes on a forked raw app
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: fork a raw app from the editor's content, not the server's copy
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: keep the log indexer starting when a stored day chunk is broken
Bumps the EE ref to the companion change in windmill-ee-private.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: update ee-repo-ref to f806a793b07105417dd7a592fbfc93ec2f226d4e
This commit updates the EE repository reference after PR #921 was merged in windmill-ee-private.
Previous ee-repo-ref: 008b710eb0d92b382b9d20835c9fa8a41d867dad
New ee-repo-ref: f806a793b07105417dd7a592fbfc93ec2f226d4e
Automated by sync-ee-ref workflow.
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: windmill-internal-app[bot] <windmill-internal-app[bot]@users.noreply.github.com>
* fix: keep a fork's own auto-pull settings when applying settings.yaml
The settings.yaml on a fork branch carries the parent's git_sync, so a
pull into a fork failed with "Auto-pull cannot be configured on a fork
workspace". The fork now keeps its own auto_pull and fork_open_prs and
a throwaway fork drops promotion repos, matching fork creation.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: show the parent's git sync side in a fork's settings document
A fork's settings.yaml is the parent's file, so exporting the fork's own
git_sync (auto-pull off, no fork PRs, no promotion repos) and merging
the fork back would turn off the parent's auto-pull. The fork's document
now states the parent's values for the parts the parent owns, and
applying one keeps the fork's own: the two are inverses, so a round
trip is a no-op. Repos the fork does not carry are no longer added.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: drop promotion repos on non-dev forks and keep the fork's repo order
A dev workspace detached from dev keeps its promotion repo, which the
validator refuses on a non-dev fork, so its pull still failed. And a
fork whose own repo came before a shared one saw its document reorder
the repos, so re-applying it was a change. The apply now drops
promotion repos unless the fork is a dev workspace and emits repos in
the fork's own order.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: apply only a fork's synced git sync keys from settings.yaml
Taking the parent's repo entry and restoring a few fork-owned fields let
every unlisted field flow from the parent: a dev workspace lost its
promotion mode, and a malformed repository list emptied the fork. The
fork now starts from its own git_sync and takes only the item filters
(settings, exclude_types_override, group_by_folder) of the repos it
carries; the document is the parent's block with those keys from the
fork. The parent's block is folded down the ancestor chain, so a fork
of a dev workspace shows the root's auto-pull too.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: sync a fork's legacy git sync filters and drop its stale promotion repos
Repos without their own settings filter by the workspace-level
include/exclude lists, which a fork now takes from settings.yaml while
it stores them. A non-dev fork's apply drops the promotion repos it
kept from a dev designation, so the write passes the save's check. An
unset and a null key no longer count as a difference, so settings.yaml
is not rewritten over the two spellings.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: copy the filters a repo syncs by between a fork and settings.yaml
A fork on per-repo settings applying a file still on workspace-level
filters lost its repo settings and gained none, so it synced nothing.
The copy now goes between each side's effective filters, the repo's
settings with the workspace-level lists they fall back to filled in,
so either layout maps onto the other. The workspace-level keys are no
longer synced separately, and a null git_sync leaves them alone.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: sync a fork's filters only between per-repo settings on both sides
The workspace-level filter layout reads an empty or missing per-repo
list as "use the workspace's", so it cannot state some filters the
per-repo layout can, and every mapping between the two widened or
emptied a fork's filters on some round trip. Filters now cross only
when neither the fork nor the file uses workspace-level filters;
otherwise the fork keeps its own and its document keeps the parent's.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: detect the legacy git sync layout by its fallback filters only
exclude_path and extra_include_path are read only beside a fallback
include_path, and the save leaves them behind once every repo has
migrated, so they no longer mark a workspace as legacy. Rewraps the
comment on the synced keys to say when settings crosses.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* fix: return variable.value as text so widening it changes no result type
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: update ee-repo-ref to 16858ac4cf7326ed3d5a6fae1a97fcade5a97af7
This commit updates the EE repository reference after PR #920 was merged in windmill-ee-private.
Previous ee-repo-ref: dcf6219b5635fc93f11dcb2fd0564c1c5f8407b3
New ee-repo-ref: 16858ac4cf7326ed3d5a6fae1a97fcade5a97af7
Automated by sync-ee-ref workflow.
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: windmill-internal-app[bot] <windmill-internal-app[bot]@users.noreply.github.com>
* feat: read-only ai sessions on protected workspaces with a use, plan and build picker
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: address local review findings on the use, plan and build picker
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: address CI review findings on use mode and protected sessions
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: hold test-run forms and pending protection lookups to use mode
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* refactor: fetch rules once per send and dedupe helpers and prompt text
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: send role-locked operators to an admin and cover it with an eval
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* feat: count the work mode each session message runs in
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* chore: regenerate the mcp session definitions after merging main
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* feat: rename build to use & build and let the chat ask to switch modes
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: word a declined mode switch by the switch, not the mode
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* chore: update ee-repo-ref to 55445977dd05c25791388070182c77f4dbc20c0e
This commit updates the EE repository reference after PR #915 was merged in windmill-ee-private.
Previous ee-repo-ref: 7f7bf7003e356346ce74395af02c5bdf14f38781
New ee-repo-ref: 55445977dd05c25791388070182c77f4dbc20c0e
Automated by sync-ee-ref workflow.
---------
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-authored-by: windmill-internal-app[bot] <windmill-internal-app[bot]@users.noreply.github.com>
* [ee] fix: run unstamped git auto-pulls as a superadmin when the workspace has no admin
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* bump ee ref: log the fallback identity
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* chore: update ee-repo-ref to 6858e4cbd515b52713afea8dc32b23072af2248c
This commit updates the EE repository reference after PR #918 was merged in windmill-ee-private.
Previous ee-repo-ref: 03d89d10bdd9fba9d1184dc75f8582a5ad3741a8
New ee-repo-ref: 6858e4cbd515b52713afea8dc32b23072af2248c
Automated by sync-ee-ref workflow.
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: windmill-internal-app[bot] <windmill-internal-app[bot]@users.noreply.github.com>
* feat: open empty ai sessions with the home build-with-ai composer
* feat: vertically center the empty session composer
* fix: drop the stray indent on the session composer's rotating placeholder
* fix: give the starter composer a stable accessible name
* feat: pick workspace, fork and permission mode from the home composer
* fix: hand off the workspace home displays, not only an explicit pick
* feat: drop the starter prompt chips from the empty session
* feat: home and empty ai sessions share one session composer
* fix: keep session draft attachments across home and session page
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: drop superseded home ai-hidden responses
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: load home session starter lazily to keep monaco out of home
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* feat: redesign home composer and items list
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* feat: align the composer chat icon, share the folder row, add a home preview page
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* refactor: drop home tech debt, fix phone layout and keyboard access, remove the home preview page
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* feat: suggest composer prompts from workspace signals
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: pass dev page placeholders through inputProps, key settled signals by role
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* perf: read filter chip positions before hiding any in clampRows
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: scope composer signal caches to the account, drop stale workspace answers
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* chore: update ee-repo-ref to dd0c7087f9b2453260f3d73b0d589042b4393a1d
This commit updates the EE repository reference after PR #900 was merged in windmill-ee-private.
Previous ee-repo-ref: e922599943c472a6d0f736f629ae04081f866686
New ee-repo-ref: dd0c7087f9b2453260f3d73b0d589042b4393a1d
Automated by sync-ee-ref workflow.
* chore: update ee-repo-ref to dd0c7087f9b2453260f3d73b0d589042b4393a1d
This commit updates the EE repository reference after PR #900 was merged in windmill-ee-private.
Previous ee-repo-ref: e922599943c472a6d0f736f629ae04081f866686
New ee-repo-ref: dd0c7087f9b2453260f3d73b0d589042b4393a1d
Automated by sync-ee-ref workflow.
* feat: name workspace items and connections in composer pills
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* feat: teach one Windmill concept per composer pill from the workspace
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: drop the failed-deploy pill, which reports a run outcome
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: read favorites from the workspace's own item list
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* chore: regenerate mcp session guidance for the data table row
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: address cubic review of the composer signals and data table guidance
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* test: make the billing fixture's receipt step send what its summary says
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: keep loaded item kinds and drop stale loads in the composer playground
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: preview an instance admin who is a plain member in the composer playground
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: scope the enterprise note to external_instance and check receipt sends
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Diego Imbert <diego@windmill.dev>
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-authored-by: windmill-internal-app[bot] <windmill-internal-app[bot]@users.noreply.github.com>
* feat: let flow builder operators build AI agents
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: check linked agents' bound tools and type, validate on the write's transaction
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: bound the linked-agent walk by sorting bound tool ids
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: let builders bind only the agent tool inputs left to the model
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: check every agent tool sharing a bound id
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* feat: show builders the agent's own tool inputs read-only and name agents in the setting
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor: show the agent's own tool inputs with the read-only step viewer
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* style: give the agent-set inputs heading the input label style
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* style: label the agent's fixed tool inputs static inputs
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: address cubic review on agent builder rights
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: check agent writes against the role's flows capability
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* docs: name the flows capability as the agent builder right
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* fix: gate agent evals on the role's code capability
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
* refactor: move the composed-flow check into windmill-api-auth
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
* feat: manage and create folders from the home tree view
* fix: drop empty folders under a kind filter, gate manage on visibility
* fix: show the tree in a folders-only workspace, record created folder
* fix: address review nits on the home folder menu
* fix: record created folder ownership, offer folder in empty-state menu
* fix: change an app's access mode under the deploy row lock
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: defer a mode change to deploy on an app run as another user
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: hold the access toggle while its change is in flight
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* revert: leave the deploy panel's access toggle to the settings drawer PR
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: keep the caller's draft on a mode-only app update
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: refuse a builder's mode-only change on an unsandboxed app
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Guilhem LemouelandClaude Opus 5.5
hugocasaandClaude Opus 5.5
Ruben FiszelandClaude Opus 5.5
Alexander PetricandClaude Opus 4.8
