Skip to content

chore: bump to rc.48 and crate 0.8.0#12

Merged
samjanny merged 1 commit into
mainfrom
chore/bump-rc48-readme
Jun 3, 2026
Merged

chore: bump to rc.48 and crate 0.8.0#12
samjanny merged 1 commit into
mainfrom
chore/bump-rc48-readme

Conversation

@samjanny
Copy link
Copy Markdown
Owner

@samjanny samjanny commented Jun 3, 2026

The content-index and undeclared-state conformance fixes are merged, but SPEC_REVISION and the CI corpus pin still pointed at rc.47, so CI ran against the 88-vector corpus and never exercised the 20 new vectors.

  • SPEC_REVISION 1.0-rc.47 -> 1.0-rc.48 (entangled-core/src/lib.rs).
  • CI corpus checkout ref v1.0-rc.47 -> v1.0-rc.48 (.github/workflows/ci.yml). The conformance harness asserts these match the corpus rc_target, so they move in lockstep, and CI now runs the full 108-vector corpus (106 in scope, 2 Stage 7 trust vectors out of scope).
  • Crate version 0.7.0 -> 0.8.0 (additive: content-index wiring and the optional state_policy parameter on parse_and_verify_transaction).
  • Correct the stale crate-version line in README.md (0.5.7 -> 0.8.0).

Verified locally: fmt, clippy -D warnings, doc -D warnings, full test suite, and the conformance suite against the rc.48 corpus all green.

The conformance fixes for content index and undeclared state are merged
but SPEC_REVISION and the CI corpus pin still pointed at rc.47, so CI ran
against the 88-vector corpus and never exercised the 20 new vectors. Move
both to rc.48: SPEC_REVISION in entangled-core/src/lib.rs and the corpus
checkout ref in .github/workflows/ci.yml. The conformance harness asserts
these match the corpus rc_target, so they move in lockstep.

Bump the crate version 0.7.0 -> 0.8.0 (the content-index wiring and the
new optional state_policy parameter on parse_and_verify_transaction are
additive functionality), and correct the stale crate-version line in
README.md (0.5.7 -> 0.8.0).
@samjanny samjanny merged commit 1013c9d into main Jun 3, 2026
11 checks passed
@samjanny samjanny deleted the chore/bump-rc48-readme branch June 3, 2026 09:22
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