dry-validation-rust 0.1.0.pre5-aarch64-linux → 0.1.0.pre6-aarch64-linux

data/CONTRIBUTING.md

@@ -0,0 +1,159 @@
+# Contributing to dry-validation-rust
+
+Thank you for helping improve `dry-validation-rust`. This is a hybrid
+Ruby/Rust native extension, so changes must preserve both Ruby-facing behavior
+and the safety of the Rust FFI boundary.
+
+Before starting substantial work, open an issue or comment on an existing one
+so scope and compatibility expectations can be agreed. Keep pull requests
+focused on one behavior, maintenance concern, or documentation change.
+Roadmap priorities, milestone scope, label meanings, and project-board flow are
+defined in [docs/PROJECT_MANAGEMENT.md](docs/PROJECT_MANAGEMENT.md).
+
+## Prerequisites
+
+Use a Ruby, Rust toolchain, and platform listed in
+[the support matrix](docs/SUPPORT_MATRIX.md). A source checkout currently
+requires:
+
+- CRuby 3.3 or newer with development headers;
+- Rust 1.75 or newer and Cargo (the MSRV, tested in CI);
+- Bundler;
+- a C compiler and `make`;
+- Clang/libclang when the selected `rb-sys` build requires bindgen.
+
+The checkout pins Rust 1.75.0 in `rust-toolchain.toml`, so the documented
+commands use the MSRV by default. Do not introduce code or dependencies that
+require a newer Rust release unless the MSRV policy is intentionally updated.
+
+On macOS, install the Xcode Command Line Tools and LLVM. On Debian/Ubuntu,
+install a build toolchain plus `clang` and `libclang-dev`.
+
+## Clean-checkout setup
+
+```bash
+git clone https://github.com/alex-tomilov/dry-validation-rust.git
+cd dry-validation-rust
+bundle install
+bundle exec rake compile
+script/verify
+```
+
+`script/verify` is the canonical local gate. It compiles the native extension,
+runs the Ruby and Rust tests, checks Rust formatting and Clippy warnings,
+verifies the lockfile, builds the source gem, installs it into an isolated gem
+home, and runs an installed-package smoke contract.
+
+## Test layers
+
+Use the smallest relevant check while developing, then run `script/verify`
+before requesting review.
+
+```bash
+# Ruby integration suite
+script/test
+
+# One Ruby test file
+bundle exec ruby -Itest test/schema_test.rb
+
+# Rust unit tests and quality checks
+cargo test --locked --manifest-path ext/dry_validation_rust/Cargo.toml
+cargo fmt --check --manifest-path ext/dry_validation_rust/Cargo.toml
+cargo clippy --manifest-path ext/dry_validation_rust/Cargo.toml \
+  --all-targets --all-features -- -D warnings
+
+# Source-gem contents and clean-install smoke
+bundle exec rake package:audit
+```
+
+Rust code must be formatted with `rustfmt` and pass Clippy with warnings denied.
+Consider installing a pre-commit hook so formatting issues are caught before
+pushing:
+
+```bash
+cargo install cargo-husky
+```
+
+Code must compile on the Rust 1.75 MSRV; all CI workflows use and test that
+exact toolchain.
+Runtime and FFI code must not use `unwrap`, `expect`, broad `.ok()`, or
+`unwrap_or(default)` unless the reason is narrow, documented, and reviewed.
+No Rust panic may cross the Ruby FFI boundary.
+
+## Compatibility fixtures
+
+The current baseline fixtures live in `test/fixtures/baseline` and are
+exercised by `test/baseline_fixture_test.rb`.
+
+When changing compatibility behavior:
+
+1. Add or update a narrowly named scenario in
+   `test/baseline_fixture_test.rb`.
+2. Add the expected normalized result under
+   `test/fixtures/baseline/<scenario>.json`.
+3. Cover valid and invalid input when both paths are relevant.
+4. Compare the same contract and input against the pinned
+   `dry-validation` and `dry-schema` versions from
+   `docs/SUPPORT_MATRIX.md`, in a separate process.
+5. Include both outputs, exceptions, and version details in the pull request.
+
+The full differential harness is not implemented yet. Until it is, do not
+describe a local baseline fixture as proof of upstream parity.
+
+## Changelog policy
+
+Add an entry under `Unreleased` in `CHANGELOG.md` for user-visible behavior,
+compatibility changes, packaging changes, security changes, or meaningful
+documentation changes. Internal refactors that do not affect users generally
+do not need an entry.
+
+Do not rewrite released changelog sections except to correct a factual error.
+
+## Benchmark evidence
+
+Performance claims require reproducible before/after evidence. Include:
+
+- the exact benchmark script and revision;
+- warmup and measured iteration counts;
+- Ruby, Rust, dependency, OS, CPU, and memory details;
+- throughput or latency plus RSS/allocations where relevant;
+- raw results from multiple runs;
+- compatibility checks proving semantics did not change.
+
+`script/benchmark-smoke` is a non-gating sanity check, not evidence for a
+public performance claim.
+
+## Pull requests
+
+The repository currently uses `develop` as the active integration branch and
+`main` as the default/release branch. Unless a maintainer requests otherwise,
+open feature and maintenance pull requests against `develop`. Tested changes
+are promoted to `main`; releases are tagged from `main`.
+
+Pull requests should:
+
+- link the implementation issue and milestone;
+- explain the problem and the chosen design;
+- identify public API and compatibility impact;
+- include regression tests for behavior changes;
+- remain small enough to review as one coherent change;
+- update relevant documentation and the changelog;
+- report exact verification commands and results;
+- avoid drive-by formatting or unrelated refactoring.
+
+Prefer squash merging for a focused pull request. Do not force-push after
+review has started unless necessary to remove sensitive data or repair the
+branch, and explain any rewritten history.
+
+Do not commit generated native libraries, packaged `.gem` files, Cargo
+`target` output, generated Makefiles, or other build artifacts. Release tooling
+may generate binary artifacts in CI, but those artifacts belong in the release
+pipeline rather than the source tree.
+
+## Contribution certification
+
+The project does not require a Contributor License Agreement or mandatory
+Developer Certificate of Origin sign-off at this stage. By contributing, you
+confirm that you have the right to submit the work under the repository's MIT
+license. A future certification change will be proposed publicly before it is
+enforced.

