* feat: encrypt workspace secrets with AES-256-GCM
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* docs: note the aead gate covers workers only and is one-way
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: skip secrets the upgrade cannot store and clear its guard on panic
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: start aead secret writes one release after read support
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* chore: update ee-repo-ref to 06610ecc950ed64a2709d7f1aa8c7b49a95fdbae
This commit updates the EE repository reference after PR #869 was merged in windmill-ee-private.
Previous ee-repo-ref: 599eae0034b34c5e0d3d42df37cf18bbe01f9b49
New ee-repo-ref: 06610ecc950ed64a2709d7f1aa8c7b49a95fdbae
Automated by sync-ee-ref workflow.
* feat: widen variable.value to fit AES-GCM ciphertext of the longest legacy secret
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: refuse legacy secrets longer than 15000 chars so every secret can be upgraded
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
* fix: cap legacy secrets at 15000 chars with a check constraint so every writer is covered
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
---------
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: deploy from the UI to a workspace on another instance
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: keep the remote deploy proxy from being spent by a link
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: key remote deploy proxy URLs instead of a global client header
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: keep the remote deploy proxy key out of logs and restricted hands
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: serialize remote deploy connect with account and key changes
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* feat: key remote deploy tokens to the account and connect by signing in
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: bind remote deploy connect to its target and order its locks
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: serialize remote deploy connect with target changes
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* docs: list every lock remote deploy connect takes in auth-surface
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: never wait on the membership lock in remote deploy connect
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: keep a superseded target response out of the settings form
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: void stale remote deploy tokens on read instead of locking in connect
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: void remote deploy tokens older than the last target change
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: order remote deploy connections by when their connect started
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: bind stored remote deploy tokens to the membership and target they were connected under
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
* fix: answer remote deploy connect without settings as no target
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
Ruben FiszelandClaude Opus 5