Version Packages - #104
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
August 3, 2026 12:36
fec27fb to
2b0d82e
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@neuledge/context@1.2.1
Patch Changes
#105
d557b46Thanks @moshest! - Keep every installed version of a package usable. Installing a second version of the same package (for example upgradingocctswiftfrom1.15.9to1.15.10) used to hide one of them: only one version per name was tracked, and which one survived depended on the order the package files happened to be read in.context listshowed a single entry, andcontext query occtswift@1.15.10reported "Package not found" even though the package was installed — removing the older version was the only workaround.All installed versions are now listed and addressable.
name@versionresolves to that exact version, and a bare name resolves to the highest installed version, compared numerically so1.15.10beats1.15.9(prereleases rank below their release; labels such aslatestrank below any numbered version).context serve --libs pkg@1.15.9now pins the session to exactly that version while a newer one stays installed; a bare--libs pkgexposes every installed version.context removeno longer ignores the version in its argument:context remove pkg@1.15.9removes exactly that version, and a bare name is refused with the list of installed versions when there is more than one, instead of deleting an arbitrary one.context addnow points out when the version just installed is not the one a bare name resolves to.#103
f3d5e43Thanks @moshest! - Fix out-of-memory crash when building packages from very large documentation files (such as a site'sllms-full.txt, or a single-page HTML manual). Oversized markdown is now split into smaller chunks before parsing, and oversized HTML is cut at tag boundaries before it reaches the HTML-to-Markdown converter, so no input can exhaust the heap. An 8MB HTML page that previously needed more than 512MB of heap now builds in under 192MB and yields the same sections. The HTML split also scans each page once rather than once per tag, so a malformed page full of unclosed<scriptor<svgtags no longer stalls the build for minutes.Malformed pages keep their page chrome out of the index: a stray close tag such as a
</header>inside an<aside>no longer ends the sidebar early and leak it into search results, and a<script>,<style>or<title>that is never closed no longer has its body indexed as prose. A file that cannot be split or parsed at all is now skipped on its own instead of failing the whole build, andbuildPackagereports how many it skipped.Sections of a split document also keep unique titles. A page with no
##/<h2>heading anywhere — anh1+h3page, or one with div-based headings — used to restart its part numbering in every chunk, so the same run of "Introduction", "Introduction (part 2)", … repeated once per chunk and blunted title search; the numbering now runs continuously across the whole document. Such a page also keeps its frontmatter title on every chunk instead of falling back to the filename part-way through.@neuledge/registry@0.0.14
Patch Changes
d557b46,f3d5e43]: