Skip to content

build: the sibling core checkout is ../core - #6

Merged
dejanstrbac merged 1 commit into
mainfrom
fix-core-dir-default
Sep 10, 2026
Merged

dejanstrbac merged 1 commit into
mainfrom
fix-core-dir-default

Conversation

@dejanstrbac

Copy link
Copy Markdown
Contributor

CORE_DIR defaulted to ../openemail-core, a directory name nothing uses — the repo is Open-Email/core and checks out as core.

So make sync-spec and make sync-spec-check failed on the only layout there is, and the sync had to be given CORE_DIR=../core by hand every time. That is how the vendored snapshot came to sit three core commits behind with TestWireStructsMatchOpenAPISnapshot red on main (fixed in #5): a default that is never right is worse than no default, because the snapshot was not refreshed and wrong — it was not refreshed at all, and nothing said so.

CORE_DIR still overrides, and CI passes .core, so the workflow is unaffected.

Verified: gofmt -l clean, go build ./..., the contract test, and make -n sync-spec (resolves to ../core) / make -n sync-spec CORE_DIR=/tmp/elsewhere (override still wins).

The same one-line default is fixed in the gateway, dav and webmail.

🤖 Generated with Claude Code

CORE_DIR defaulted to `../openemail-core`, a directory name nothing uses:
the repo is Open-Email/core and checks out as `core`. So both spec targets
failed on the only layout there is, and `make sync-spec` had to be given
CORE_DIR=../core by hand every time — which is how the vendored snapshot
came to sit three core commits behind with the contract test red on main.

A default that is never right is worse than no default: the snapshot was
not refreshed and wrong, it was not refreshed at all, and nothing said so.
CORE_DIR still overrides; CI passes `.core` and is unaffected.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@dejanstrbac
dejanstrbac merged commit ecec0c4 into main Sep 10, 2026
2 checks passed
@dejanstrbac
dejanstrbac deleted the fix-core-dir-default branch September 10, 2026 13:44
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