Repository navigation
The latest release of Lore, Epic Games' next-generation open source version control system.
Quickstart | Design | Documentation | Discord
Quick Install
Windows
irm https://raw.githubusercontent.com/EpicGames/lore/main/scripts/install.ps1 | iex
macOS / Linux
curl -fsSL https://raw.githubusercontent.com/EpicGames/lore/main/scripts/install.sh | bash
Release Notes
Changes since v0.13.0.
Breaking changes
- Branch metadata keys
archived,restored,restoringandreleasedare reserved for archives and restores; remove or rename values stored under them before upgrading - An invalid
LORE_AUTH_STORE, or a user-levelconfig.tomlthat can't be read or parsed, stops every command. Commands relayed to the service withoutLORE_AUTH_STOREuse the secure store - The Lore service and its clients must come from the same build; end a running service after upgrading
- Requests the server or authentication service refuses fail with
NotAuthenticated(16) orNotAuthorized(17) instead of an internal error (255),NotConnected(29) or a not-found code lore branch createwith an invalid name and a refusedlore repository instance moveexit withInvalidArguments(3);lore clone --root-filewith a missing file exits with 82- C API: push events start with their
repositoryandbranch, and the instance-delete begin event dropsdry_run. Rebuild against the newlore.h - Switching, resetting or pushing to an archived branch leaves it archived;
lore pushrestores it, other clients restore it with a branch create - Mutable store plugins must remove a key swapped to zero and refuse a swap from a non-zero value on an absent key
lore-server: aremoteimmutable store trusts its upstream and checks only payload sizes (verify = truerestores full checks)lore-server: QUIC storage request failures log under thelore_server::quictarget
Features
- Virtual clones on Linux with
lore clone --vfs fuse, served from the shared store and supporting status, stage, commit, sync, reset and merge.--vfs defaultnow picks FUSE on Linux lore clone --vfs fuse --prefetch <file>warms the store from an access recording (LORE_FUSE_RECORD_DIR)lore repository instance clonecopies an instance on a shared store, sharing data blocks on APFS, Btrfs, XFS, ReFS and Dev Drive[auth]in the user-levelconfig.tomlchooses the token store (store,path)- Per-instance ignore rules in
.lore/ignore --fast-flushwrites the local store's index in place, which is faster on Windows[store] cache_payloadssets whether fetched and written content is kept in the store- The Lore service closes remote connections idle for 5 minutes (
idle_connection_timeout) lore-unix://remotes reach a machine server through a Unix socket (LORE_UDS_SOCKET), whichlore-serverserves to containers with[server.uds]lore-server:client_credentials_scopesfor OIDC providers, requested bylore auth login --client-idlore-server: round-robin read replica selection for composite stores (read_replica_selection)lore-server: HTTP range requests on the content and presigned endpointslore-server:ThinClientService.RevisionTreecan attribute entries to the revision that last changed themlore-server:server.upstream_connectionssets the connections to aremotestore's upstream (default 4)
Fixes & Improvements
lore pushpushes branches, layers and links up to 8 at a time, and each linked branch only once- Faster lookup of the revision shared with the remote, without endless loops or wrong merge bases
- Fixed concurrent branch creates, restores, archives and metadata edits undoing each other
- Merges, cherry-picks, reverts and syncs handle case-only renames on both sides
- Fixed
lore file dirty,lore file dirty moveandlore stage movelosing moves or dropping files from a commit - Fixed forced stages, unstages and merges under a sparse view corrupting or losing changes
- Replacing a file with a folder, or the reverse, reports a merge conflict instead of failing with
Not a directory - Fixed several merge, resolve, reset and obliterate problems inside links
- Instances on a shared store keep their file times in
.lore/records/, so they no longer rewrite each other's - Commands that change the user-level
config.tomlkeep settings they don't know - Fixed content missing from the local store after concurrent reads or eviction, and commits failing with "leader upload failed"
- C API revision-tree handles are safe under concurrent deletes and moves
- SWFS: release builds need no dynamic C runtime, and files a sync brings back are no longer missing
lore-server: fixedlore push --fast-forward-mergestoring revisions with mismatched directory hasheslore-server: DynamoDB compare-and-swap fixes for zero values and refused swapslore-server: the replicated immutable store spreads requests over several connections (num_clients)lore-server: fixedRevisionDiffandRevisionTreeresults around links and mergeslore-server: accepts partition-scoped tokens from a separatetoken_exchange_issuer
Release Assets
Important
These can be downloaded under the "Assets" section below.
Installer
lore-setup- Lore CLI Windows installer
Binaries
lore- Lore CLIloreserver- Lore Serverliblore- Lore Shared Library
Headers
lore.h- Single header forliblore(packaged withliblore)
Supported Platforms
- Windows x86_64
- macOS AArch64
- Linux x86_64
- Linux AArch64
- Linux AArch64, optimized for Graviton/Neoverse 512-tvb
Lore Desktop Client
Important
Lore Desktop Client is available as binaries only, download the installer for your platform here:
- Windows: Lore-Desktop-Setup-x64.exe
- macOS: Lore-Desktop-arm64.dmg
- Linux (Ubuntu 24.04): lore-desktop_amd64.deb
- Linux (AppImage): Lore-Desktop-x86_64.AppImage