NewYour coding agent can read the release notes before it upgrades.Set up the MCP server →
Go modules
Go modules, #2023 by repository stars
Latest stable
v0.7.26
Last release 15 days ago
06 Nov 2026
Ships on a steady schedule
a new release about every 2 weeks
Nearly every release is documented
notes for 60 of the last 60 stable releases
Nothing withdrawn
no release was ever pulled
7 years old
421 releases · first in 2020
Drag across the ruler to compare, or tap a release to open it.
Nothing published for this version
Skip the presence clears of a server-side detach on a presenceless document, so a detach no longer reads every client attached to it, and load the sto
RemoveOnDetach cannot turn a detach into a removal,
by @chacha912 in https://github.com/yorkie-team/yorkie/pull/2330Your coding agent can read these notes before it upgrades. Set up the MCP server →
Mark the proto fields no SDK writes or reads as deprecated (ChangePack.min_synced_ticket, every created_at_map_by_actor, JSONElementSimple.moved_at/re…
rl_session_daily before the server. The sessions stats now read
the rollup by name. A cluster with starrocksSummaryEnabled whose
sum_session_hll_daily_ch lacks it, or is still building it, falls back to
that table's channel-day index and logs read sum_session_hll_daily_ch instead of rl_session_daily until it is queryable — correct, but slow
enough on a large project to miss the dashboard's deadline. Clusters that
followed v0.7.20 already have it. The analytics init job adds it when
missing, waits up to two minutes for the build, and logs rl_session_daily is not queryable yet instead of failing when it is not done, so a finished
job does not mean a finished build. Upgrade yorkie-analytics first, and
roll out the server once SELECT 1 FROM rl_session_daily [_SYNC_MV_] LIMIT 1 returns rather than erroring. Provisioning kept outside the chart
should wait on that read too, not on desc ... all, which lists the index
while it is still building.TextNode.removal_events, which records the
deletions and undos a piece of text has seen. The server builds snapshots
with the new rules and starts writing ledgers as soon as it runs, even from
changes sent by older clients. An older server drops the field when it
re-encodes a document, so finish the server rollout before releasing an
SDK that writes ledgers (yorkie-js-sdk#1514), keep the rollout short so
no older pod re-writes a snapshot in between, and do not roll the server
back once such clients are connected. SDKs without the ledger — earlier
JS SDK releases, iOS and Android — can still disagree with the server when
an undo meets a concurrent deletion of the same text, as they do today.GarbageLen and the GC size for the life of
the document. The server's MaxSizePerDocument gate reads only the live
size; the JS SDK's local size check counts both.Presence.Set and the presence given to WithPresence on attach now
JSON-encode their values, which is the form every other SDK reads. Callers
that already passed JSON text, such as an object or a number, must switch
to Presence.SetJSON, or the value is encoded twice. In the other
direction, the Document presence getters and presence events now return
decoded values, so code that ran json.Unmarshal on what it read must drop
that step.Presence.SetJSON for values that are already encoded by
@yorkie-team-agent[bot] in https://github.com/yorkie-team/yorkie/pull/2280deprecated
(ChangePack.min_synced_ticket, every created_at_map_by_actor,
JSONElementSimple.moved_at/removed_at and RGANode.next). Their
numbers stay declared, so the wire format is unchanged, by
@yorkie-team-agent[bot] in https://github.com/yorkie-team/yorkie/pull/2279golang.org/x/net, x/text, x/crypto, grpc, mongo-driver,
klauspost/compress and edwards25519 past their open security advisories
by @hackerwins in https://github.com/yorkie-team/yorkie/pull/2314/mcp/ is no longer served: a request to it gets
404 (a CORS preflight still gets 204), so assistants configured against it
must be removed from their client. The Admin API still serves document and
schema reads. By @hackerwins in
https://github.com/yorkie-team/yorkie/pull/2272rl_session_daily by name, so project
stats over long windows stay on one sketch per day on StarRocks 3.3.22, by
@hackerwins in https://github.com/yorkie-team/yorkie/pull/2296Add can write, and pin the
dedup hash across SDKs with a conformance fixture by
@yorkie-team-agent[bot] in https://github.com/yorkie-team/yorkie/pull/2278yorkie version server-fetch error to stderr, so
--output json stays a well-formed document by @yorkie-team-agent[bot] in
https://github.com/yorkie-team/yorkie/pull/2298Nothing published for this version
Nothing published for this version
Nothing published for this version
--backend-watch-heartbeat-interval is deprecated and ignored: it is not an off switch, even at 0s. Clients older than v0.7.25 never ask, so they never…
yorkie-secret. Set the same key, at least 32
characters, on every node with --backend-secret-key or
YORKIE_BACKEND_SECRET_KEY. A blank key, a shorter one, or yorkie-secret
stops startup; with no key at all, each process generates a random one that
other nodes reject. The yorkie-cluster chart requires
yorkie.args.secretKey or yorkie.args.secretKeyExistingSecret. Tokens
signed with the old key stop working, so every dashboard and CLI user must
log in again.yorkie-cluster chart
refuses to render without yorkie.args.clusterSecret or
yorkie.args.clusterSecretExistingSecret. When a release turns the secret
on, cluster RPCs from old pods to new ones are refused until the rollout
completes.mongodb.enabled
is true, mongodb.credentials.{databaseAdmin,userAdmin,clusterAdmin}.password
must be set, and the old published defaults are rejected. Releases that used
those defaults must replace them before upgrading.--backend-watch-heartbeat-interval-min (default 5s) and
--backend-watch-heartbeat-interval-max (default 60s; 0s turns
heartbeats off). --backend-watch-heartbeat-interval is deprecated and
ignored: it is not an off switch, even at 0s. Clients older than v0.7.25
never ask, so they never receive a heartbeat.presence-patch. An older server stores such a patch as an unspecified
presence change, and later pulls of that document fail. Roll the server out
to every node before publishing or deploying JS SDK 0.7.25, and do not roll
it back afterwards.GetProject
and ListProjects return an empty secret_key to roles below Admin.
Clients must fall back to the session token plus the x-yorkie-project
header for project-scoped AdminService calls, and proxies must pass that
header through. Owners should rotate the project keys after demoting or
removing an admin.WatchRequest.heartbeat_interval_ms, and serve heartbeats only to the
streams that asked. Watch responses gain a heartbeat, and the Go client
times out a stream that stays silent past three advertised intervals. The
server clamps the request to --backend-watch-heartbeat-interval-min /
-max and advertises the effective value. The Go client gains
WithWatchHeartbeatInterval, defaulting to 20s, with
client.NoWatchHeartbeat to opt out. By @yorkie-team-agent[bot] in
https://github.com/yorkie-team/yorkie/pull/2163 and
https://github.com/yorkie-team/yorkie/pull/2209presence-patch capability by @hackerwins in https://github.com/yorkie-team/yorkie/pull/2164Breaking for API clients. Stop returning the project's secret key to
users whose project role is below Admin. GetProject and ListProjects
answer a member with an empty secret_key; the key was the whole
credential of the project-scoped AdminService procedures, so handing it to
a member let that member act with the project owner's authority.
Those procedures now accept a second credential so members keep the reads
they are entitled to: a session token (Authorization: Bearer <token>)
together with the project named in the x-yorkie-project header. The
caller's role in that project is checked against a per-procedure minimum —
reads need Member, anything that changes documents, schemas or sessions
needs Admin.
Any client that authenticates project-scoped calls with a key read from
GetProject must fall back to the session when that key comes back empty,
or its member-role users will start seeing PermissionDenied. The Go
admin.Client does this already; the dashboard, which lives in a separate
repository, needs the same change. Proxies must also pass
x-yorkie-project through. See docs/design/admin-credentials.md.
A key copied before this change keeps working: it is a bearer credential and
nothing revokes it implicitly. Owners should run RotateProjectKeys after
demoting or removing an admin. Rotation is left to the owner because the same
key signs the event webhook and authenticates the MCP endpoint, and replacing
it cuts those off.
By @yorkie-team-agent[bot] in https://github.com/yorkie-team/yorkie/pull/2196
Stop serving the pprof /debug/pprof/cmdline endpoint. It wrote the process
arguments, disclosing any credential passed as a flag to whoever could reach
the unauthenticated profiling port. It now answers 404 Unknown profile;
every other pprof route and /metrics are unchanged. By
@yorkie-team-agent[bot] in https://github.com/yorkie-team/yorkie/pull/2200
Heartbeats are now on by default, which is safe because they are opt-in per stream: a client older than the heartbeat does not ask for one and so is never sent one.
Omit minVersionVector from a push-only PushPull reply, so no client version garbage-collects with a vector it has not pulled by @yorkie-team-agent[bot] in https://github.com/yorkie-team/yorkie/pull/2195
Hold off a refused push instead of resending it every round, and retry only the failing attachment in the Go client by @hackerwins in https://github.com/yorkie-team/yorkie/pull/2173
Skip the auto revision when only presence changed since the previous snapshot by @yorkie-team-agent[bot] in https://github.com/yorkie-team/yorkie/pull/2157
--backend-watch-heartbeat-interval / WatchHeartbeatInterval is ignored
and logs a warning at startup. Use --backend-watch-heartbeat-interval-min
/ -max; a 0s maximum turns heartbeats off.Nothing published for this version
Nothing published for this version
Expose cache hit and miss counts as Prometheus metrics by @mr8356 in https://github.com/yorkie-team/yorkie/pull/2039
Full Changelog: https://github.com/yorkie-team/yorkie/compare/v0.7.23...v0.7.24
Nothing published for this version
Precompute the daily peak sessions per channel by @hackerwins in https://github.com/yorkie-team/yorkie/pull/1997
Six fixes around one seam — what a tombstone is, and who is charged for it — plus an unrelated query optimization.
#2000, #2010 and #2012 are document-size accounting. A tree split dropped
sizes that Live was still holding, an attribute stayed charged to Live after it
stopped being the live value, and a tombstoned node's style was charged as
though it were live. Each drifts docSize away from the document it describes,
which matters wherever size is a limit rather than a statistic.
#2005 and #2009 are the collection-correctness pair. A tree split copies an
attribute tombstone, and the copy had no place of its own in GC, so it was
never collected. The heavier one is #2009: recreateFromSpan resolved a
restored node's parent by identity but never by liveness, so a parent
tombstoned since the node was purged still accepted it — a live node placed
under a tombstone, registered and reachable from nothing once the parent was
unlinked. The same PR fixes a snapshot losing a text attribute's removal flag,
where toTextNodes wrote attributes without isRemoved while toRHT always
has. The flag defaults to false on decode, so a tombstoned attribute came back
live stamped with the removal's own ticket — the newest ticket in play, which
therefore wins LWW against every older write. A replica served from a snapshot
rendered formatting a replica that replayed the changes did not, and the two
never reconciled.
#2001 makes a split report its boundary growth to undo/redo reconciliation, which previously could not see it.
#1997 is unrelated. Peak sessions per channel was setting GetProjectStats
latency against a fixed 3s deadline: the window total repeated the series'
scan, and peak was the only metric whose cost scaled with channels x days —
about 280k rows for a 3-month window on a project with ~4,900 channels, while
every other metric stayed under 0.7s. The total is now reduced in Go from the
series, and sum_session_peak_daily stores the finished daily peak as one
BIGINT per (project_id, dt), so the same window reads about 91 rows.
Operators: #1997 requires
sum_session_peak_dailyto exist and be backfilled before this version rolls out. The server's coverage probe reads every summary table in one round trip, so a cluster that lacks the table fails the probe for every project-stats metric, not just peak, wherever--starrocks-summary-enabledis on. See yorkie-team/devops#359.
The client half of this release ships in yorkie-js-sdk v0.7.23.
Nothing published for this version
Emit an object's members in a stable order when encoding by @hackerwins in https://github.com/yorkie-team/yorkie/pull/1984
Four fixes, splitting into two groups.
#1984 is the convergence-shaped one. Object members were emitted in whatever order the map yielded, so two servers encoding the same document could produce different bytes for it. Snapshots are content-addressed downstream and compared across replicas, so an ordering that varies per process makes equal documents look unequal.
#1990 corrects document-size accounting for an element removed before it
was ever registered with the root. Its size was booked but never unbooked, so
docSize drifted upward over a document's lifetime — which matters where size
is a limit rather than a statistic.
#1991 and #1993 are YSON hardening. The parser accepted malformed constructor argument lists instead of rejecting them, and the marshaller emitted object keys and strings unquoted, producing output it could not read back. Both are round-trip defects: what came out was not what would go in.
The client half of this release ships in yorkie-js-sdk v0.7.22, which carries the same #1990 and #1991 fixes plus the offline-persistence work.
Nothing published for this version
Nothing published for this version
Add the element-restore wire fields and a capability handshake, and stop generated code from drifting by @hackerwins in https://github.com/yorkie-team
Both fixes are convergence bugs rather than crashes — nothing fails loudly, the replicas simply stop agreeing — which is the argument for taking this release promptly.
#1978. Undoing an object member's removal restored it and the next
collection pass deleted it again, on every replica except the one that undid,
and on the server, which replays the change log with OpSourceReplay to build
snapshots. The key then disappeared from every snapshot built afterwards and
from every client that later loaded one.
#1980. RGA decides where an insert lands by walking forward from its anchor over the nodes currently linked into the list, tombstones included — and collection unlinks exactly those. So collection mutated the input to the insertion rule, and two replicas differing only in whether it had run ordered the same later insert differently, with nothing left to reconverge them. All three RGA-shaped structures were affected: Array, Text and Tree.
The client half of the same element-identity problem ships in yorkie-js-sdk v0.7.21.
Charts. Only yorkie-cluster moves, to 0.7.21. No commit in this window
touched build/charts/, so yorkie-analytics stays at 0.7.20 and
yorkie-monitoring at 0.7.7.
Full Changelog: https://github.com/yorkie-team/yorkie/compare/v0.7.20...v0.7.21
Add server-side offline-resumable attach (stable actor, resume, epoch) by @hackerwins in https://github.com/yorkie-team/yorkie/pull/1969
Full Changelog: https://github.com/yorkie-team/yorkie/compare/v0.7.19...v0.7.20
Nothing published for this version
Serve long-retention project-stats windows via decoupled HLL summaries by @hackerwins in https://github.com/yorkie-team/yorkie/pull/1961
Full Changelog: https://github.com/yorkie-team/yorkie/compare/v0.7.18...v0.7.19
Release candidate for validating the project-stats long-retention dual read ( #1961 ) on the public cluster. Go server only — builds yorkieteam/yorkie
Release candidate for validating the project-stats long-retention dual read (#1961) on the public cluster. Go server only — builds yorkieteam/yorkie:0.7.19-rc. Not a stable release; charts/SDKs unchanged.
Nothing published for this version
Anchor Array.Add on the last node's position identity by @lemon0333 in https://github.com/yorkie-team/yorkie/pull/1958
Full Changelog: https://github.com/yorkie-team/yorkie/compare/v0.7.17...v0.7.18
Port the JS SDK's undo/redo history layer to the Go SDK by @hackerwins in https://github.com/yorkie-team/yorkie/pull/1932
Full Changelog: https://github.com/yorkie-team/yorkie/compare/v0.7.16...v0.7.17
Keep a document loadable when two tree nodes share one ID by @hackerwins in https://github.com/yorkie-team/yorkie/pull/1927
Full Changelog: https://github.com/yorkie-team/yorkie/compare/v0.7.15...v0.7.16
Speed up GetProjectStats with approximate, concurrent reads by @raararaara in https://github.com/yorkie-team/yorkie/pull/1925
Full Changelog: https://github.com/yorkie-team/yorkie/compare/v0.7.14...v0.7.15
Identity-preserving restore for Tree undo/redo by @harrykim8672 in https://github.com/yorkie-team/yorkie/pull/1893
Full Changelog: https://github.com/yorkie-team/yorkie/compare/v0.7.13...v0.7.14
Nothing published for this version
Nothing published for this version
Identity-preserving restore for Text undo/redo (server + wire) by @harrykim8672 in https://github.com/yorkie-team/yorkie/pull/1875
Full Changelog: https://github.com/yorkie-team/yorkie/compare/v0.7.12...v0.7.13
Nothing published for this version
Nothing published for this version
Nothing published for this version
Nothing published for this version
Add disable_presence Document option for presence-free docs by @raararaara in https://github.com/yorkie-team/yorkie/pull/1841
Full Changelog: https://github.com/yorkie-team/yorkie/compare/v0.7.11...v0.7.12
Nothing published for this version
Add per-project ChannelSessionTTL with admin override by @hackerwins in https://github.com/yorkie-team/yorkie/pull/1827
Full Changelog: https://github.com/yorkie-team/yorkie/compare/v0.7.10...v0.7.11
Nothing published for this version
Support wildcard patterns in Project.AllowedOrigins by @hackerwins in https://github.com/yorkie-team/yorkie/pull/1810
Full Changelog: https://github.com/yorkie-team/yorkie/compare/v0.7.9...v0.7.10
Channel RPC consolidation + PeekChannel by @JOOHOJANG in https://github.com/yorkie-team/yorkie/pull/1805
Full Changelog: https://github.com/yorkie-team/yorkie/compare/v0.7.8...v0.7.9
Replace single LRU with sharded LRU to reduce lock conte… by @raararaara in https://github.com/yorkie-team/yorkie/pull/1783
Full Changelog: https://github.com/yorkie-team/yorkie/compare/v0.7.7...v0.7.8
Fix SplitElement computing VisibleLength with removed children by @hackerwins in https://github.com/yorkie-team/yorkie/pull/1772
Full Changelog: https://github.com/yorkie-team/yorkie/compare/v0.7.6...v0.7.7
Nothing published for this version
Update undo-redo design doc with overlapping undo analysis by @hackerwins in https://github.com/yorkie-team/yorkie/pull/1754
Full Changelog: https://github.com/yorkie-team/yorkie/compare/v0.7.5...v0.7.6
Nothing published for this version
Remove deprecated yorkie-argocd Helm chart by @hackerwins in https://github.com/yorkie-team/yorkie/pull/1748
Full Changelog: https://github.com/yorkie-team/yorkie/compare/v0.7.4...v0.7.5
Fix convergence bugs in concurrent tree merge/split by @hackerwins in https://github.com/yorkie-team/yorkie/pull/1722
Full Changelog: https://github.com/yorkie-team/yorkie/compare/v0.7.3...v0.7.4
Add StyleByPath and RemoveStyleByPath for Tree by @hackerwins in https://github.com/yorkie-team/yorkie/pull/1717
Nothing published for this version
Nothing published for this version
Add zstd snapshot compression and external body storage to prevent 16MB overflow
Nothing published for this version
Add tree-level schema support by @hackerwins in https://github.com/yorkie-team/yorkie/pull/1691
Full Changelog: https://github.com/yorkie-team/yorkie/compare/v0.7.0...v0.7.1
Fix flaky TestBatchExpiration by removing racy per-batch assertions by @hackerwins in https://github.com/yorkie-team/yorkie/pull/1688
Full Changelog: https://github.com/yorkie-team/yorkie/compare/v0.6.49...v0.7.0
Nothing published for this version
Fix inverted revision sort order in memory database by @hackerwins in https://github.com/yorkie-team/yorkie/pull/1676
Full Changelog: https://github.com/yorkie-team/yorkie/compare/v0.6.48...v0.6.49
Nothing published for this version
Deduplicate k6 test code and update k6/README.md by @ggyuchive in https://github.com/yorkie-team/yorkie/pull/1663
Full Changelog: https://github.com/yorkie-team/yorkie/compare/v0.6.47...v0.6.48
Refactor channel terminology from presence to session by @emplam27 in https://github.com/yorkie-team/yorkie/pull/1655
Full Changelog: https://github.com/yorkie-team/yorkie/compare/v0.6.46...v0.6.47
Refine shard key routing logic in Envoy Lua filter by @raararaara in https://github.com/yorkie-team/yorkie/pull/1649
Full Changelog: https://github.com/yorkie-team/yorkie/compare/v0.6.45...v0.6.46
One column per quarter.