v1.0.0

1.0.0 - 2026-02-19

• TAG: v1.0.0
• COVERAGE: 83.82% -- 171/204 lines in 7 files
• BRANCH COVERAGE: 41.30% -- 19/46 branches in 7 files
• 78.87% documented

Added

• AGENTS.md
• Initial release of markly-merge
• Thin wrapper around markdown-merge for Markly backend
• Markly::Merge::SmartMerger - smart merging with markly defaults
  • Default freeze token: "markly-merge"
  • Default inner_merge_code_blocks: true (enabled by default)
• Markly::Merge::FileAnalysis - file analysis with markly backend
• Markly::Merge::FreezeNode - freeze block support
• Markly-specific parse options:
  • flags: - Markly parse flags (e.g., Markly::FOOTNOTES, Markly::SMART)
  • extensions: - GFM extensions (:table, :strikethrough, :autolink, :tagfilter, :tasklist)
• Error classes: Error, ParseError, TemplateParseError, DestinationParseError
• Re-exports shared classes from markdown-merge:
  • FileAligner, ConflictResolver, MergeResult
  • TableMatchAlgorithm, TableMatchRefiner, CodeBlockMerger
  • NodeTypeNormalizer
• FFI backend isolation for test suite
  • Added bin/rspec-ffi script to run FFI specs in isolation (before MRI backend loads)
  • Added spec/spec_ffi_helper.rb for FFI-specific test configuration
  • Updated Rakefile with ffi_specs and remaining_specs tasks
  • The :test task now runs FFI specs first, then remaining specs
• MergeGemRegistry Integration: Registers with Ast::Merge::RSpec::MergeGemRegistry
  • Enables automatic RSpec dependency tag support
  • Registers as category :markdown
• Documentation on hostile takeover of RubyGems
  • https://dev.to/galtzo/hostile-takeover-of-rubygems-my-thoughts-5hlo

Security

Dependencies

• appraisal2 (v3.0.6)
• kettle-test (v1.0.10)
• stone_checksums (v1.0.3)
• ast-merge (v4.0.6) - shared merge infrastructure
• tree_haver (v5.0.5) - normalized AST conventions
• markdown-merge (v1.0.3) - central merge infrastructure for markdown
• tree_stump (v0.2.0)
• markly (~> 0.15) - cmark-gfm C library
• version_gem (~> 1.1) - smart versions for libraries

Security

Official Discord 👉️

Many paths lead to being a sponsor or a backer of this project. Are you on such a path?