chore: version packages - #222
Open
github-actions[bot] wants to merge 1 commit into
Open
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
29 times, most recently
from
July 25, 2026 19:51
0c422d6 to
2bd28ff
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 29, 2026 19:25
e04c0c0 to
420d09c
Compare
greptile-apps
Bot
dismissed
their stale review
July 29, 2026 19:25
Dismissed because a newer commit was pushed; Greptile will re-review the current head.
github-actions
Bot
force-pushed
the
changeset-release/main
branch
2 times, most recently
from
July 29, 2026 19:44
7820bd9 to
2cdbbf9
Compare
greptile-apps
Bot
dismissed
their stale review
July 29, 2026 19:44
Dismissed because a newer commit was pushed; Greptile will re-review the current head.
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
July 29, 2026 19:50
2cdbbf9 to
86f82aa
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@donadiosolutions/lcm@2.0.0
Major Changes
lcm mapwith unified machine registration and project identity commands, preserving local SQLite hashes while adding explicit PostgreSQL UUIDv7 project pairing and reimage recovery. Addlcm postgres migrateas the supported packaged administrator workflow for provisioning the PostgreSQL schema.Code integration. Install or update LCM with npm, then run
lcm install; theinstaller migrates recognized legacy Marketplace installations before
registering native hooks, MCP, commands, and skills.
Node.js 22.12.0 or newer.
Minor Changes
631481b: Extend automated issue triage to identify, link, and close high-confidence duplicate bug reports.
2f4e59f: Support Changesets beta releases with Codex-generated, pull-request-linked draft GitHub notes and publish npm only after a maintainer publishes the draft.
9b3f706: Add durable, versioned local passive-event envelopes; staged PostgreSQL inbox delivery, fenced completion, retry, quarantine, exact replay, and crash-safe acknowledgement/pruning; and operator status, validation, quarantine-inspection, and replay commands while keeping hooks fully local and offline.
842104b: Launch managed systemd and launchd daemons through a bounded clean environment so ambient manager variables cannot override staged credentials. Consume authenticated launchd credential files once and retain their immutable in-memory startup snapshot for in-process configuration reloads.
90a10e4: Manage daemon recovery through the current user's systemd or launchd service
manager, recreate normally idle services on demand, preserve the tri-state
no-response boundary, and provide canonical doctor, restart, and connector
repair guidance instead of offline process recovery.
Foreground or detached compatibility daemons are not eligible for automatic offline force recovery: if they stop returning HTTP responses,
lcm daemon restartrefuses and gives operator/manual recovery guidance instead of signaling or replacing the process.87d5179: Add secure SQLite/PostgreSQL backend selection and PostgreSQL connection configuration, while retaining SQLite as the zero-configuration default.
da03d2d: Add staged PostgreSQL promoted-memory, recall, redaction-administration, and session-coordination repositories with SQLite metadata parity, atomic scoped purge, least-privilege grants, and shared conformance coverage.
e2b4b63: Add staged PostgreSQL cross-machine transaction locks, fenced leases, final-write validation, fair passive-inbox claims, bounded cleanup, diagnostics, and least-privilege runtime grants.
5ab4b25: Unify linked Git worktrees under one local project, transactionally preserve and merge legacy worktree memory, and conservatively reconcile Codex transcripts from deleted managed worktrees.
Patch Changes
established LF or CRLF style in normal rules append-mode installs and avoiding
extra blank lines in generated
SKILL.mdfiles. Rules installs heal recognizedduplicate current or legacy managed blocks, including the maximal union of
overlapping or touching recognized ranges, and recover the narrowly recognized
header-only partial region consisting of a current marker followed only by
exact
# Workflow Instructionlines. Arbitrary ambiguous or malformedunmatched marker/header combinations remain preserved conservatively and may
require a second reinstall to become byte-stable; user-authored Markdown,
including heading lines, outside recognized regions is not removed. Removing a
rules connector preserves spaces, tabs, form-feed, and other non-CR/LF user
Markdown bytes with exactly one established terminal EOL, while blank-line-only
content is deleted.
extensions.worktreeConfigwhen resolving submodule project identity.functions.execandfunctions.exec_commandPostToolUse events, and validate the installed Codexhook with structural and no-write functional connector checks.
lcm-contextskill examples to use the supported repeatable--tagoption.has disappeared so the flow no longer creates spurious project-map entries for
never-seen paths, repairs private-directory permissions on existing sidecars,
and fails closed on malformed or inconsistent persisted parking state during
both runtime observation and worktree reconciliation.
LCM_TEST_POSTGRES_SIGNAL_READY_TIMEOUT_MSoverride, register signal runs before readiness, exhaustively audit every registered run and Docker resource class, converge transient whole-run cleanup failures before signal exit, retain bounded sanitized cleanup diagnostics, remove verified private directories after orphan reclamation, fail signal tests when Docker cleanup does not complete, and tolerate an exactly owned Docker resource disappearing during concurrent orphan recovery.processed_at: unprocessed events, history, and delivery state remain intact, repeated absent sweeps return a quiet terminal state, and a later cwd recovery clears the state and promotes the preserved backlog normally.lcm statscompression output to compare compacted conversations with the total conversation count.local state-root establishment, staged PostgreSQL privilege posture, and
fail-closed operator behavior.
lcm doctorwhile preserving fail-closed lifecycle refusals and reporting the repaired restart.release when an exact failed draft workflow for the same signed tag and commit
completed before publication, while preserving all tag, ancestry, history,
artifact, and npm ordering checks.
extensions.worktreeConfigassignment and keep exact retired event fences out of sidecar health scans while surfacing malformed candidates.repository_dispatchrecovery path for exact commit SHAs.PATHor working directory.