Repository navigation
Release NativeLink v1.8.0 - #2979
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HBxQtV9S561AzBo7aPCYFj
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Member
Author
|
/build-image nativelink |
Member
Author
|
/build-image nativelink-worker-init |
Contributor
|
Image built and pushed! |
Contributor
|
Image built and pushed! |
MarcusSorealheis
marked this pull request as draft
October 20, 2026 18:15
MarcusSorealheis
marked this pull request as ready for review
October 20, 2026 23:24
Regenerate the v1.8.0 section with git cliff after merging main, and pin TraceMachina#2993 to Bug Fixes by subject, since the generic rules file it under Miscellaneous. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Add TraceMachina#2995 after merging main, and skip the release branch's own changelog commits, which the generic "Add" rule filed under Features. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
corcillo
reviewed
Oct 21, 2026
|
|
||
| - Bound object store reads with an adaptive permit pool, Azure first ([#2941](https://github.com/TraceMachina/nativelink/issues/2941)) - ([3e3237c](https://github.com/TraceMachina/nativelink/commit/3e3237cd8371e56f1d62ca65b1cbc8b6a75fa758)) | ||
| - add option to mount cached input directories as read-only ([#2751](https://github.com/TraceMachina/nativelink/issues/2751)) - ([786c2c2](https://github.com/TraceMachina/nativelink/commit/786c2c2f0da02711e2b632ab0a19524a2a953f9d)) | ||
| - Bound a worker's input fetches with one pool across the actions it stages ([#2952](https://github.com/TraceMachina/nativelink/issues/2952)) - ([23b4472](https://github.com/TraceMachina/nativelink/commit/23b4472a09ea1467708e5980b8ae846a9542625f)) |
Collaborator
There was a problem hiding this comment.
This makes the shared pool of 64 input fetches the default, but #2984 is open to make it opt-in again in 1.8.1. A worker that's staging several cold actions is slower than on v1.7.7. Shipping a new default in a minor release and reverting it in the next patch gives operators two behavior changes back to back. Could we decide before tagging? Either merge #2984 now, so 1.8.0 keeps v1.7.7's behavior and the "New worker default" Risk bullet comes out, or keep 64 and close or rework #2984.
corcillo
reviewed
Oct 21, 2026
Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Regenerate the v1.8.0 section after merging main, and pin TraceMachina#2984 to Bug Fixes by subject, since the generic rules file it under Miscellaneous. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
corcillo
approved these changes
Oct 21, 2026
amankrx
approved these changes
Oct 21, 2026
This branch was successfully deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What and why
Cuts v1.8.0, following "Creating releases" in CONTRIBUTING.md. There are 38 commits since v1.7.7. This is a minor bump rather than a patch because the release adds backward-compatible features: new opt-in configuration fields and new metrics. Nothing is removed or renamed. Every new field defaults to the existing behavior.
experimental_readonly_input_mounts(worker: add option to mount cached input directories as read-only #2751). An opt-in pool of input fetches shared by every action a worker stages,max_concurrent_input_downloads, off by default (Bound a worker's input fetches with one pool across the actions it stages #2952, Restore per-action input fetches as the worker default and suggest a shared pool under load #2984). A worker without it logs a warning suggesting it when input fetches fail with transient store errors or time out. An adaptive bound on object store reads,max_concurrent_reads/adaptive_read_concurrency/min_concurrent_reads, off by default (Bound object store reads with an adaptive permit pool, Azure first #2941). Opt-in repair removal throughCacheMetricsStore,allow_remove, default false (Forward cache removal through CacheMetricsStore #2968).worker.input_mount.{cache_hits,cache_misses,fallbacks,prepare_failures},store.object.read_limitandstore.object.read_waits.Unavailable(Return Unavailable when resuming an active ByteStream upload #2889). Every upload is written through the existence cache (Write every upload through the existence cache instead of discarding one it believes present #2951).has()batch no longer cascades evictions (EvictingMap: a batch size/existence query must not cascade-evict every resident entry #2840). Redis subscription gaps that dropped events are closed (Redis: don't silently lose pubsub subscriptions on reconnect or a transient init error #2839). An empty Azure object or Redis value under a non-empty digest is reported as missing, and an Azure read with no length returns the whole object (Report empty Azure and Redis objects under a non-empty digest as missing and stop cutting unbounded Azure reads #2993).Unknownmaps to retryableUnavailable(Map transport-originated Unknown to retryable Unavailable #2816). Throttle waits grow and jitter (Grow and jitter consecutive throttle waits in the retrier #2939). Remote-execution scheduling edge cases and output flush are handled (fix(remote-exec): handle scheduling edge cases and output flush (#1533) #2963).#2881 and its revert #2953 cancel out, so neither appears in the changelog.
How was this verified?
mainat f66c65c and has since mergedmainthrough 2a3ad61 (Restore per-action input fetches as the worker default and suggest a shared pool under load #2984).git describeconfirms v1.7.7 is the latest tag on that history.git diff v1.7.7 origin/mainovernativelink-config/srcandnativelink-util/src/metrics.rsshows only additions, apart from one doc-comment formatting change inschedulers.rs. That still holds after the later merges: Restore per-action input fetches as the worker default and suggest a shared pool under load #2984 changes only the doc comment and default ofmax_concurrent_input_downloads, a field that is itself new since v1.7.7. No commit in the range is marked breaking.MODULE.bazel, the rootCargo.tomland all 13 crate manifests, includingnativelink-metric-macro-derive. NoCargo.tomlorMODULE.bazelstill says 1.7.7.cargo update --workspace --offline. The only changes are the 18nativelink-*version entries (13 inCargo.lock, 5 in the fuzz lock).cargo metadata --offline --lockedpasses in both workspaces.CHANGELOG.mdwas prepended withgit cliff --unreleased --tag=v1.8.0 --prepend CHANGELOG.md(git-cliff 2.13.1 from the Nix shell), and regenerated the same way after each merge ofmain, which moved the section date to 2026-10-21. Regenerating again from the final commit produces an identical file. The diff adds 50 lines and removes none, so earlier releases are untouched.CHANGELOG.mdandcliff.tomlfor each follow-up changelog commit.This change adds no runtime code. No build, test suite or deployment was run against the release candidate beyond CI.
Risk
Low for this change itself: it touches only version strings, lock files, the changelog and
cliff.tomlgrouping rules.The release carries behavior changes that operators should know about before upgrading:
Unknownnow arrive asUnavailableand are retried.cliff.tomlgains a rule per misfiled v1.8.0 commit, pinned by subject as in v1.7.7, plus one skip rule for the #2881/#2953 pair. Without their rules, #2993 and #2984 land under Miscellaneous; with them, under Bug Fixes. A second skip rule drops the branch's own changelog commits, which the generic "Add" rule otherwise listed as a Feature. Taplo sorted the new rules. Each commit matches exactly one of them, and the generated section was checked after sorting.Signing the tag, publishing images and regenerating the config reference remain post-merge steps; this PR does none of them.
AI assistance
Claude Code chose the version by diffing the config schema and metrics since v1.7.7. At Marcus Eagan's request, it bumped the versions, regenerated the lock files and changelog (again after each merge of
main), added thecliff.tomlgrouping rules, ran the checks above and drafted this description. A maintainer should review the version choice and the changelog grouping before merge.🤖 Generated with Claude Code
https://claude.ai/code/session_01HBxQtV9S561AzBo7aPCYFj