Skip to content

fix(ci): check out openaec-reports so builds stop failing#9

Open
Nozzit wants to merge 1 commit into
OpenAEC-Foundation:mainfrom
Nozzit:ci/checkout-openaec-reports
Open

fix(ci): check out openaec-reports so builds stop failing#9
Nozzit wants to merge 1 commit into
OpenAEC-Foundation:mainfrom
Nozzit:ci/checkout-openaec-reports

Conversation

@Nozzit

@Nozzit Nozzit commented Jul 20, 2026

Copy link
Copy Markdown

The problem

Every build job on every platform has been failing since May. The three most recent release.yml runs failed on all four matrix jobs, and nightly.yml has failed every night since. As a result the pipeline produces no artifacts at all — the v0.1.4 release contains only the Windows installer, which was evidently built and uploaded by hand.

The cause

packages/desktop/src-tauri/Cargo.toml has a path dependency pointing outside the repository:

openaec-core = { path = "../../../../openaec-reports/rust/crates/openaec-core" }

That resolves to a sibling directory next to the repository root — a layout developers have locally, but which CI never creates. From today's nightly run (Linux job):

error: failed to get `openaec-core` as a dependency of package `open-calculations-studio v0.1.4`
  failed to read `/home/runner/work/Open-Calculations-Studio/openaec-reports/rust/crates/openaec-core/Cargo.toml`
  No such file or directory (os error 2)

The identical error appears in the Windows and macOS jobs, which is why all four fail.

The change

Clone the sibling repository into ../openaec-reports before the build, mirroring the local development layout. OpenAEC-Foundation/openaec-reports is public, so no additional token is needed. Added to the three workflows that build the app: ci.yml, nightly.yml, release.yml. Nine added lines, nothing else touched.

actions/checkout is not usable here because it refuses to write outside $GITHUB_WORKSPACE, and the dependency has to land in the workspace's parent directory.

Verification

Reproduced and fixed locally against this branch:

cargo metadata in packages/desktop/src-tauri
Without the sibling checkout fails with the exact CI error above
With the sibling checkout exit 0, resolves all 607 packages

The workflow YAML parses cleanly. What I could not verify is a full end-to-end run on GitHub's runners — that only happens once this is merged and a build is triggered. If anything else is broken further along the pipeline, this fix gets the build past its first hurdle rather than guaranteeing a green run.

Why this came up

The OpenAEC Installer gained Linux support and can install tools that publish an .AppImage. This repository already lists appimage in its bundle targets, so once the pipeline builds again, Linux artifacts should follow without further changes here.

Note that openaec-core is pinned to whatever is on openaec-reports@main. If you would rather have reproducible builds, a git dependency with a pinned rev would be the more robust long-term fix — that felt like a bigger architectural call than belongs in a build fix.

🤖 Generated with Claude Code

…c-core

Every build job on every platform has been failing since May, so no
release artifacts are produced at all — the v0.1.4 release only contains
the Windows installer that was built by hand.

The cause is a path dependency in packages/desktop/src-tauri/Cargo.toml:

  openaec-core = { path = "../../../../openaec-reports/rust/crates/openaec-core" }

That resolves to a sibling directory next to the repository root, which
developers have locally but CI never checks out. Cargo then fails with:

  failed to get `openaec-core` as a dependency
  failed to read `.../openaec-reports/rust/crates/openaec-core/Cargo.toml`
  No such file or directory (os error 2)

Cloning the (public) sibling repository into ../openaec-reports before
the build mirrors the local development layout. Added to the three
workflows that build the app: ci.yml, nightly.yml and release.yml.

Verified locally: `cargo metadata` in packages/desktop/src-tauri fails
with the exact CI error without the sibling checkout, and resolves all
607 packages with it.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
@Nozzit
Nozzit requested a review from DutchSailor as a code owner July 20, 2026 13:03
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.

1 participant