v1.0.2 GA — 2026-07-16
RepoWrangler v1.0.2 is the current generally available release and the patch operators should install. The v1.0.0 and v1.0.1 tags remain immutable historical release records; their same-day deployment-recipe corrections are included here.
| Artifact | Identity |
|---|---|
| Git tag | v1.0.2 |
| Source commit | bc4047f9c45d142ee06f41ce84ad113e3fbdeee2 |
| Server image tag | repo-wrangler-server:v1.0.2 (build from the release tag) |
GA scope
- Secure first boot, provider-aware sign-in and sign-out, immediate invalidation of sessions issued by disabled providers, and build-derived version reporting.
- GitHub and GitLab read-only estate discovery, branch/change intelligence, pipelines, security and budget capability reporting, onboarding, and estate growth workflows.
- Cloudflare Worker/D1 and Node container hosts with SQLite or PostgreSQL, plus documented Docker, Azure Container Apps, Kubernetes, and decoupled SPA recipes.
- Clean dependency audit, type checking, production build, and 189 automated tests across 33 test files.
B11 — enrichment backlog fixed
Discovery was successful, but the scheduler processed only three queued jobs every fifteen minutes. A large discovery could therefore leave repository branches, pipelines, and merge requests pending for hours without recording an error. The scheduler now runs every five minutes and drains up to ten inexpensive jobs per invocation while retaining its provider subrequest limit.
Production verification cleared all 13 pending GitLab enrichment jobs, completed 19 enrichment jobs in ten minutes, and left zero failed jobs. All 26 discovered GitLab repositories were enriched; 25 reported branches and the remaining profile repository was empty upstream.
Azure Container Apps corrections
- v1.0.1 wired
SECRET_ENCRYPTION_KEYfrom Key Vault and added the explicit single-replica scheduler switch. - v1.0.2 emits the scheduler value in the lowercase form the application expects, preserves an existing managed custom-domain binding during template updates, and keeps the PowerShell and bash deployment helpers aligned with Bicep.
Upgrade and rollback
v1.0.2 has no database migration relative to v0.6.10. Back up the database, record the current deployment identity, and deploy the immutable v1.0.2 tag. Follow the upgrade and rollback runbook; do not build a production deployment from a moving branch.
Support is best effort and latest-patch only.