Skip to content

chore: version packages - #222

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main
Open

chore: version packages#222
github-actions[bot] wants to merge 1 commit into
mainfrom
changeset-release/main

Conversation

@github-actions

@github-actions github-actions Bot commented Jul 19, 2026

Copy link
Copy Markdown

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

  • 991d75b: Replace lcm map with unified machine registration and project identity commands, preserving local SQLite hashes while adding explicit PostgreSQL UUIDv7 project pairing and reimage recovery. Add lcm postgres migrate as the supported packaged administrator workflow for provisioning the PostgreSQL schema.
  • fb81d39: Replace direct Claude Marketplace distribution with an npm-owned native Claude
    Code integration. Install or update LCM with npm, then run lcm install; the
    installer migrates recognized legacy Marketplace installations before
    registering native hooks, MCP, commands, and skills.

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.
  • 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

  • d946542: Make worktree reconciliation, project identity mutations, staged PostgreSQL admission, and cross-project import/export fail closed around one verified project snapshot.
  • 051c097: Add the staged PostgreSQL conversation, message, and ordered message-part repository with collision-safe session segments, canonical project-scoped advisory locking, atomic contiguous append allocation, nonnegative safe-integer and U+0000-free text inputs, bigint-safe part ordinals, isolation-fenced scoped transactions, serialized scoped operations, and reviewed least-privilege runtime grants.
  • ee87087: Preserve an owned daemon that may be busy when bounded health checks remain unavailable instead of signaling it and starting a replacement.
  • f0e0c66: Add the staged PostgreSQL lexical-search repository with full-text ranking, database-normalized bounded trigram eligibility, strict runtime limit validation, regex paths, exact project and filter scoping, timeout-safe transaction handling, least-privilege grants, and PostgreSQL 18 conformance evidence.
  • fa0bd2a: Document safe initial and incremental native Question issue-type rollouts.
  • 603c95b: Keep worktree reconciliation available when an unrelated stale project-map path crosses a regular file, while preserving strict filesystem validation for the requested project.
  • b60b8fd: Recognize Git-compatible inline comments on extensions.worktreeConfig when resolving submodule project identity.
  • 49957e1: Correct the lcm-context skill examples to use the supported repeatable --tag option.
  • 9ea6006: Use authenticated daemon health when doctor reports storage readiness and distinguish unavailable storage from readiness that could not be verified.
  • eb27833: Restart same-version stale daemons, safely recover the exact empty legacy SQLite instruction cache, and surface per-project compaction scan failures.
  • e6167e8: Isolate restored instruction caches by project, machine, client, session, verified worktree, and exact working directory; authenticate linked-worktree metadata bidirectionally and discard unscoped legacy instruction rows during a transactional upgrade.
  • 62dc49a: Keep PreCompact hooks best-effort when PostgreSQL credentials are unavailable, require SQLite health checks to prove rollback-safe writes, and retire pooled handles whose rollback fails.
  • 6bfc7ab: Make the staged PostgreSQL conformance harness validate its complete run identity before database mutation, require every exposed project repository adapter to register a backend-neutral contract suite, raise nested signal-probe readiness from 30 to 90 seconds with the bounded LCM_TEST_POSTGRES_SIGNAL_READY_TIMEOUT_MS override, 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.
  • 9c24fae: Accept Git config files up to 4 MiB during project identity resolution while retaining the stricter 64 KiB limit for Git topology pointers.
  • 9c43b01: Add locally scrubbed, append-only PostgreSQL native transcript ingestion with exact message provenance, resumable checkpoints, metadata-only local quarantine, and least-privilege runtime access.
  • 1332a89: Allow worktree reconciliation to preserve an identical passive-event predecessor after that predecessor has been pruned from both local event databases.
  • ff9a468: Prevent worktree reconciliation from changing passive-event predecessor identity after delivery may have reached PostgreSQL.
  • f930c8f: Add the transactional PostgreSQL 18 schema, backend-neutral project identity, bounded exact session-ID lookup, complete applied-baseline inventory verification, identity-function drift fingerprinting, scoped privilege hardening, and namespace-aware extension readiness for upcoming PostgreSQL storage adapters.
  • 025030b: Add staged PostgreSQL summary-DAG, context-item, and large-file repositories with deterministic traversal, transactional graph integrity, fenced mutation support, least-privilege grants, conformance coverage, and operator diagnostics.
  • 5ab4b25: Prevent Codex-backed compaction from rejecting otherwise valid user configuration when LCM applies reasoning-effort or fast-mode overrides.
  • 388490f: Bound doctor health checks and recover the managed daemon once when automatic post-compaction promotion loses its transport.
  • 8114f15: Add the internal verified-TLS PostgreSQL 18 pool and migration foundation plus a digest-pinned, run-isolated conformance harness for upcoming PostgreSQL storage adapters.
  • 2ecc6b4: Make the PostgreSQL development harness recover proven stale Docker resources safely and clean up local test consumers reliably after process termination.
  • 9ee092d: Reject accessor-backed and symbol-bearing promoted metadata arrays before reading their values.
  • 89c83fb: Keep public daemon health storage-free and path-free while retaining authenticated health diagnostics for lifecycle checks, clients, and doctor.
  • e7baaba: Correct lcm stats compression output to compare compacted conversations with the total conversation count.
  • 4ccf628: Harden release publication against local tarball path ambiguity and delayed npm registry propagation.
  • 0aea3d3: Honor Git's final extensions.worktreeConfig assignment and keep exact retired event fences out of sidecar health scans while surfacing malformed candidates.
  • caa0ed2: Keep MCP SDK build dependencies out of published consumer dependency paths, install and verify native Claude settings before removing Marketplace plugins, normalize legacy HTTP/SSE entries to stdio while preserving compatible options, and preview native settings changes without mutating them during dry-run.
  • 73a82cd: Replace polling external admission with event-driven evaluation and add a default-branch repository_dispatch recovery path for exact commit SHAs.
  • a909b21: Harden PostgreSQL test-process and orphan-resource teardown, and clean isolated Vitest homes at the end of each run.
  • dbbd850: Prevent private mutation-lock ownership checks from executing process-birth helpers found through an untrusted PATH or working directory.
  • e5c524c: Validate release markers and publication history with trusted default-branch policy before tagged package code is available.

