Skip to content

Releases: risense-ai/respire-releases

v1.0.9

Choose a tag to compare

@github-actions github-actions released this 04 Oct 12:34

CLI source: risense-ai/respire-cli@a617950

Verified seven-platform CLI distribution.

Respire CLI 1.0.9

Stable release.

Changes since v1.0.8.

Features

No new commands; this release focuses on migration reliability and background indexing.

Fixes

  • Migrate existing legacy Windows libraries and account credentials without decrypting discarded tombstones. Validate live records before marking migration complete; preserve original libraries and encrypted data.
  • Keep metadata listing and plaintext export independent of model loading and semantic index rebuilds.
  • Build and resume retrieval indexes in the runtime background. Report explicit index-pending state until the complete index is ready; preserve checkpoints and avoid stale artifact publication when source data changes.
  • Improve runtime diagnostics, profile-switch and legacy injection acceptance checks, and keep real email/browser release validation queued instead of canceling pending checks.

Other changes

  • Development versions now use the next unreleased patch: 1.0.8 -> 1.0.9-dev.1 -> 1.0.9 -> 1.0.10-dev.1.
  • Expand migration, native credentials, async readiness and release evidence checks without skipping existing API or browser acceptance.

Commits

Commit Change
a6179501 Wait for index readiness after reset-vault cloud recovery
c24193a7 Honor asynchronous index readiness in release acceptance
1ecbfa5a Fix migration readiness and prepare the next development cycle
f7b44e5b Merge validated legacy migration and release acceptance fixes
d656f229 Retain pending shared mailbox checks in the concurrency queue
cc929dc2 Keep synthetic tombstones within the default retention window
9d97dd83 Require exact retained-tombstone sync warning in the migration fixture
f9f2ef8f Capture fixed sync counters when native migration validation fails
8e64fc08 Verify native account migration with foreign encrypted tombstones
0806d020 Serialize the shared development mailbox across API and browser gates
72399e3b Connect the release browser gate to the existing development mailbox
cd33efe2 Keep migration usability guards without decrypting historical rows
a15da006 Group progress counter type checks without masking other violations
e1981231 Keep release smoke process results free of environment cleanup output
e1db6b51 Align missing-space diagnostics and expose progress contract failures
7395eb21 Fix legacy migration by copying encrypted libraries without content validation
6620170f Verify legacy injection migration and live runtime profile switching
322af728 Report safe doctor diagnostics when runtime release smoke fails

Full comparison

Install

npm install -g @rsrsai/cli@1.0.9
rsrs --version

Source and validation

v1.0.9-dev.1

v1.0.9-dev.1 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 04 Oct 11:29

CLI source: risense-ai/respire-cli@a617950

Verified seven-platform CLI distribution.

Respire CLI 1.0.9-dev.1

Development release for testing. The npm latest channel remains on the stable version.

Changes since v1.0.8.

Features

No separately classified changes.

Fixes

  • Validate live legacy encrypted records before completing automatic migration, while retaining unreadable discarded tombstones and original libraries.
  • Make metadata listing and plaintext export usable before semantic indexing or model initialization.
  • Rebuild retrieval indexes in the runtime background, preserve durable checkpoints, and report index-pending until the complete index is ready.
  • Back off rebuilds when source data changes and require actual index readiness before a single read-only recovery-test retry.

