Changelog - 2026-10-18

VULCAN 0.2.0-6: typescript is never auto-installed, changes knows an unreleased package

Type: Bug Fix

In one line. Two defects BANA's rehearsal found in atlas: a stray install of typescript 7, and a misleading "unknown package".

What changed

• atlas never auto-installs typescript. In a directory with no node_modules, Bun answered a bare require('typescript') by fetching the newest typescript (7.x, no compiler API). atlas now looks for node_modules/typescript on disk, first from the project and then in its own install, and installs nothing. With no typescript in either place it fails with atlas: cannot find typescript ... - install it with bun add typescript.
• changes knows a package that has no release on this ref. A tag outside the checked-out branch's history releases nothing there, so a project with a repo-level atlas.tagPattern and its date tags on another branch had no released package, and changes {"package":"@nx/core"} said unknown package. A declared package (by npm name, directory key or alias) now answers the dated entries whose packages: frontmatter names it, with a note that says there is no release on this ref. A from or to version is refused with that reason. A name nobody declares is still unknown.
• The "no releases" reason is accurate. It now reads no tag matches <pattern> in this ref's history.

Who is affected

• A client that read changes's unknown package for an unreleased package. It now gets a result with a note.
• Everyone else. No action needed: upgrade, then vulcan sync.