CollabOps Q2 2026 Release Notes — 4 Major + 12 Minor
Q2's four major releases (AI Agent GA, Integration Marketplace beta, OpenShift Operator, FIPS-validated builds) + 12 minor changes summarized.
CollabOps Q2 2026 (April–June). Four major releases + 12 minor changes.
Major
1. AI Agent GA — April
After eight months of beta. → AI Agent GA
Core:
- Graph-permission integration (same model as humans)
- 5W card handoff pattern
- Four rollback strategies
2. Integration Marketplace beta — May
→ Why we didn't build a marketplace at first
Beta (verified tier only):
- 17 verified integrations (Slack, GitHub, GitLab, JIRA, PagerDuty, Datadog, Sentry, ...)
- Partner / community tiers shipping in Q3
3. OpenShift Operator — May
Accelerates OpenShift adoption. RHACM integration. SCC-compatible images. FIPS mode option.
4. FIPS-Validated builds — June
→ Engineering cost of FIPS 140-3 compliance
Qualifies CollabOps for US federal and select Korean public-sector procurement.
Minor (summary)
- Permission graph simulation — *if alice had bob's permissions*
- Audit log compression — auto-compressed past 90 days, still searchable
- CLI: --json flag added to `collab who`
- CLI: trace depth configurable for `collab why`
- API v2.4: webhook signing algorithm changed (HMAC-SHA256 → SHA512)
- Korean documentation updates — 47 pages
- Helm chart: default image pull policy IfNotPresent → Always (security)
- VM installer: boot time 4 min → 1 min (warm pool)
- Auto-generate BlogPosting JSON-LD (blog side)
- Auto-generate llms.txt
- Search engine sitemap auto-ping (IndexNow)
- Post-incident *aftermath effect* policy applies automatically — change frequency auto-throttled 50% for 7 daysQ3 priorities (preview)
- Integration Marketplace partner / community tiers
- Multi-tenant (multiple orgs per instance)
- AI Agent Korean fine-tune option
- Rancher / k0s support beyond OpenShift
Teams running CollabOps or evaluating it should start by identifying which of the four major releases touches their environment. Among the 12 minor items, several change existing behavior — the webhook signing algorithm change (HMAC-SHA256 → SHA512) and the Helm image pull policy default among them — worth an ops review.
Related posts
What Should a 100 Million Won Software Contract Change for the Customer?
The contract size a vendor wants and the reason a customer pays are two separate explanations. Working through a hypothetical ROI calculation to the end shows why counting only the hours saved per deployment falls short, and which items belong in the same table.
John Baek
The Customer Said They Hate Jira. Do They Need a New Jira?
Complaints about a familiar tool are easy to hear. But a complaint is not the same as a buying problem. What one conversation taught me about separating the friction a customer mentions from the problem their organization actually has to solve, and the four questions to ask instead.
John Baek
More Features, and a Harder Question: Why Us?
Issues, repositories, reviews, CI/CD, docs, AI. Every new feature made the product description longer, but not the reason to choose it today. So we changed the question: what decision can the customer not make right now? Why Change sits at the center of CollabOps.
John Baek