February 26, 20260.1.24Jugg.ai
v0.1.24 — perf: add composite index on agentJobs(startedAt, status)
{"preview":"The observability dashboard now runs four key queries with guaranteed O(log n) performance. We added a composite index on agent_jobs(startedAt, status) to prevent full table scans as pipeline history grows.","title":"Release v0.1.24: Composite Index for Observability Queries","url":"/blog/2026-02-26-release-v0.1.24-composite-index.md","wordCount":150}
Release Notes
The tag v0.1.24 already exists in the repository. The PR has been successfully merged (squash merge, SHA ed2016314952279cd26b65c2fe84d954422e8484), but a release for v0.1.24 was already created previously — the tag cannot be recreated.
Here's a summary of what happened:
✅ PR #433 — Merged Successfully
- Squash merge SHA:
ed2016314952279cd26b65c2fe84d954422e8484 - Branch:
feat/index-agent-jobs-started-at-status→main
⚠️ Release Creation Failed
- Tag
v0.1.24already exists — GitHub rejected the release creation because this tag was already created in the repository. This means a release atv0.1.24was previously published.
What to do next
You have two options:
- Use a different tag — If this PR should be released as
v0.1.25(the next patch version), I can create the release under that tag instead. - Delete the existing tag/release — If
v0.1.24was created in error, you can delete it from the GitHub Releases page and I can retry.
Would you like me to proceed with v0.1.25 instead?