eric/narratio
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 18 Wiki Activity

18 Releases 21 Tags

RSS Feed
  • v1.6.0 545aa6893b
    Compare

    Narratio v1.6.0
    All checks were successful
    ci/woodpecker/push/verify Pipeline was successful
    Details
    ci/woodpecker/tag/release Pipeline was successful
    Details
    Stable

    eric released this 2026-08-30 20:40:04 +00:00 | 0 commits to main since this release

    Narratio v1.6.0

    Narratio v1.6.0 makes large pipeline configurations easier to organize,
    inspect, and vary while adding character-oriented artifact generation and a
    guarded, reproducible release procedure.

    Summary

    Pipeline configuration can now be assembled from explicit additive imports and
    a selected production or testing profile. Campaigns can own a canonical,
    versioned party roster, and Scriptorium artifact families can expand one
    definition into concrete per-character artifacts, dependencies, variables, and
    publish rules.

    New read-only configuration commands expose the fully resolved pipeline,
    source provenance, semantic digest, and profile differences before a session is
    run. Stage reuse now records configuration-sensitive semantic evidence so
    profile or configuration changes cannot silently reuse incompatible work.

    Compatibility

    This is a backward-compatible feature release. Existing monolithic pipeline
    files, concrete Scriptorium artifacts, publish rules, and configurations
    without profiles remain supported. When profiles are declared and no explicit
    profile is selected, Narratio uses the configured production default.

    An unversioned party file plus a separate players file remains available as an
    isolated legacy compatibility path, but it cannot drive artifact families. New
    campaigns and new party-oriented features should use the narratio.party.v1
    schema. Existing manifests remain readable; missing legacy semantic evidence
    is treated as stale rather than trusted.

    Narratio continues to consume the documented Notarius D&D pipeline contract.
    The release workflow still cross-compiles Linux, macOS, and Windows binaries
    for amd64 and arm64; cross-compilation is not native runtime evidence for
    macOS or Windows.

    Upgrade

    No special action is required for existing monolithic configurations that do
    not adopt profiles or artifact families. On the first run after upgrading,
    stages recorded by older manifests may regenerate once because those records do
    not contain the new semantic configuration evidence.

    To adopt the new configuration model, use the maintained
    examples/production-testing bundle as a migration reference: split stable
    settings into explicit imports, define a production default and optional
    testing profile, convert campaign party data to narratio.party.v1, remove the
    separate players file, and then introduce character artifact families. Review
    the result with narratio config validate, config show, config sources, and
    config diff before running a session.

    Campaign, session, previous-session, and run identifiers must satisfy the
    documented portable identity grammar. Existing manifests or remote state with
    unsafe legacy identifiers must be migrated before use.

    Changes

    • Added root-owned, non-recursive additive pipeline imports with strict,
      source-aware conflict detection.
    • Added named pipeline profiles with an explicit production default and
      deliberate command-line selection.
    • Added config validate, config show, config sources, and config diff
      for read-only inspection of resolved configuration and provenance.
    • Added the strict narratio.party.v1 campaign roster, including stable
      character IDs, player and character names, optional aliases, and classes.
    • Added deterministic players derivation and canonical party delivery to
      downstream integrations.
    • Added character-oriented artifact families, corresponding member
      dependencies, family selection, and generated publish policies.
    • Added semantic configuration fingerprints and stage-specific resume checks
      across transcript and artifact stages.
    • Added shared release candidate, asset build, and guarded tag-publication
      scripts, with tag-triggered publication remaining asynchronous.
    Downloads