Skip to content

Releases: soft9tech/s9terpsync

v0.2.0

Choose a tag to compare

@github-actions github-actions released this 10 Aug 14:59

Structured, level-configurable logging across the whole pipeline — the CLI, the service, and every stage in between (intake, matching, target publication, retention, replay) now emit JSON logs, one object per line, on stdout, with run-scoped context and secret/PII redaction built in from the start.

Added

  • Structured logging across the CLI and the service: JSON logs, one object per line, on stdout, with run-scoped context and secret/PII redaction.
  • LOG_LEVEL environment variable (fatal, error, warn, info, debug, trace, silent; case-insensitive, defaults to info) controlling log verbosity, documented in the README and the wiki.

v0.1.8

Choose a tag to compare

@github-actions github-actions released this 06 Aug 04:29

Moves the "How it works" pipeline diagram out of the README and onto the wiki's Home page, alongside the data-flow diagram it already carries — the README now leads straight from Quick start into how data moves from Slate to Banner.

Changed

  • Relocated the "How it works" pipeline diagram from README.md to the wiki's Home.md.

v0.1.7

Choose a tag to compare

@github-actions github-actions released this 05 Aug 15:55

Real documentation: a comprehensive GitHub Wiki (nine pages covering installation, Ethos/Banner prerequisites, configuration, running, service operation, retention/replay, diagnostics, and architecture) plus a real README, both synced automatically from GitLab. Adds a Slate-to-Banner-via-Ethos data flow diagram and core-entities table to the README and the wiki's Home page, grounded in the real stage-dependency registry.

Added

  • GitLab → GitHub wiki sync: a second, independent push step in the mirror pipeline publishing docs/GitHub-Wiki/*.md to the project's GitHub wiki on release.
  • Nine GitHub Wiki pages and real docs/GitHub/README.md content, verified against the actual CLI, config schema, and stage registry.
  • A Slate → Ethos → Banner data-flow diagram and core-entities table on the README and wiki Home page.

Fixed

  • Root README.md no longer shows internal development history on GitLab's own repo page; it now matches the clean public content. The project's internal "agent readiness" consistency checks that previously depended on README.md's content were relocated to .ai-context/index.md / .ai-context/architecture.md, which already carried the same facts.

v0.1.6

Choose a tag to compare

@github-actions github-actions released this 04 Aug 07:11

v0.1.5 proved the tag-webhook fix works, but also surfaced that GitHub delivers push events for the mirrored tag at-least-once - it fired release.yml twice for the same commit, and the second run's npm publish failed as a duplicate. This release validates the fix for that: npm publish now skips cleanly when the version is already published, so a duplicate trigger is a clean no-op instead of a failing run.

Fixed

  • Nothing code-level beyond what v0.1.5 already validated; re-publishes to confirm the idempotent npm publish guard keeps a duplicate release.yml trigger from showing as a failure.

v0.1.5

Choose a tag to compare

@github-actions github-actions released this 04 Aug 06:46

GitHub only fires one push webhook when a single git push updates multiple refs together, so release.yml (tag-triggered) never ran through the normal mirror pipeline even though the release commit and tag were published correctly - every release so far had needed a manual, one-off GitHub API workaround to actually trigger the release workflow and npm publish. This release exists to prove the fix works end-to-end with zero manual intervention.

Fixed

  • The GitLab mirror pipeline now re-publishes the release tag as its own single-ref push right after the atomic branch+tag push, so GitHub reliably fires release.yml on every release.

v0.1.4

Choose a tag to compare

@github-actions github-actions released this 03 Aug 03:54

The 0.1.3 npm publish was a manual, one-time bootstrap run directly from the internal GitLab working directory (needed because npm requires a package's first version to exist before its Trusted Publisher settings page is reachable). That bypassed the mirror pipeline's docs/GitHub/README.md → README.md rename, so the tarball — and the npm package page — carried the internal, development-tracking README.md instead of the public one. This release carries no functional change; it exists to publish through the normal mirror → GitHub Actions → npm path so the correct public README ships.

Fixed

  • Nothing code-level; re-publishes with the correctly mirrored public README.md.