2026 Q1

Q1 2026 — Go-OpenAPI Organization Summary

Period: December 7, 2025 — March 17, 2026 Overall effort: 674 commits across 14 repositories

1. Migration to go-openapi/testify/v2 (Organization-Wide)

Building on the testify/v2 fork introduced in the previous period, this quarter completed the organization-wide migration. All 14 repositories now use go-openapi/testify/v2 as their test framework.

Automated migration: A dedicated v1→v2 migration tool was built and used to transition existing test suites, handling import rewrites and API changes systematically.

Generics adoption: testify/v2 introduced first-class support for Go generics, with 17+ new generic assertions (IsOfType[T], SeqContains/SeqNotContains, JSONMarshalAsT, YAMLMarshalAsT, and more). Several repositories — notably swag and analysis — upgraded their test suites to leverage generics.

New safety assertions: NoGoRoutineLeak and NoFileDescriptorLeak (Linux) detect resource leaks in tests.

Additional highlights: colorized output, Kind/NotKind assertions, Hugo-based doc site, bug fixes (spew panics, uint display, map key ordering).

Releases v2.1.x → v2.4.1. The high commit count (165) largely reflects iterative stabilization of the new testing framework.

Q1 2026 — AI-Assisted Development & CI/CD

2. AI-Assisted Development Infrastructure (Organization-Wide)

All 14 repositories were equipped with instructions for AI coding agents (Claude Code, GitHub Copilot, OpenCode, Cursor, etc.):

• .claude/CLAUDE.md — project-specific overview, package layout, key API, design decisions
• .github/copilot-instructions.md — lightweight standalone version for GitHub Copilot
• AGENTS.md — vendor-neutral symlink at root
• .claude/rules/contributions.md — enforces DCO sign-off, human commit authorship, incremental linting, mandatory tests
• .claude/rules/github-workflows-conventions.md — generalized from ci-workflows to all repos

3. CI/CD Maturation and Mono-Repo Release Automation

Continuing from the previous period, the shared workflow platform matured and stabilized. The major new capability is mono-repo release automation — enabling strfmt, testify, swag, and analysis to tag and release sub-modules correctly.

ci-workflows: mono-repo variants for test/release/coverage, fuzz testing with corpus caching, remote shared git-cliff config, Trivy upgrade, cross-org workflow reuse.

gh-actions: four new composite actions (detect-go-monorepo, next-tag, bot-credentials, wait-pending-jobs). High commit counts (145/59) reflect iterative testing difficulty, not change scope.

Adopted across: analysis, jsonpointer, loads, spec, validate, swag.

Q1 2026 — strfmt, Go 1.25.0, Documentation & Quality

4. strfmt: MongoDB Driver Decoupling

Structural refactoring to remove the MongoDB driver dependency from the root module — benefiting every downstream consumer.

• internal/bsonlite — minimal BSON codec (wire-compatible with mongo-driver v2.5.0)
• enable/mongodb — blank-import package that swaps in the real mongo-driver codec
• internal/testintegration — integration tests against MongoDB, MariaDB, PostgreSQL
• Upgraded to mongo-driver v2; fixed swagger strfmt annotations
• Released v0.26.0 (decoupling) and v0.26.1 (annotation fix)

5. Go 1.25.0 Directive Bump (Organization-Wide)

All repositories updated from go 1.24.x to 1.25.0, including sub-modules. gh-actions excluded (deps already require 1.25.3).

6. Documentation, Code Quality & Community

• Discord server launched and linked across all repos
• errors: complete godoc coverage with testable examples
• jsonreference: usage examples, fuzz test for reference parser
• runtime: FAQ from resolved issues, godoc headers, denco attribution
• Coordinated relinting, SPDX license headers, broken link fixes across 8 repos

Notable bug fixes: deterministic OAIGen order (analysis), OrderedItems key escaping (spec), edge case panic guard (spec)

7. Dependency Management

Dependabot updates across all repos: testify/v2 bumps, go-openapi dependency cascades (spec→loads→analysis→validate→runtime), security updates (golang.org/x/net, x/sync, edwards25519).

Q1 2026 — Impact Assessment & Repository Highlights

Impact

• Organizational Consistency: Uniform AI agent instructions, contribution rules, CI conventions, and test framework across all 14 repos
• Test Framework: Complete migration to testify/v2 with generics — cleaner, more expressive test API
• Automation: Mono-repo release automation handles sub-module tagging correctly
• Dependency Footprint: strfmt BSON decoupling removed MongoDB driver from all downstream consumers
• Risk Level: Low — no breaking API changes; strfmt decoupling uses enable/mongodb opt-in

Repository Highlights

Q1 2026 — Summary

This period continues and consolidates the infrastructure work reported in December 2025. The three main threads are: test framework migration, CI/CD stabilization, and dependency footprint reduction.

The organization-wide migration to go-openapi/testify/v2 is now complete. All 14 repositories use the fork, and several have adopted its generics-based assertions. The automated migration tool and the addition of safety assertions (goroutine and file descriptor leak detection) make testify/v2 a meaningful upgrade over the original stretchr/testify, not just a fork.

The CI/CD platform, which underwent its initial overhaul in the previous period, matured into a stable mono-repo-aware system. The major new capability — automated mono-repo releases with correct sub-module tagging — required iterative hardening but is now operational across strfmt, testify, swag, and analysis.

The strfmt BSON decoupling removed the MongoDB driver from the transitive dependency graph of every downstream go-openapi consumer, a structural improvement with no breaking changes.

AI agent instructions were deployed across all repositories, establishing a consistent onboarding experience for both human and AI-assisted contributors. No breaking API changes were introduced during this period.