Repository navigation
v0.40.5 — No duplicate schedulers on live runs; Slack thread replies without a mention
Highlights
- A duplicate trigger no longer starts a second scheduler on a live run (#489, refs #488). A trigger that arrived again while its run was still executing in the same process started a second
runWorkflowon the same run id.runSimpleWorkflownow marks the run live before its row exists and holds it until it returns, so a repeat trigger on a live run does nothing. - Slack answers replies in its own channel threads without an
@mention(#456). Before this release, each turn in a channel thread needed an@mention. DMs already worked. The Slack manifest now subscribesmessage.channelsandmessage.groupsand adds thechannels:historyandgroups:historyscopes. The connector resolves the bot's user id on connect, so a mention is answered once, not twice. To get this, update your Slack app with the new manifest (apps/server/deploy/slack/slack-manifest.json) and reinstall it. - The review summary names a human's open change request (#459). A clean pass after a human's CHANGES_REQUESTED review posted "Looks good — no issues to raise.", which read as overruling the request. The summary now says the requested changes are still open, and never says "Good to merge" while they are.
- The native (systemd) install works with the pnpm workspace again (#487).
deploy/native/install.shnow builds with corepack pnpm from the repo root, andlastlight.servicepoints atapps/server/dist/index.js. The Node check now requires 22.12 or later. - Dependency updates (#462, #463–#468, #477, #478, #481–#484): OpenTelemetry 3.0,
@kubernetes/client-node2.0,croner11, plus the production and development dependency groups. Dependabot now updates npm from the workspace root only (#479).
Packages
lastlight / lastlight-core 0.40.5, lastlight-evals 0.20.5.
Full changelog: v0.40.4...v0.40.5