LearnNewsExamplesServices
Frontmatter
id19102
titleWrite the 13.2 upgrade path: what changes for a 13.1 user
stateClosed
labels
documentationenhancementai
assigneesneo-opus-grace
createdAtSep 23, 2026, 11:27 AM
updatedAtSep 23, 2026, 4:40 PM
githubUrlhttps://github.com/neomjs/neo/issues/19102
authorneo-opus-grace
commentsCount1
parentIssue14800
subIssues[]
subIssuesCompleted0
subIssuesTotal0
contentTrust
projected
quarantined0
signals[]
blockedBy[]
blocking[]
closedAtSep 23, 2026, 4:40 PM
milestonev13.2

Write the 13.2 upgrade path: what changes for a 13.1 user

Closed v13.2.0/archive-v13-2-0-chunk-22 documentationenhancementai
neo-opus-grace
neo-opus-grace commented on Sep 23, 2026, 11:27 AM

Context

This is a survey leaf of #14800. It follows the survey method (@tobiu, 2026-09-23: the window is roughly 1,500 PRs and the split moved the Brain and the Fleet Manager out of scope).

This leaf owns Tier 2 across the whole engine window: what a 13.1 user must do when they upgrade. It also owns the build, package and deps slice: 172 merged PRs, listed in the first comment.

The Problem

The notes' Upgrade Path line and Continuity section are still pending (#19091). The one fact known is that the three 13.1 Dock* files were removed without a compatibility layer.

A 13.1 consumer could also hit the following, and none of it is measured yet:

  • Removed trees. The repository lost ai/, apps/agentos and apps/devindex in the split (#17806, #17429), and the notes don't yet say what that means for the published package.
  • package.json changes: scripts, bin, engines, dependencies and postinstall (#19052).
  • The dist/esm output (#17932, #19087).
  • The npx neo-app scaffold.

The Architectural Reality

  • The baseline is the published neo.mjs@13.1.0. npm pack --dry-run on dev gives today's file list.
  • What ships is governed by .npmignore and buildScripts/util/check-package-contents.mjs.
  • Consumer-facing fields live in package.json: compare 615d76e7d2 against dev.

The Fix

  1. Diff the 13.1.0 package file list against npm pack --dry-run on dev, and group removed and added paths by family.
  2. Diff the package.json fields a consumer sees.
  3. Walk the window's Tier-2 candidates across all areas: removals, renames, !: subjects, and config or requirement changes.
  4. Write the Upgrade Path line and a "Breaking changes and upgrade notes" section in resources/content/release-notes/v13.2.0.md.

Acceptance Criteria

  • AC-1 The 13.1.0 → dev package file-list diff is measured and summarized by family, with counts.
  • AC-2 Every removed or renamed public file or API family carries its PR and a one-line migration.
  • AC-3 The consumer-facing package.json changes are listed.
  • AC-4 The Upgrade Path line is filled. Release Type and Stability stay the operator's.
  • AC-5 Reviewed cross-family.

Out of Scope

  • The Brain and Institution lines' own upgrade notes.
  • Changing what ships. A defect found along the way gets a defect-note or its own ticket.

Related

#14800 · #19090 / PR #19091 · #17806 · #17429 · #19052 · #19087 · #17932


Live latest-open sweep: the latest 20 open issues at 2026-09-23T09:26:41Z; no survey leaf exists. A2A claim sweep: the newest messages, all read-states; no claim on a 13.2 notes survey. MC sweep: "release notes which items matter to external readers since last release" found the v13.1 precedent (selection over enumeration, a curated digest, an actionability section) and no prior decision against surveys. Own-assignment sweep: #14800 (parent) and #19090 (iteration 1); no overlap.

Origin Session ID: bf94c4a1-fded-4546-87d6-73df33928275 Retrieval Hint: "13.2 release notes survey external readers upgrade path breaking changes package diff"

tobiu referenced in commit 64ff609 - "docs(release): the 13.2 notes gain the upgrade path from 13.1 (#19102) (#19113) on Sep 23, 2026, 4:40 PM
tobiu closed this issue on Sep 23, 2026, 4:40 PM