Skip to content

Advance the themelios-syntax pin to 4f02758; release 1.0.7 - #11

Merged
GregoryGelfond merged 1 commit into
mainfrom
release/v1.0.7
Sep 21, 2026
Merged

GregoryGelfond merged 1 commit into
mainfrom
release/v1.0.7

Conversation

@GregoryGelfond

Copy link
Copy Markdown
Owner

Advances the pinned themelios-syntax revision from 653ca5b to 4f02758 and cuts the corresponding patch release, 1.0.7.

Why

themelios origin/main advanced to 4f02758, adding two additive fusion doors (keyword, punctuation) and documenting the module's shared lexical facts. 653ca5b — morphe's current pin, shipped in 1.0.5 — is a true ancestor of 4f02758, so this is a clean forward bump with no divergence.

Scope

  • crates/morphe/Cargo.toml: pin 653ca5b → 4f02758
  • Cargo.lock: refreshed
  • both crates: 1.0.6 → 1.0.7
  • CHANGELOG.md: 1.0.7 entry

No morphe source changes. The fusion surface morphe consumes (separator_between, lex_mode_of, and their types) is unchanged; the new doors are additive and morphe imports none of them. Behaviour is identical — a build-source change with no API change is a patch release.

Verification (full local gate, green)

  • cargo fmt --all --check — clean
  • cargo clippy (workspace + embedded-python,embedded-lua), -D warnings — clean
  • cargo test (workspace + embedded backends) — 0 failures
  • cargo doc --no-deps — clean
  • coverage — 94.12% (floor 90%)

Adopt the syntax tier's additive fusion changes: the keyword roster and the
punctuation formation gain a single home and public doors, and the fusion
module now documents its shared lexical facts. The surface morphe consumes
(separator_between, lex_mode_of, and their types) is unchanged and the resolved
themelios-syntax behaviour is identical; no API or behaviour change. A
deliberate rev-bump with no source change is a patch release.
@GregoryGelfond
GregoryGelfond merged commit ba28cbf into main Sep 21, 2026
3 checks passed
@GregoryGelfond
GregoryGelfond deleted the release/v1.0.7 branch September 21, 2026 21:56
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