Skip to content

Release NativeLink v1.8.0 - #2979

Merged
amankrx merged 8 commits into
TraceMachina:mainfrom
MarcusSorealheis:release/v1.8.0
Oct 21, 2026
Merged

amankrx merged 8 commits into
TraceMachina:mainfrom
MarcusSorealheis:release/v1.8.0

Conversation

@MarcusSorealheis

@MarcusSorealheis MarcusSorealheis commented Oct 20, 2026 •

Copy link
Copy Markdown
Member

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.

#2881 and its revert #2953 cancel out, so neither appears in the changelog.

How was this verified?

  • The branch was cut from main at f66c65c and has since merged main through 2a3ad61 (Restore per-action input fetches as the worker default and suggest a shared pool under load #2984). git describe confirms v1.7.7 is the latest tag on that history.
  • For the version choice, git diff v1.7.7 origin/main over nativelink-config/src and nativelink-util/src/metrics.rs shows only additions, apart from one doc-comment formatting change in schedulers.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 of max_concurrent_input_downloads, a field that is itself new since v1.7.7. No commit in the range is marked breaking.
  • The version is bumped in MODULE.bazel, the root Cargo.toml and all 13 crate manifests, including nativelink-metric-macro-derive. No Cargo.toml or MODULE.bazel still says 1.7.7.
  • Both lock files were regenerated with cargo update --workspace --offline. The only changes are the 18 nativelink-* version entries (13 in Cargo.lock, 5 in the fuzz lock). cargo metadata --offline --locked passes in both workspaces.
  • CHANGELOG.md was prepended with git 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 of main, 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.
  • The PR touches the same 18 files as the v1.7.6 and v1.7.7 release commits.
  • Pre-commit passed on every changed file, including buildifier, generate-bazel-rc, machete, taplo, typos and vale. It passed again on CHANGELOG.md and cliff.toml for 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.toml grouping rules.

The release carries behavior changes that operators should know about before upgrading:

  • Stricter CAS uploads: incomplete uploads are now rejected rather than published.
  • Changed error codes: some errors that clients saw as Unknown now arrive as Unavailable and are retried.

cliff.toml gains 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 the cliff.toml grouping 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

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01HBxQtV9S561AzBo7aPCYFj
@vercel

vercel Bot commented Oct 20, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
nativelink Ready Ready Preview Oct 21, 2026 1:46pm UTC
nativelink-aidm Ready Ready Preview Oct 21, 2026 1:46pm UTC

Request Review

@MarcusSorealheis

Copy link
Copy Markdown
Member Author

/build-image nativelink

@MarcusSorealheis

Copy link
Copy Markdown
Member Author

/build-image nativelink-worker-init

@github-actions

Copy link
Copy Markdown
Contributor

Image built and pushed!

ghcr.io/TraceMachina/nativelink-worker-init:2026-10-20-131cda9d74695b9e9e01fe854aebe40cc5131316

@github-actions

Copy link
Copy Markdown
Contributor

Image built and pushed!

ghcr.io/TraceMachina/nativelink:2026-10-20-131cda9d74695b9e9e01fe854aebe40cc5131316

@MarcusSorealheis
MarcusSorealheis marked this pull request as draft October 20, 2026 18:15
@MarcusSorealheis
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>
MarcusSorealheis and others added 2 commits October 21, 2026 13:43
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>
Comment thread CHANGELOG.md

- 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))

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Comment thread CHANGELOG.md Resolved
MarcusSorealheis and others added 2 commits October 21, 2026 14:44
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>
@amankrx
amankrx merged commit 0c4e6ef into TraceMachina:main Oct 21, 2026
31 checks passed

This branch was successfully deployed

2 active deployments
Preview – nativelink — 5fece13e Deployed Oct 21, 2026 by vercel[bot]
Preview – nativelink-aidm — 5fece13e Deployed Oct 21, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants