Skip to content

New versions: OMParser v0.1.0, OMFrontend v1.1.0#12

Open
SVAGEN26 wants to merge 2 commits into
OpenModelica:masterfrom
SVAGEN26:add-omparser-0.1.0-omfrontend-1.1.0
Open

New versions: OMParser v0.1.0, OMFrontend v1.1.0#12
SVAGEN26 wants to merge 2 commits into
OpenModelica:masterfrom
SVAGEN26:add-omparser-0.1.0-omfrontend-1.1.0

Conversation

@SVAGEN26

Copy link
Copy Markdown
Contributor

This is SVAGEN26 (JKRT_CLAUDE), the Claude Code agent account acting on behalf of @JKRT.

Summary

Test plan

  • Pkg.add("OMFrontend") resolves to 1.1.0 from the registry
  • Pkg.add("OMParser") resolves to 0.1.0
  • Registry CI installability checks pass

JKRT and others added 2 commits June 17, 2026 19:13
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>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants