v1.6.0 #65

Merged

josh merged 25 commits from dev into main 2026-03-28 21:01:27 -04:00

Conversation 0 Commits 25 Files Changed 8

+97 -16

josh commented 2026-03-28 21:01:08 -04:00

Owner

Copy Link

Copy Source

No description provided.

josh added 25 commits 2026-03-28 21:01:09 -04:00

feat: run jobs on instance creation when run_on_create is enabled ... 817fdaef13

Jobs with run_on_create=true in their config fire automatically
after a new instance is created. Runs fire-and-forget so they don't
delay the 201 response. Option exposed as a checkbox in each job's
detail panel.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Merge branch 'dev' into feat/jobs-system 883e59789b

Merge pull request 'feat: run jobs on instance creation when run_on_create is enabled' (#54) from feat/jobs-system into dev ... cec82a3347

Reviewed-on: #54

fix: queue on-create jobs sequentially and fix history ordering ... 8f35724bde

runJobsOnCreate now awaits each job before starting the next,
ensuring they don't stomp each other's DB writes in parallel.

getInstanceHistory changed to ORDER BY changed_at ASC, id ASC so
the creation event (lowest id) is always first regardless of
same-second timestamps.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Merge branch 'dev' into feat/jobs-system a5b409a348

Merge pull request 'fix: queue on-create jobs sequentially and fix history ordering' (#56) from feat/jobs-system into dev ... 64de0e432c

Reviewed-on: #56

fix: initialize jobs nav dot on every page load ... 76d2bffb4f

Previously the dot only updated when visiting the Jobs page.
Now a jobs fetch runs at bootstrap so the dot reflects status
immediately on any page, including after a hard refresh.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Merge branch 'dev' into feat/jobs-system 34af8e5a8f

Merge pull request 'fix: initialize jobs nav dot on every page load' (#57) from feat/jobs-system into dev ... 307c5cf9e8

Reviewed-on: #57

fix: millisecond precision timestamps and correct history ordering ... 7999f46ca2

datetime('now') only stores to the second, making same-second events
indistinguishable. Switched all instance_history and job_runs writes
to strftime('%Y-%m-%dT%H:%M:%f', 'now') for millisecond precision.

Reverted getInstanceHistory to ORDER BY changed_at DESC, id DESC so
newest events appear at the top and instance creation (lowest id,
earliest timestamp) is always at the bottom.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Merge branch 'dev' into feat/jobs-system d84674b0c6

Merge pull request 'fix: millisecond precision timestamps and correct history ordering' (#58) from feat/jobs-system into dev ... 03cf2aa9c6

Reviewed-on: #58

feat: auto-refresh UI after on-create jobs complete ... ddd528a682

After creating an instance, if any jobs have run_on_create enabled,
the client polls /api/jobs every 500ms until each relevant job has a
new completed run (tracked via last_run_id baseline). The dashboard
or detail page then refreshes automatically. 30s timeout as a safety
net if a job hangs.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Merge branch 'dev' into feat/jobs-system 8a9de6d72a

Merge pull request 'feat: auto-refresh UI after on-create jobs complete' (#59) from feat/jobs-system into dev ... d88b79e9f0

Reviewed-on: #59

fix: capture job baseline before POST to avoid race condition ... 1bbe743dba

The previous version snapshotted last_run_id after the 201 response,
but jobs fire immediately server-side — by the time the client fetched
/api/jobs the runs were already complete, so the baseline matched the
new state and the poll loop never detected completion.

Baseline is now captured before the creation POST so it always
reflects pre-run state regardless of job speed.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Merge pull request 'fix: capture job baseline before POST to avoid race condition' (#60) from feat/jobs-system into dev ... e2935c58c8

Reviewed-on: #60

fix: config is already a parsed object from the jobs API response ... 027ed52768

maskJob parses job.config before returning it, so calling JSON.parse
on it again threw an exception. The catch returned false for every
job, so relevant was always empty and _waitForOnCreateJobs returned
immediately without polling.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Merge branch 'dev' into feat/jobs-system 047fd0653e

Merge pull request 'fix: config is already a parsed object from the jobs API response' (#61) from feat/jobs-system into dev ... cb83d11261

Reviewed-on: #61

feat: make stats bar cells clickable to filter by state ... 2e3484b1d9

Clicking deployed/testing/degraded sets the state filter to that
value. Clicking total clears all filters. Hover style added.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Merge branch 'dev' into feat/jobs-system a9147b0198

Merge pull request 'feat: make stats bar cells clickable to filter by state' (#62) from feat/jobs-system into dev ... 518ed42f60

Reviewed-on: #62

chore: bump to version 1.6.0 5ca0b648ca

Merge pull request 'chore: bump to version 1.6.0' (#64) from chore/bump-v1.6.0 into dev ... a8d367b4be

Reviewed-on: #64

josh scheduled this pull request to auto merge when all checks succeed 2026-03-28 21:01:14 -04:00

josh merged commit edf6f674b3 into main 2026-03-28 21:01:27 -04:00

josh referenced this issue from a commit 2026-03-28 21:01:28 -04:00

Merge pull request 'v1.6.0' (#65) from dev into main

Sign in to join this conversation.

Reviewers

No Reviewers

Labels

No items

No Label

Milestone

No items

No Milestone

Projects

Clear projects

No project

Assignees

Clear assignees

josh (Josh Wright)

No Assignees

1 Participants

Notifications

Subscribe

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: josh/Catalyst#65