Greptile Summary

This is an automated Changesets release PR bumping @donadiosolutions/lcm from 1.4.2 to 2.0.0. The version jump is driven by two breaking changes: the replacement of lcm map with unified machine registration commands and the switch from Claude Marketplace distribution to a native npm-owned Claude Code integration.

  • package.json / package-lock.json: version field updated to 2.0.0; no dependency changes.
  • CHANGELOG.md: 2.0.0 section prepended with 2 major, 7 minor, and 34 patch entries sourced directly from the consumed changeset files.
  • .changeset/*.md (43 files): all changeset descriptors deleted after being folded into the changelog by the Changesets action — exactly the expected lifecycle for this workflow.

Confidence Score: 5/5

Safe to merge — this is a purely mechanical version bump generated by the Changesets action with no production code changes.

Only three files carry meaningful edits: package.json and package-lock.json receive a version string update, and CHANGELOG.md gets the new release section prepended. All 43 changeset descriptor files are deleted as part of the normal Changesets lifecycle. There is nothing here that could alter runtime behaviour.

Files Needing Attention: No files require special attention.

Important Files Changed

Filename Overview
package.json Version bumped from 1.4.2 to 2.0.0; no dependency or script changes.
package-lock.json Lock file root version updated to 2.0.0 in sync with package.json; no dependency tree changes.
CHANGELOG.md 2.0.0 release section prepended with 2 major, 7 minor, and 34 patch entries matching consumed changeset files.
.changeset/machine-project-identities.md Major changeset file deleted after being consumed into CHANGELOG.md by the Changesets action.
.changeset/native-claude-install.md Major changeset file deleted after being consumed into CHANGELOG.md by the Changesets action.

Sequence Diagram

sequenceDiagram
    participant Dev as Developer
    participant GH as GitHub Actions
    participant CS as Changesets Action
    participant NPM as npm Registry

    Dev->>GH: "Merge feature PR with .changeset/*.md"
    GH->>CS: Trigger Changesets release action
    CS->>CS: "Consume all .changeset/*.md files"
    CS->>CS: Compute version bump (major: 2.0.0)
    CS->>GH: "Open/update version PR #222"
    Note over GH: PR updates package.json, package-lock.json, CHANGELOG.md
    Dev->>GH: "Review & merge PR #222"
    GH->>NPM: "Publish @donadiosolutions/lcm@2.0.0"
Loading

Reviews (26): Last reviewed commit: "chore: version packages" | Re-trigger Greptile

@github-actions github-actions Bot added the no-release-notes Exclude this pull request from generated release notes label Jul 19, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 29 times, most recently from 0c422d6 to 2bd28ff Compare July 25, 2026 19:51
greptile-apps[bot]
greptile-apps Bot previously approved these changes Jul 29, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 5023269 to b610533 Compare July 29, 2026 19:09
@greptile-apps
greptile-apps Bot dismissed their stale review July 29, 2026 19:10

Dismissed because a newer commit was pushed; Greptile will re-review the current head.

greptile-apps[bot]
greptile-apps Bot previously approved these changes Jul 29, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from b610533 to e04c0c0 Compare July 29, 2026 19:12
@greptile-apps
greptile-apps Bot dismissed their stale review July 29, 2026 19:12

Dismissed because a newer commit was pushed; Greptile will re-review the current head.

greptile-apps[bot]
greptile-apps Bot previously approved these changes Jul 29, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from e04c0c0 to 420d09c Compare July 29, 2026 19:25
@greptile-apps
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.

greptile-apps[bot]
greptile-apps Bot previously approved these changes Jul 29, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch 2 times, most recently from 7820bd9 to 2cdbbf9 Compare July 29, 2026 19:44
@greptile-apps
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.

greptile-apps[bot]
greptile-apps Bot previously approved these changes Jul 29, 2026
@github-actions
github-actions Bot force-pushed the changeset-release/main branch from 2cdbbf9 to 86f82aa Compare July 29, 2026 19:50
greptile-apps[bot]
greptile-apps Bot previously approved these changes Jul 29, 2026
greptile-apps[bot]
greptile-apps Bot previously approved these changes Jul 29, 2026
greptile-apps[bot]
greptile-apps Bot previously approved these changes Jul 29, 2026
greptile-apps[bot]
greptile-apps Bot previously approved these changes Jul 29, 2026
greptile-apps[bot]
greptile-apps Bot previously approved these changes Jul 29, 2026
greptile-apps[bot]
greptile-apps Bot previously approved these changes Jul 30, 2026
greptile-apps[bot]
greptile-apps Bot previously approved these changes Jul 30, 2026
greptile-apps[bot]
greptile-apps Bot previously approved these changes Jul 30, 2026
greptile-apps[bot]
greptile-apps Bot previously approved these changes Jul 30, 2026
greptile-apps[bot]
greptile-apps Bot previously approved these changes Jul 30, 2026
greptile-apps[bot]
greptile-apps Bot previously approved these changes Jul 30, 2026
greptile-apps[bot]
greptile-apps Bot previously approved these changes Jul 31, 2026
greptile-apps[bot]
greptile-apps Bot previously approved these changes Jul 31, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

no-release-notes Exclude this pull request from generated release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants