دانلود نسخه‌های قدیمی Lore Server

Changes since v0.12.0.
Breaking changes
- lore.user.v1: UserService partition RPCs are replaced by RepositoryRegistryService; with user_url set, the directory there must serve it before lore-server is upgraded
- lore-server authorization: changing a partition needs write, changing branch protection needs owner or admin (or write for the creator), and presigned URLs need presign instead of is_service_account
- Server hooks: Hook::pre_handler is now async; a timeout fails the request with UNAVAILABLE instead of INTERNAL
- Clients on a lores:// remote refuse advertised endpoints that don't authenticate the server, such as lore://
- Ignore and view rules match paths as .gitignore does: ** and character classes stay within one path component
- .loreignore applies only to untracked paths, so changes to committed files it matches are reported and staged (ADR-00027)
- lore sync --reset and lore branch switch --reset leave untracked files in place, and lore reset no longer consults the ignore file
- A failed link push exits with its error's code instead of 255, or the new code 52 (LinkDivergent)
- File names Windows reads as something else, such as C:, file. or file::$DATA, are refused on every platform
Features
- Progress is printed every 30 seconds when stdout is not a terminal (LORE_PROGRESS_INTERVAL)
- lore auth login --reuse-session reuses a still-valid login
- The AuthUserToken event reports when the stored OIDC session expires
- [sync] prefetch_tree = true fetches a sync's tree in bulk requests
- lore-server: server.trust_unsigned_identity names callers in locks and notifications on servers without auth
- lore-server: the lock service's Query can be forwarded to a remote server (lock_query)
- lore-server: configurable QUIC initial congestion window (initial_cwnd_bytes) and, on Linux, several UDP sockets per endpoint (num_sockets)
Fixes & Improvements
- Much faster scans under large views and ignore files (157 s to 11 s for a 6,342-rule view over 450,000 files)
- Whole-directory adds and deletes in a sync run on every core, and large syncs use less memory
- Windows: fewer file system calls for antivirus and other filter drivers to inspect
- Written files take fewer stats and only change executable bits where needed
- Throttled storage copies back off and retry instead of uploading the full payload
- gRPC over TLS falls back to bundled root certificates when the OS store has none
- Sparse views: excluded directories are skipped by clone, diff and scans, and created only for content the view keeps
- Scans and staging add or delete excluded directories only along with content below them
- Directory-only rules such as Intermediate/ apply to directories only
- lore status lists and lore unstage takes back staged changes to ignored paths
- Fixed lore stage --scan taking in some ignored files under nested re-inclusions
- Fixed scans keeping untracked entries an ignore rule later excludes
- Fixed lore stage taking in every file of a new directory where only some were marked
- Merges keep both a move and an edit of the same file, and report conflicts for paths with [ or ]
- Case-only renames commit without --force
- Fixed deleted directories left behind when a file in them is spelled in another case
- Merges under a sparse view show up in diffs, file history and lore link list
- Fixed several staging, unstaging and reset problems with links and layers
- lore reset keeps nested repositories
- Fixed a failed removal on Unix making files world-writable; removals no longer follow symbolic links
- Lore service closes its SWFS mounts on exit, and on Windows a second service no longer takes over the socket
- lore repository instance prune keeps unreadable instances on file systems such as Btrfs
- Revisions named by number resolve faster, and common-ancestor lookups no longer return a too-new revision
- lore-server: faster branch push and BranchList, and the legacy BranchPush handles deleted branches as v1 does
- lore-server: replicated store req

Changes since v0.11.0.
Features
- lore service run runs the Lore service in the current process until it stops (via lore service stop or lore::service::quit); Rust only, no C API equivalent
- Expired OIDC access tokens are renewed with the refresh token (RFC 6749 §6) on the next operation, without a new lore auth login
- lore auth logout (C API: lore_auth_logout) revokes the OIDC refresh token at the provider when it advertises a revocation endpoint (RFC 7009); a failed revocation fails the logout, after the local login is removed
Fixes & Improvements
- --dry-run is now side-effect free across the CLI: no writes to the working tree, .lore config, branch/revision/staged/layer state, local or shared store, token store, settings, or the remote. Affected commands included file reset, branch create|reset|archive, revision amend, unstage, layer add, link add, repository create|clone|gc, shared-store create, file obliterate, commit, branch merge into and auth login|logout|clear
- repository clone --force --dry-run, clone --dry-run --vfs swfs and clone --dry-run --use-shared-store (when it would create the store) now fail instead of acting
- repository verify --heal --dry-run reports without healing
- Fixed a cross-process deadlock when several processes run commands on the same repository or shared store (e.g. concurrent lore history). All processes using the store must run this version
- lore repository verify fails on unreadable parts of the local store instead of skipping them, and heals fragments moved by a concurrent flush
- lore stage of several paths under a directory missing from disk stages deletes for only those paths, not the whole directory
- lore stage --case keep with a differently-cased directory stages files as modified under the repository's case, not as deleted, on case-sensitive file systems
- lore branch switch <branch> <revision> resolves a bare revision (1234, @1234) on <branch>, not the current branch
- TLS: reject certificates chained through compromised eMudhra intermediates (RUSTSEC-2026-0382) and drop the emSign ECC Root CA - G3, Root CA - C1 and ECC Root CA - C3 built-in roots
- TLS: abort on TLS 1.3 handshake messages at the wrong encryption level (RUSTSEC-2026-0285), prevent forced downgrade to classical key exchange (RUSTSEC-2026-0349), and redact secrets from client session debug output (RUSTSEC-2026-0346)

