Skip to content

Ship MainNet default splice-dars (0.1.4) - #4

Merged
HardlyDifficult merged 2 commits into
mainfrom
cursor/default-splice-dars-bef4
Aug 11, 2026
Merged

Ship MainNet default splice-dars (0.1.4)#4
HardlyDifficult merged 2 commits into
mainfrom
cursor/default-splice-dars-bef4

Conversation

@HardlyDifficult

@HardlyDifficult HardlyDifficult commented Aug 11, 2026

Copy link
Copy Markdown
Collaborator

Summary

Ships a shared config/default-splice-dars.json so repos can run sync-splice-dars without maintaining a local copy.

Splice pin: MainNet 0.6.14 (398919a5b13479877fd61587003ba7a4ba00091b) — not TestNet 0.7.0.

Version 0.1.4 (0.1.3 had been published earlier with the wrong 0.7.0 ref; this corrects it).

Override precedence: --configCANTON_SPLICE_DARS_CONFIG → repo-root splice-dars.json → packaged default.

Test plan

  • unit tests / build / lint / pack:check
  • merge → publish workflow publishes 0.1.4
Open in Web Open in Cursor 

cursoragent and others added 2 commits August 11, 2026 18:52
Consumers can drop per-repo splice-dars.json and use the packaged
0.7.0 pin; a local file remains an optional override.

Co-authored-by: hardlydiff <hardlydiff@gmail.com>
Replace TestNet 0.7.0 spliceRef with MainNet commit
398919a5b13479877fd61587003ba7a4ba00091b (tag 0.6.14). DAR sha256s
are unchanged. Bump package to 0.1.4 so main merge publishes the fix
(0.1.3 already shipped with the wrong pin).

Co-authored-by: hardlydiff <hardlydiff@gmail.com>
@cursor cursor Bot changed the title Ship shared default splice-dars.json (0.1.3) Ship MainNet default splice-dars (0.1.4) Aug 11, 2026
@HardlyDifficult
HardlyDifficult marked this pull request as ready for review August 11, 2026 19:39
@HardlyDifficult
HardlyDifficult merged commit f1b0c5b into main Aug 11, 2026
3 checks passed
@HardlyDifficult
HardlyDifficult deleted the cursor/default-splice-dars-bef4 branch August 11, 2026 19:45
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