stroblmeandClaude Opus 5 95be9bc092 Pin that a per-flow publish deploys the source it just published ...

The worst thing moving publish off the whole-pipeline rebuild could do
is quietly keep running the old code, and nothing was watching for it.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01StpRc2C6au1WJ1EUU7fsfu

2026-08-23 19:09:02 +02:00

..

connector-wheels

Record the connectors and what is still read-only

2026-08-16 10:00:10 +02:00

fluksio

Say a rebuild has two scopes, and close the notepad items it fixes

2026-08-23 19:05:23 +02:00

scripts

Keep the engine's state in SQLite, not Postgres

2026-08-21 22:19:45 +02:00

tests

Pin that a per-flow publish deploys the source it just published

2026-08-23 19:09:02 +02:00

.dockerignore

Rename the import package app to fluksio

2026-08-21 21:48:05 +02:00

.gitignore

Rename the import package app to fluksio

2026-08-21 21:48:05 +02:00

alembic.ini

Rename the import package app to fluksio

2026-08-21 21:48:05 +02:00

Dockerfile

Split the worker into a distribution of its own

2026-08-21 21:54:10 +02:00

pyproject.toml

Add the fluksio CLI: serve, enroll, worker

2026-08-21 22:51:13 +02:00