data/GOVERNANCE.md

@@ -0,0 +1,68 @@
+# Governance
+
+## Project status and maintainer
+
+`dry-validation-rust` is an independent, single-maintainer project. Alexey
+Tomilov is the current maintainer and has final responsibility for technical
+direction, merges, releases, security advisories, and repository
+administration.
+
+This governance model describes the current project; it does not imply a
+foundation, steering committee, or multi-maintainer organization.
+
+## Decision making
+
+Routine changes are decided through issue and pull-request discussion. The
+maintainer considers correctness, compatibility evidence, FFI safety,
+maintenance cost, performance evidence, and alignment with the documented
+product scope.
+
+When consensus is not reached, the maintainer makes the final decision and
+records material tradeoffs in the issue, pull request, architecture
+documentation, or changelog as appropriate.
+
+## Compatibility philosophy
+
+`Dry::Validation::Rust::Contract` is the primary supported API. Familiar
+dry-validation-style behavior is supported only where it is documented and
+tested against pinned upstream releases. Exact compatibility mode remains
+experimental and process-isolated from upstream gems.
+
+Unsupported behavior must fail loudly. Compatibility claims require executable
+evidence; performance claims require reproducible measurements. The project
+will not silently widen its supported DSL or weaken tests to hide a mismatch.
+
+## Breaking changes
+
+Breaking changes should start with a public issue describing the affected
+surface, migration path, compatibility evidence, and release impact. During
+the alpha period, breaking changes may occur in prereleases, but they must be
+intentional and documented.
+
+Once a stable line exists, its deprecation and support policy will be defined
+before release. This file does not create a stability promise beyond the
+current support matrix.
+
+## Branches and releases
+
+`main` is the default and release branch. `develop` is currently the active
+integration branch, with short-lived feature branches merged through pull
+requests. Tested changes are promoted from `develop` to `main`.
+
+Only the maintainer may authorize a gem publication, release tag, GitHub
+release, or security advisory. Passing CI does not itself authorize a release.
+
+## Adding maintainers
+
+Additional maintainers may be invited after sustained, trustworthy
+contributions across code review, compatibility work, security-sensitive
+changes, documentation, and support. Access should be granted incrementally
+and follow least privilege. Any change to release or security authority will
+be documented publicly.
+
+## Relationship to dry-rb
+
+This project is independent from dry-rb and its maintainers. It is not an
+official dry-rb project, and its compatibility and support statements apply
+only to `dry-validation-rust`. Upstream project names are used to describe the
+API reference and comparison target.

