The release fixes an issue where $id was being parsed when inside examples. The index module was also heavily refactored to make it easier to read, operate, and understand, a huge cleanup of years of organic growth. Much more to come.

No breaking changes, no new features, 7% more efficient.

@luke-hagar-sp

Fixes security issues and patches issues #545

@zhirschtritt

Addresses pb33f/wiretap#143 by adding reusable local reference-resolution helpers and ensuring that nested-reference context settings are consistently propagated from document-level config into index/resolver config.

@andreyyudin

Fixes issue daveshanley/vacuum#821

Minor bugfix for vacuum and some multi-file lookup edge cases, no new features, no breaking changes.

Adds support for Arazzo

Docs https://pb33f.io/libopenapi/arazzo/

Configurable JSONPath lookup

#535

Updates JSONPath lookup in utils to be configuration-aware and safe with recent https://github.com/pb33f/jsonpath behavior, especially with respect to WithLazyContextTracking().

Different lookup scenarios need different execution behavior and safety constraints. This keeps existing behavior by default while allowing explicit control and preventing incorrect cache reuse across different JSONPath engine settings.

@andreyyudin

• Fixes #533

New CreateSchemaProxyRefWithSchema(ref string, schema *Schema) introduced

• Fix goroutine leak in schema

@1000p

• Also adds a new Release() method to Documents that cascades releasing cached objects to allow GC to collect them.

Adds a new ClearAllCaches() method to the top of the library.

// ClearAllCaches resets every global in-process cache in libopenapi.
// Call this between document lifecycles in long-running processes
// (servers, CLI tools that process many specs) to release memory that
// would otherwise accumulate and never be garbage-collected.
func ClearAllCaches() { 
...

No other new features or fixes.

Even more memory use and speed tuneups! This time, a little further down the stack. No breaking changes, no new features, just better memory use.

Memory use and performance tune-ups; no new features, but did fix some goroutine leaks and added a public cache-clearing capability, which isn't useful unless you're building long-running services.

After a couple of tune-ups, the default config is constructed properly now, and forced JSON parsing during spec load can be avoided. No breaking changes.

@its-hammer-time