Repository navigation
Prepare ReactantServer, Gateway, and Node 0.1.0 for the General registry - #99
Merged
Merged
Conversation
Server, Gateway, and Node have only ever been registered in the internal MMIRegistry (0.1.1 through 0.1.10). They go to General as new packages, which must start at 0.0.1, 0.1.0, or 1.0.0; 0.1.0 is unused in both registries, so it is free. The MMIRegistry 0.1.x entries share these UUIDs and will be yanked once the General registrations merge, so the resolver cannot prefer them. ReactantServerCore goes to 1.2.0, not a patch: the regulated profile added public API (RuntimeProfile, BatchSizeMode, new RuntimeConfig fields) after 1.1.0. Server, Gateway, and Node now floor on Core 1.2.0, since the old "1.0.0" bound admitted a released Core that lacks that API. Reactant_jll goes from the open-ended ">= 0.0.410" to "0.0.410 - 0.0", the range [0.0.410, 0.1.0). General AutoMerge rejects compat entries without an upper bound, and a plain "0.0.410" would pin that one version, since a 0.0.x caret admits only itself. ReactantServerExport goes from the unregistered 1.1.1 to 1.2.0: since 1.1.0 it gained the single-program detection export (detection.jl, two_stage_detector.jl), which is new public API. TagBot gets the three new subdirs so their registrations are tagged. The deploy lock is re-resolved; only the workspace version fields change. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
…t is The philosophy and scope pages described the project largely by exclusion, including "non-LLM" in the mission and "not an LLM serving stack" in the architecture scope. Local LLM serving is now a goal: the memory pressure that puts many models on one GPU applies equally to one model larger than a GPU, and the existing on-demand weight cache and multi-program bundles are the footing for it. Philosophy gains a "Local LLM serving" section describing the direction (split a model into compiled stages, stream each stage's weights from storage, and eventually move weights from storage straight into device memory) and ties generation-specific machinery to the non-interference principle. "Who this is not for" becomes a shorter "Where other tools fit better" that names the design point's edges without the closing dismissal; the LLM entry now scopes out only hosted, high-concurrency services. The mission line, README, docs home, deployment page, and architecture overview and scope are aligned to the same framing. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
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.
Server, Gateway, and Node have only ever been registered in the internal MMIRegistry (0.1.1 through 0.1.10). They go to General as new packages, which must start at 0.0.1, 0.1.0, or 1.0.0; 0.1.0 is unused in both registries, so it is free. The MMIRegistry 0.1.x entries share these UUIDs and will be yanked once the General registrations merge, so the resolver cannot prefer them.
ReactantServerCore goes to 1.2.0, not a patch: the regulated profile added public API (RuntimeProfile, BatchSizeMode, new RuntimeConfig fields) after 1.1.0. Server, Gateway, and Node now floor on Core 1.2.0, since the old "1.0.0" bound admitted a released Core that lacks that API. ReactantServerExport goes to 1.2.0 since it has new detection support code.
Reactant_jll is pinned exactly to 0.0.410 instead of an open-ended floor. General AutoMerge rejects compat entries without an upper bound, and the worker calls the PJRT serialization C API directly, so a new JLL should be adopted deliberately alongside a Reactant bump.
TagBot gets the three new subdirs so their registrations are tagged. The deploy lock is re-resolved; only the workspace version fields change.