What's New in Gluecron

Shippedlive from merged pull requests

Gluecron builds itself on Gluecron. Every entry below is a real merged pull request from the platform's own repository — gated by its full CI suite and deployed automatically within minutes of merging. This list updates itself; it cannot go stale.

• fix(ci): a deploy that was overtaken is not a deploy that failed

  #5606 · merged 21h ago

• fix(ci): moving checkouts to a shared volume made them leak forever

  #5605 · merged 22h ago

• fix(ci): the runner's healthcheck had the same lie as the broker's

  #5604 · merged 22h ago

• fix(ci): the broker reported healthy while unable to reach docker at all

  #5603 · merged 22h ago

• feat(ci): a container per job — jobs isolated from each other, not just the app

  #5602 · merged 22h ago

• docs(ci): the attribution guarantee promised more than the gate delivers

  #5601 · merged 22h ago

• fix(api): ?branch= silently hid nearly every workflow run

  #5600 · merged 22h ago

• fix(gate): the CI merge gate could be switched off by capitalising the repo name

  #5599 · merged 23h ago

• fix(ci): an unwritable checkout dir must not take CI down platform-wide

  #5598 · merged 23h ago

• feat(api): list every workflow run in a repo, not one workflow at a time

  #5597 · merged 23h ago

• feat(admin): show whether the AI key actually works, not just what it spent

  #5596 · merged 23h ago

• feat(ci): execute workflow steps in a sibling container, not the app

  #5595 · merged 23h ago

• fix(ci): two false greens — a job that ran nothing, and a failing line that didn't fail

  #5594 · merged 23h ago

• fix(spine): the daily journey was watched by a clock that could not see it

  #5593 · merged 1d ago

• fix(oauth): the consent screen never showed where the tokens go

  #5590 · merged 1d ago

• fix(auth): signup is closed during build-out

  #5591 · merged 1d ago

• feat(repo): the page notices when it contradicts itself

  #5588 · merged 1d ago

• fix(repo): "Updated 9d ago" on a repo nothing had touched for 19 days

  #5586 · merged 1d ago

• feat(ai): a daily ceiling, so lean spend is enforced rather than remembered

  #5584 · merged 1d ago

• feat(ai): learn the provider is down once, instead of rediscovering it everywhere

  #5582 · merged 1d ago

August 2026

• Merges wait for green

  Every push runs typecheck + the full test suite on Gluecron CI, and the merge gate refuses a PR while its branch is red or still running. Non-fast-forward merges were also fixed at the resolver level.

• The spine reaches the owner

  Synthetic journeys probe the product (sign-in, session, explore), heartbeat detection notices the platform's own outages, and red probes, error spikes, failed deploys and rollbacks now notify the owner in-app and by email.

• GitHub import brings the whole history

  Issues, pull requests and comment threads are imported alongside git objects — single-repo and bulk — with recovery for quota-interrupted runs.

• Ships with Anthropic down

  An invariant test proves every customer path works with the AI provider unreachable; AI features degrade to honest fallbacks instead of errors.

• Honest site pass

  A visible pre-launch label on every page, standards-mode HTML site-wide, a single price list shared by home and /pricing, dead links resolved, and enterprise/compliance copy rewritten to what is real today versus planned for GA.

• Access visibility

  Admins can see, and revoke, every OAuth client and token that can reach their repositories. Repository slugs resolve case-insensitively across the MCP surface.

July 2026

• Selfcheck: the platform diagnoses its own source

  Twenty-one static rules run hourly over Gluecron's code — unguarded mutations, unawaited writes, check-then-insert races, indexes weaker than the schema declares, fetches without deadlines — and surface on /admin/selfcheck.

• Production-readiness gate

  A CI gate that exits non-zero on drift between Drizzle and migrations, unguarded state-changing routes, or missing production configuration.

• Push-time policy

  Secret scanning at push, CODEOWNERS enforced at merge, and PR workflows wired to fire on open and update.

• Unified navigation and admin console

  One repo nav everywhere, grouped settings sidebar, a single admin shell, and a nav-audit tool that presses every tab on every repo to prove it renders.

• Onboarding that arrives working

  New repositories start with a README, gates and labels; bulk imports are secured and scanned; the Connect Claude page points at a first real task.

• Tokens that expire

  Personal access tokens gained a real expiration control, and the admin token flow no longer hardcodes a seven-day life.

June 2026

• AI Trio Review

  Three-model parallel PR review running Security, Correctness, and Style passes simultaneously — faster feedback, broader coverage.

• Spec-to-Live progress UI

  Watch your spec become a merged PR in real time: a live progress stream shows each agent step from spec parse to gate green to merge.

• Pack-content ruleset enforcement

  Block bad commits at push time with pack-content rulesets — enforce file-size limits, banned extensions, and content patterns before the push lands.

• Customer deploy targets

  SSH deploy to your own server directly from a merge. Register a server target in repo settings and autopilot handles the rsync.

• Workflow cache SAVE

  CI runs warm from the second run. Workflow jobs can now persist dependency caches between runs, cutting install time on hot paths by up to 80%.

• Push Watch

  A pulsing Live indicator appears in the repo header whenever a push is in flight — gate runs, AI review, and deploy status update without a page reload.

May 2026

• Branch preview URLs with auto-expiry cleanup

  Every PR branch gets an isolated preview URL. Autopilot tears down stale previews 24 hours after the branch is merged or closed.

• Dashboard AI activity widget

  A compact widget on /dashboard surfaces the last hour of autopilot actions across all your repos — repairs, reviews, deploys, and digest sends at a glance.

• Health score badge on repo header

  A colour-coded health score (0–100) appears in the repo header, computed from gate pass rate, stale PR count, and recent deploy success.