Changes since v0.8.5.
Breaking changes
- lore-client: logging CLI arguments are now strictly mutually exclusive; a command line passing conflicting logging flags is rejected instead of silently accepted
- Auth login/info now return NotSupported (code 18) when the server has no auth endpoint configured, and surface NotAuthenticated / Disconnected instead of a generic internal error (code -1); scripts branching on these exit/FFI codes must be updated
- Presigned URL vending (POST /v1/repository/{id}/content/{address}/presign) is now restricted to service accounts; normal user tokens can no longer mint presigned URLs
Features
- lore-server: forward BranchList and RepositoryCreate to a remote Lore server when configured (extending the existing BranchCreate/BranchDelete/BranchGet forwarding)
- lore: add a batch node-add verb (lore_revision_tree_add) to the low-level revision API, landing a whole subtree atomically
- lore: run the service process (lore service run) on Linux and macOS, not just Windows
- lore: validate that all strings passed to the C API are valid UTF-8, rejecting invalid input up front with a named field
- lore-server: support file:// JWKS endpoints in the JWK service
- lore-revision: optional durable_delay on the composite store so read replicas can answer before the durable tier is queried
- lore-storage: self-heal corrupt (torn-write / zero-filled) mutable store buckets instead of failing to open the store
- lore-server: add Cache-Control headers to the presigned-URL redeem endpoint for immutable content
- Add a self-contained Terraform example for an AWS primary + edge deployment under contrib/aws/
Fixes & Improvements
- lore-storage: read_into now respects the requested byte range for single-fragment reads (partial reads of files ≤ 256 KiB no longer fail)
- lore-server: fix JWK refresh cache check so a missing/rotated key triggers a fetch, allowing key rotation without a restart
- lore-credential: require a DNS label boundary when matching a dotless JWT aud, and allow exact apex-domain matches, closing an audience-suffix leak
- lore-revision: preserve dirty move status through status --scan instead of degrading it to delete + add
- lore-revision: bound commit read memory with a travelling fragment permit, and cap directory recursion fan-out during commit
- lore-revision: drain staging tasks on all error paths so failures propagate cleanly
- lore-storage: batch FastCDC chunking to cut per-chunk overhead on medium/large writes
- Add transport connect timeouts so local reads no longer stall on an unreachable remote
- lore: use the calling process's working directory for absolute-path resolution in the service process
- Fix lore_branch_switch and lore_branch_reset to restore the branch name→id mapping (so the branch appears in the local list), with a --force override
- lore-revision: fix restore failing with Dirty node remain after nodes were committed
- lore-base: update vendored rpmalloc to 2.0.1

Changes since v0.8.4.
Features
- Implement the low-level revision-tree read verbs on the C API: tree_load/tree_close, resolve_path, list_children, revision & node info, and node_path
- Forward BranchCreate, BranchDelete, and BranchGet to a remote Lore server, opt-in per-RPC under [server.grpc_public_services.forwarded_requests]
- Add repository info --local to read repository metadata from the local store without contacting the remote
Fixes & Improvements
- Fix a corrupt-tree race in concurrent node_add where a half-initialized node could be observed on the child chain
- Protect non-durable local-only fragments from being orphaned by store GC eviction/compaction
- Fix dirty-add reclassifying remaining files when committing multiple added files individually
- Parallelize staging of multiple explicit paths instead of a serialized per-path loop
- Make CLI paths relative to the current working directory across all path-printing commands
- Bump anyhow, crossbeam, and memmap2 for security advisories

Changes since v0.8.3.
Features
- Add --dry-run to revision commit and lock acquire/release
- Run incremental store GC by default; replace --gc with --no-gc to disable
- Expose the mutable store through the low-level storage C API
- Add ForwardedRevisionService gRPC endpoint to forward BranchCreate to a remote server
- Carry structured error detail and FFI codes on the Complete event
- Show staged renames as moves in diff output
- lore status prints paths relative to the current working directory
Fixes & Improvements
- Fix use-after-free in write_fragmented when the chunker future is cancelled
- Fix LoreArray<T> dealloc layout mismatch in Drop
- Fix commit --stats panic and report real fragment stats
- Fix link contents surfacing as parent adds in file diff
- Fix clone not materializing view-filtered directories with all-excluded children
- Reject malformed metadata set args instead of panicking; default branch metadata to current branch
- Reset staged add/remove/update for link nodes
- Propagate dirty to committed ancestor directories on dirty add
- Make dirty add idempotent so a repeat dirty doesn't duplicate the node
- Stage empty dirty-added directories by their own path
- Honor --dry-run on branch push
- Rename [server.replication] config to [server.grpc_internal] (not backwards-compatible)
- Map GRPC storage errors correctly and stop classifying Unknown/EOF errors as server errors
- Handle thin-client RevisionDiff/RevisionTree RPCs with a zeroed revision
- Tag linked-repo RevisionDiff changes with an indexed partition table
- Standardise HTTP tracing and log levels
- Seed QUIC clients with an initial CWND on regeneration
- Remove redundant dry_run field from lock events
- Rename shared store config file to shared_store.toml with auto-migration
- Change stats flag to u8 for C ABI consistency