Tags

Tags give the ability to mark specific points in history as being important
  • v1.0.3

    ctxscope v1.0.3 — the README now documents the whole API
    
    The exported-surface list claimed to be complete while omitting all four
    exported types. It now matches go doc exactly, and the release script enforces
    that.
    
    Adds worked examples for the four boundaries that matter, documents the
    concurrency guarantees, and adds a table of contents. No code change.
  • v1.0.2

    ctxscope v1.0.2 — stop forcing a linter upgrade on importers
    
    The golangci-lint tool pin was v2.12.2. A tool directive is still a require and
    Go takes the maximum across the module graph, so importing ctxscope raised every
    consumer's linter and lit up findings in code they had not touched.
    
    Pinned to v2.4.0 to match ctxerrors. Importing this module can no longer move
    anyone's linter. No library code changed.
  • v1.0.1

    ctxscope v1.0.1 — doc correction: plain slog calls keep the global tier
    
    A plain slog.Info loses the per-context tier but keeps the global one, which
    never came from a context. The docs said it carried no scope at all.
    
    No behaviour change. Adds the two tests that would have caught it, including
    the first coverage of the slog.SetDefault + package-level slog.InfoContext
    setup the README recommends.
  • v1.0.0

    ctxscope v1.0.0 — log context that rides on a context.Context
    
    Attributes pinned to a context.Context land on every log line emitted under
    it. Two tiers: SetGlobal for process facts that never travel, Set for work
    facts that cross a hop via ToJSON/FromJSON.
    
    Extracted from github.com/psyb0t/common-go/scope so it can ship on its own
    schedule instead of one shared with gorm, echo, NATS and Temporal. The API is
    unchanged apart from the package name.
    
    New in this release: NewHandler, a slog.Handler that applies the context's
    scope to every record, so plain slog.InfoContext carries the attributes --
    including from code that has never heard of this package.
    
    First release of a new module path, so the sequence starts at v1.0.0.