Repository navigation
Conversation
why: Package inventory must describe native source applications while excluding generated builds and artwork directories. what: - Parse constant application terms in a bounded OTP 29 child - Require matching application names and flat nonempty Unicode versions - Cover root and umbrella layouts, invalid terms and input limits
This was referenced Nov 9, 2026
tony
added a commit
that referenced
this pull request
Nov 9, 2026
tony
added a commit
that referenced
this pull request
Nov 9, 2026
…ts (#291) why: Six ports had docs branches ready but no published site, and three shared fixes were waiting behind them. Releasing them together gives one docs commit to trust for deployment and one set of caller pins to move, instead of six separate waves. what: - Add OCaml (#264), Haskell (#265), Erlang (#266, #278, #279, #280, #284, #292), Common Lisp (#268), Perl (#274) and Clojure (#276): native API pages, tested guides, navigation, landing and switcher entries, and cross-reference data for each - Keep browser checks from loading third-party resources, and pass the check origin to the three scripts that named an undefined base (#287) - Render guide badges at build time instead of hotlinking shields (#288) - Size the reference sidebar and member bars from the viewport, so the Chrome iOS keyboard no longer shrinks them (#290) - Make the OCaml model producer verify its native build inputs in their checkout and reject stale ones, with controls run in CI - Offer one switcher page per port, and title Perl's workspace guide "Workspace guide" - Regenerate the registry, mention index and cross-reference counts for the combined port set Base main 2593131, head dabe59b. Port heads: #264 7d4f88f and 73fb1ad, #265 dc024e3, #268 947da1f, #274 818fa2e, #276 a134503, #287 a437e97, #292 e7740d9.
Contributor
Author
|
Shipped in #291 (8245169, 2026-11-09 07:38 CST), the combined release: this PR's head |
tony
temporarily deployed
to
docs-preview-cleanup
November 12, 2026 01:53 — with
GitHub Actions
Inactive
This branch was previously deployed
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.
Summary
Read Erlang application identities and versions from root and umbrella
.app.srcfiles. This lets package inventory distinguish source applications from generated build copies and artwork directories.The reader uses OTP 29's scanner and constant-term parser without evaluating application source. Each application name must match its filename, with exactly one nonempty flat Unicode version string. The native child's serialized input and captured output are limited to 1 MiB, with a five-second deadline; these limits do not bound Git reads or Node allocations before serialization.
This is a prerequisite for Erlang site registration. It does not register the port or qualify a package or deployment. Stacked on #280, the native command-usage reader; the earlier extraction and signature work remains in #279. MCP remains excluded from the Erlang port.
Test plan
Fixtures cover source layouts, artwork/build exclusion, duplicate or mismatched metadata, nested character data, and executable expressions. The expression fixture would produce a valid version if evaluated, so rejection distinguishes constant-term parsing from evaluation followed by metadata validation. The initial empty-version failure and both review HOLDs remain preserved.
The existing whole-loop timing failures remain unwaived and tracked in #271. Registration, rendered site assembly and publisher wiring remain separate work.