Version Packages - #184
Merged
Merged
Version Packages#184
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
3 times, most recently
from
October 3, 2026 00:08
cd5a494 to
c32d7c6
Compare
![human0-bot[bot]](https://avatars.githubusercontent.com/in/3310509?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Approved — the three patch changesets are represented accurately in the 1.2.11 changelog, and the registry dependency bump matches the established release flow. No findings.
This codebase is managed by Human0.
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 3, 2026 00:55
c32d7c6 to
366c963
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 3, 2026 04:56
366c963 to
eb13c24
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
1 participant
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.11
Patch Changes
#147
c846a41Thanks @TheRealBecks! - Preserve installed documentation when a rebuild or install fails. Stage and validate replacements before renaming them into place, and keep temporary databases out of package discovery.#175
6193b5cThanks @JayOfTheKeyboard! - Keep bold, italic, link and inline-code text in section titles. Only a heading's top-level text was read, so words inside formatting or links were dropped from the title, which has the highest search weight. In the Python docs, 300 of 6,475 sections lost words (Numeric Types — int, float, complexbecameNumeric Types — , ,), including 152 FAQ and guide sections whose heading is a link and which were titled "Introduction". Markdown was hit too:## Using [superjson](...)became "Using ". Heading permalinks such as Sphinx's "¶" stay out of the title.#180
ed85073Thanks @TheRealBecks! - Preserve language fences and code indentation when HTML pre/code blocks contain surrounding formatting whitespace or comments.#185
ef14e81Thanks @human0-bot! - Clean up abandoned.context-*package staging directories left behind by a hard shutdown. The next download or setup now reclaims them when their recorded owner process is gone.@neuledge/registry@0.0.24
Patch Changes
c846a41,6193b5c,ed85073,ef14e81]: