Skip to content

Advance the themelios-syntax pin to 9f8879b; release 1.0.8 - #12

Merged
GregoryGelfond merged 1 commit into
mainfrom
release-1.0.8
Sep 23, 2026
Merged

GregoryGelfond merged 1 commit into
mainfrom
release-1.0.8

Conversation

@GregoryGelfond

Copy link
Copy Markdown
Owner

Advances the pinned themelios-syntax revision 4f02758 → 9f8879b (themelios main) and releases 1.0.8.

No-op currency bump. The themelios delta across this range is confined to themelios-program — a new AnswerSet alias and a multi-part Program::of_keyed_nodes constructor, both purely additive — plus design docs. morphe depends only on themelios-syntax (transitively themelios-base); a scoped diff of those two crates across the bump is empty, so the surface morphe consumes is byte-identical and resolved behaviour is identical. No source, API, or behaviour change.

Also repaired: the CHANGELOG link references, which since 1.0.7 lacked a [1.0.7] target and still compared [Unreleased] from v1.0.6; both are corrected here alongside the new [1.0.8] entry.

Gate: the full standing gate passes locally — fmt, clippy (default and embedded backends), test (default and embedded), doc under -D warnings, and the coverage floor at 94.12% (floor 90). Both crates align at 1.0.8.

Keep morphe current with the tier's main. The advance carries a program-tier
addition only — a new AnswerSet alias and a multi-part Program constructor in
themelios-program, which morphe does not depend on. The themelios-syntax surface
morphe consumes is byte-identical across the bump and the resolved behaviour is
identical; no API or behaviour change. A deliberate rev-bump with no source
change is a patch release.

Both crates align at 1.0.8.
@GregoryGelfond
GregoryGelfond merged commit 5cc9869 into main Sep 23, 2026
2 checks passed
@GregoryGelfond
GregoryGelfond deleted the release-1.0.8 branch September 23, 2026 22:43
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