New versions: OMParser v0.1.0, OMFrontend v1.1.0#12
Open
SVAGEN26 wants to merge 2 commits into
Open
Conversation
Add .github/workflows/installability.yml: for each core package, Pkg.add it FROM THE REGISTRY (no develop) on a clean depot and precompile on Julia 1.12, one package per parallel matrix job. Reproduces a fresh install / demo machine, so a stale or broken registered version fails CI instead of a demo. On pull_request it tests the registry as proposed, gating new registrations. Add OMFrontend to .ci/packages.toml so the daily auto-update bot tracks it. OMFrontend was never in the tracked list, which is why the registry froze at 0.4.1 while master advanced to 1.0.1. Its release Project.toml has no [sources] block, so the existing flow registers it as-is. OMBackend still needs a strip-and-register path ([sources] on master); tracked as follow-up. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
OMParser 0.1.0: Windows/WSL compatibility fixes OMFrontend 1.1.0: skip precompile workload on Windows; add 1.x deps/compat Co-Authored-By: Claude Sonnet 4.6 <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
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 is SVAGEN26 (JKRT_CLAUDE), the Claude Code agent account acting on behalf of @JKRT.
Summary
OMParser v0.1.0— Windows/WSL compatibility fixes (see Fix Windows/WSL precompilation: resolve Absyn via Base.require (v0.1.0) OMParser.jl#27)OMFrontend v1.1.0— skip precompile workload on Windows (see Require OMParser 0.1+ for Windows precompilation (v1.1.0) OMFrontend.jl#86)OMFrontend v1.0.1entry (was missing from the Linux-side registry)OMFrontendDeps.toml: split into[0-1]/[1]sections to reflect the new deps added in the 1.x series (PrecompileTools, Distributed, JSON, Serialization, ManualMemory, OMRuntimeExternalC)OMFrontendCompat.toml: add[1]section withjulia = "1.12.0-1"OMParserCompat.toml range from"0.0.6"to"0.0.6-1"to cover 0.1.0Test plan
Pkg.add("OMFrontend")resolves to 1.1.0 from the registryPkg.add("OMParser")resolves to 0.1.0