Skip to content

fix: build the linux gnu release on ubuntu-22.04 (glibc 2.35) - #9

Merged
PerishCode merged 1 commit into
mainfrom
fix/linux-glibc-compat
Jun 29, 2026
Merged

PerishCode merged 1 commit into
mainfrom
fix/linux-glibc-compat

Conversation

@PerishCode

Copy link
Copy Markdown
Owner

No description provided.

The x86_64-unknown-linux-gnu artifact was built on ubuntu-latest (24.04,
glibc 2.39) and failed to run on older distros — e.g. Debian 12 (glibc 2.36)
errored with `GLIBC_2.38/2.39 not found`. Build on ubuntu-22.04 so the binary
needs only glibc <= 2.35 and runs on Debian 12 and other modern servers.
@PerishCode
PerishCode merged commit ca643ee into main Jun 29, 2026
3 checks passed
@PerishCode
PerishCode deleted the fix/linux-glibc-compat branch June 29, 2026 12:00
PerishCode added a commit that referenced this pull request Jul 7, 2026
…nd poison (#35)

Flip the trust boundary (PHASE-09 SLICE 0 / decision #9): tool_calls becomes neutral occurrence only; provider wire material moves to an adaptor-owned provider_replay_material side-table; the OpenAI adaptor validate-and-regenerates on read, so an invalid replay blob is a droppable cache-miss (old fc-id-poisoned strands self-heal) instead of a permanent poison. Concept fork regenerable/irreplaceable now, storage later. schema 20->21 (ephemeral wipe; soul memory files survive).
PerishCode pushed a commit that referenced this pull request Aug 1, 2026
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