Skip to content

v0.40.5 — No duplicate schedulers on live runs; Slack thread replies without a mention

Choose a tag to compare

@umxr umxr released this 03 Nov 13:40
· 12 commits to main since this release

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 runWorkflow on the same run id. runSimpleWorkflow now 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 subscribes message.channels and message.groups and adds the channels:history and groups:history scopes. 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.sh now builds with corepack pnpm from the repo root, and lastlight.service points at apps/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-node 2.0, croner 11, 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