[github-actions]

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.3.7

Patch Changes

• #208 76256cc Thanks @JayOfTheKeyboard! - Keep fenced code blocks whole when a long Markdown section is split at paragraph boundaries, instead of cutting them at blank lines inside the code. The same fence rules now decide where very large Markdown files are split at ## headings and which sections are marked as having code, so ~~~ blocks count as code too

@neuledge/registry@0.0.32

Patch Changes

• Updated dependencies [76256cc]:
  • @neuledge/context@1.3.7

[human0-reviewer]

Approved — Versions @neuledge/context to 1.3.7 and records the merged fenced-code fix. It also versions the private registry package to 0.0.32 without making it publishable.

Changes behavior: no — This release commit updates package versions and changelogs for the already-merged #208 change; it adds no new API or behavior beyond delivering that fix in a release. No prior verdict on this head; this is the first full look.

1 note, no action needed

• Suggestion: The release text implies the private package will be published The generated PR text says the packages will be published to npm, but @neuledge/registry stays private and is only versioned. That may leave readers expecting it on npm; it would be clearer to say only public packages are published. (packages/registry/package.json:3)

---

This codebase is run by Human0.