data/Gemfile

@@ -0,0 +1,15 @@
+# frozen_string_literal: true
+
+source 'https://rubygems.org'
+gemspec
+gem 'benchmark', '>= 0.3', '< 1.0'
+gem 'benchmark-ips', '~> 2.14'
+gem 'bundler-audit', require: false
+gem 'dry-validation', '1.11.1'
+gem 'memory_profiler', '~> 1.1'
+gem 'rubocop', '>= 1.88.2'
+gem 'rubocop-minitest', require: false
+gem 'rubocop-performance', require: false
+gem 'simplecov', require: false, group: :test
+gem 'simplecov-lcov', require: false, group: :test
+gem 'yard', '~> 0.9', require: false

data/Gemfile.lock

@@ -0,0 +1,132 @@
+PATH
+  remote: .
+  specs:
+    dry-validation-rust (0.1.0.pre6)
+      bigdecimal (>= 3.1, < 5.0)
+      rb_sys (>= 0.9.100, < 0.10)
+
+GEM
+  remote: https://rubygems.org/
+  specs:
+    ast (2.4.3)
+    benchmark (0.5.0)
+    benchmark-ips (2.15.1)
+    bigdecimal (4.1.2)
+    bundler-audit (0.9.3)
+      bundler (>= 1.2.0)
+      thor (~> 1.0)
+    concurrent-ruby (1.3.7)
+    drb (2.2.3)
+    dry-configurable (1.4.0)
+      dry-core (~> 1.0)
+      zeitwerk (~> 2.6)
+    dry-core (1.2.0)
+      concurrent-ruby (~> 1.0)
+      logger
+      zeitwerk (~> 2.6)
+    dry-inflector (1.3.1)
+    dry-initializer (3.2.0)
+    dry-logic (1.6.0)
+      bigdecimal
+      concurrent-ruby (~> 1.0)
+      dry-core (~> 1.1)
+      zeitwerk (~> 2.6)
+    dry-schema (1.16.0)
+      concurrent-ruby (~> 1.0)
+      dry-configurable (~> 1.0, >= 1.0.1)
+      dry-core (~> 1.1)
+      dry-initializer (~> 3.2)
+      dry-logic (~> 1.6)
+      dry-types (~> 1.9, >= 1.9.1)
+      zeitwerk (~> 2.6)
+    dry-types (1.9.1)
+      bigdecimal (>= 3.0)
+      concurrent-ruby (~> 1.0)
+      dry-core (~> 1.0)
+      dry-inflector (~> 1.0)
+      dry-logic (~> 1.4)
+      zeitwerk (~> 2.6)
+    dry-validation (1.11.1)
+      concurrent-ruby (~> 1.0)
+      dry-core (~> 1.1)
+      dry-initializer (~> 3.2)
+      dry-schema (~> 1.14)
+      zeitwerk (~> 2.6)
+    json (2.21.2)
+    language_server-protocol (3.17.0.6)
+    lint_roller (1.1.0)
+    logger (1.7.0)
+    memory_profiler (1.1.0)
+    minitest (6.0.6)
+      drb (~> 2.0)
+      prism (~> 1.5)
+    parallel (2.1.0)
+    parser (3.3.12.0)
+      ast (~> 2.4.1)
+      racc
+    prism (1.9.0)
+    racc (1.8.1)
+    rainbow (3.1.1)
+    rake (13.4.2)
+    rake-compiler (1.3.1)
+      rake
+    rake-compiler-dock (1.12.0)
+    rb_sys (0.9.128)
+      rake-compiler-dock (= 1.12.0)
+    regexp_parser (2.12.0)
+    rubocop (1.89.0)
+      json (~> 2.3)
+      language_server-protocol (~> 3.17.0.2)
+      lint_roller (~> 1.1.0)
+      parallel (>= 1.10)
+      parser (>= 3.3.0.2)
+      rainbow (>= 2.2.2, < 4.0)
+      regexp_parser (>= 2.9.3, < 3.0)
+      rubocop-ast (>= 1.49.0, < 2.0)
+      ruby-progressbar (~> 1.7)
+      unicode-display_width (>= 2.4.0, < 4.0)
+    rubocop-ast (1.50.0)
+      parser (>= 3.3.7.2)
+      prism (~> 1.7)
+    rubocop-minitest (0.40.0)
+      lint_roller (~> 1.1)
+      rubocop (>= 1.75.0, < 2.0)
+      rubocop-ast (>= 1.38.0, < 2.0)
+    rubocop-performance (1.27.0)
+      lint_roller (~> 1.1)
+      rubocop (>= 1.89.0, < 2.0)
+      rubocop-ast (>= 1.47.1, < 2.0)
+    ruby-progressbar (1.13.0)
+    simplecov (1.1.1)
+    simplecov-lcov (0.9.0)
+    thor (1.5.0)
+    unicode-display_width (3.2.0)
+      unicode-emoji (~> 4.1)
+    unicode-emoji (4.2.0)
+    yard (0.9.45)
+    zeitwerk (2.8.2)
+
+PLATFORMS
+  ruby
+  x86_64-linux
+
+DEPENDENCIES
+  benchmark (>= 0.3, < 1.0)
+  benchmark-ips (~> 2.14)
+  bundler-audit
+  dry-validation (= 1.11.1)
+  dry-validation-rust!
+  memory_profiler (~> 1.1)
+  minitest (~> 6.0)
+  rake (~> 13.1)
+  rake-compiler (~> 1.3)
+  rake-compiler-dock (~> 1.12)
+  rubocop (>= 1.88.2)
+  rubocop-minitest
+  rubocop-performance
+  simplecov
+  simplecov-lcov
+  yard (~> 0.9)
+
+BUNDLED WITH
+   2.5.22

data/NOTICE.md

@@ -8,11 +8,11 @@ The public interfaces, documentation, tests, dependency metadata, and
 architecture of these MIT-licensed projects were studied:
 
 - dry-validation, copyright 2015–2026 Hanakai team:
-  https://github.com/dry-rb/dry-validation
+  <https://github.com/dry-rb/dry-validation>
 - dry-schema, copyright its contributors:
-  https://github.com/dry-rb/dry-schema
+  <https://github.com/dry-rb/dry-schema>
 - dry-logic and dry-types:
-  https://github.com/dry-rb
+  <https://github.com/dry-rb>
 
 No upstream implementation source is copied into this project. The compatible
 surface was independently implemented. If future development incorporates
@@ -21,8 +21,8 @@ must be preserved.
 
 The native extension uses:
 
-- Magnus (MIT): https://github.com/matsadler/magnus
-- rb-sys (MIT OR Apache-2.0): https://github.com/oxidize-rb/rb-sys
+- Magnus (MIT): <https://github.com/matsadler/magnus>
+- rb-sys (MIT OR Apache-2.0): <https://github.com/oxidize-rb/rb-sys>
 - serde and serde_json (MIT OR Apache-2.0)
 
 Their complete license texts are distributed by their respective packages.