Other changes

  • Wait for index readiness after reset-vault cloud recovery — Keep the existing key-adoption and plaintext assertions while waiting for the owned runtime before one read-only recall retry. (a6179501)
  • Honor asynchronous index readiness in release acceptance — Wait for owned runtime readiness before retrying the read-only recall assertion, preserve failure and data checks, and back off source-change rebuild retries. (c24193a7)
  • Fix migration readiness and prepare the next development cycle — Validate live legacy payloads before completing migration while preserving deleted ciphertext. Keep list and export independent of model loading and retrieval indexing. (1ecbfa5a)
  • Merge validated legacy migration and release acceptance fixes (f7b44e5b)
  • Retain pending shared mailbox checks in the concurrency queue — Set queue max on the three release and dev mailbox fixture groups while preserving cancel-in-progress false. Concurrent required API and browser checks now wait in sequence instead of canceling an earlier pending check. (d656f229)
  • Keep synthetic tombstones within the default retention window — Use the current fixture UTC timestamp for discarded foreign rows so future migration validation does not accidentally exercise the unrelated thirty-day content purge. Production retention behavior and strict migration/sync assertions remain unchanged. (cc929dc2)
  • Require exact retained-tombstone sync warning in the migration fixture — Accept exit 2 only for the seeded foreign deleted inventory when the five-row total difference is exact, active counts match and pending, conflict and decode counters are all zero. Preserve strict zero-exit synchronization on independent devices and verify the retained tombstone bytes after the network operation. (9d97dd83)
  • Capture fixed sync counters when native migration validation fails — Retain the strict zero-exit gate and expose only allowlisted numeric or boolean convergence fields. This distinguishes foreign tombstone inventory mismatch from decryption or transport failures without logging payloads, credentials or account identifiers. (f9f2ef8f)
  • Verify native account migration with foreign encrypted tombstones — Extend the existing hosted profile fixture with five unreadable deleted foreign-account records per legacy profile. Require byte-preserving SQLite/WAL copying, original credential transfer and successful status, readback and dev synchronization while leaving current rsrs fixtures unchanged. (8e64fc08)
  • Serialize the shared development mailbox across API and browser gates — Run browser email checks after API acceptance and honor the existing recipient cooldown inside a shared job lock. Preserve strict real delivery checks and production rate limits. (0806d020)
  • Connect the release browser gate to the existing development mailbox — Check out the exact CLI mail reader alongside the pinned console and pass the existing isolated IMAP configuration. Keep real email binding and password recovery required before npm publication. (72399e3b)
  • Keep migration usability guards without decrypting historical rows — Restore read-only schema and required session-key checks before publishing a profile so unsupported or keyless copies remain retryable. Continue copying ciphertext unchanged without pre-upgrading the database or decrypting tombstones. (cd33efe2)
  • Group progress counter type checks without masking other violations — PowerShell evaluates mixed logical operators left to right. Parenthesize the counter type predicate so invalid task IDs, phases and cancellation states cannot be masked by an integer counter. Verified one valid sample and each invalid field independently before hosted acceptance. (a15da006)
  • Keep release smoke process results free of environment cleanup output — Environment.Remove returns a boolean that leaked into Invoke-Om results. Suppress it explicitly and require one process result in the existing progress contract; empty fast-operation samples remain valid while malformed samples still fail. A synthetic ProcessStartInfo check reproduced and verified the correction without running a local runtime. (e1981231)
  • Align missing-space diagnostics and expose progress contract failures — Match the current explicit missing-space refusal while retaining runtime, profile and data checks. Record only boolean results and invalid-field counts for unexplained progress failures; do not weaken release assertions or include raw user data. (e1db6b51)
  • Fix legacy migration by copying encrypted libraries without content validation — Remove per-record decryption, staging schema upgrades, and missing-session data gates so historical ciphertext cannot block startup before synchronization. Keep WAL snapshots, original data, credential transfer, and default API rewriting. (7395eb21)
  • Verify legacy injection migration and live runtime profile switching — Align the existing release smoke with the implemented legacy marker replacement and isolate doctor readiness from update notifications. Add required live account, space and config takeover checks plus reembed data and progress assertions. Full hosted artifact validation is still required before merge and publication. (6620170f)
  • Report safe doctor diagnostics when runtime release smoke fails — Record only the doctor exit code and allowlisted item names and statuses before enforcing the existing release checks. Keep inject freshness, reranker readiness and accepted exit codes strict; omit raw stdout, stderr and credential-bearing detail. (322af728)

Commits

Commit Change
a6179501 Wait for index readiness after reset-vault cloud recovery
c24193a7 Honor asynchronous index readiness in release acceptance
1ecbfa5a Fix migration readiness and prepare the next development cycle
f7b44e5b Merge validated legacy migration and release acceptance fixes
d656f229 Retain pending shared mailbox checks in the concurrency queue
cc929dc2 Keep synthetic tombstones within the default retention window
9d97dd83 Require exact retained-tombstone sync warning in the migration fixture
f9f2ef8f Capture fixed sync counters when native migration validation fails
8e64fc08 Verify native account migration with foreign encrypted tombstones
0806d020 Serialize the shared development mailbox across API and browser gates
[72399e3b](risense-ai/respire-cli@72399e3bf33ffba08979146b3e2...
Read more

v1.0.8

Choose a tag to compare

@github-actions github-actions released this 03 Oct 11:40

CLI source: risense-ai/respire-cli@166a801

Verified seven-platform CLI distribution.

v1.0.8-dev.4

v1.0.8-dev.4 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 04 Oct 11:21

CLI source: risense-ai/respire-cli@f7b44e5

Verified seven-platform CLI distribution.

v1.0.8-dev.3

v1.0.8-dev.3 Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 03 Oct 10:44

CLI source: risense-ai/respire-cli@9bbcb39

Verified seven-platform CLI distribution.

v1.0.8-dev.2

v1.0.8-dev.2 Pre-release
Pre-release

Choose a tag to compare

@luodaoyi luodaoyi released this 03 Oct 09:44

Verified CLI distribution mirrored from risense-ai/respire-cli v1.0.8-dev.2 (source 5f77c3c18389bd09ea46a53f3d15647ab8f80d06).

Respire Core SDK 1.0.0

Choose a tag to compare

@luodaoyi luodaoyi released this 02 Oct 13:44

Respire Core SDK 1.0.0 provides target-specific static libraries and C ABI 1.0 interfaces for Rust 1.95.0 consumers.

Platform Targets
Linux glibc x64, ARM64
Linux musl x64, ARM64
Windows x64, ARM64
macOS ARM64

Each target has a manifest and an archive containing the library, C header, required runtime libraries and license notices. Use the matching target, toolchain and pinned checksums. Linux glibc and musl libraries are separate builds.

Model weights are installed separately. Preserve the SDK license and third-party notices when redistributing runtime artifacts.