Skip to content

About

Portable-plan, catalog-signature, and cross-dialect refusal certification across PostgreSQL and CockroachDB.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Latest commit

 

History

33 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

cross-engine-compatibility

Independent **database conformance** harness in `declarative-migrations-test` for `declarative-migrations`.

**Readiness:** `ready`  
**Primary dependency strategy:** `matrix`  
**Scheduled cadence:** `23 4 * * 2,5` UTC  
**Live infrastructure:** PostgreSQL, CockroachDB

## Upstream repositories

- `declarative-migrations/declarative-postgres-migrate.rs`

## Acceptance objectives

1. Verify portable plan equivalence and preflight classification across PostgreSQL and CockroachDB across the supported happy-path states and canonical fixtures.
  1. Verify portable plan equivalence and preflight classification across PostgreSQL and CockroachDB under retries, interruption, concurrency, offline operation, or partial failure.
  2. Verify portable plan equivalence and preflight classification across PostgreSQL and CockroachDB preserves authorization, idempotency, integrity, observability, and actionable failure classification.

Every behavior change must add a regression, preserve exact dependency pinning, avoid credentials in source or logs, and land through a pull request.

declarative-migrations-test/cross-version-matrix-e2e

Generated database-e2e harness for declarative-migrations.

Contract

Profile: database-e2e
Source organization: declarative-migrations

  • upgrade and downgrade matrix
  • server version feature gates
  • lock compatibility

Immutable source pins

Source Commit Branch observed
declarative-migrations/declarative-postgres-migrate.rs c1e0d15c08d55d52909b6eb2b2d5290529ce0114 main

Dependency lanes

Mode Source Manager Path/subdir
none - - -

Running

The pull-request workflow validates the generated contract without cross-organization credentials. Full integration is intentionally release-gated until required source repositories and organization read credentials are present. Run the profile-specific checks recorded in test-plan.json after materializing the submodule, Zed, or native-package lane.

## Dependency paths

This repository tests the upstream through independent installation paths:

1. `./scripts/bootstrap-upstream.sh git-submodule`
2. `./scripts/bootstrap-upstream.sh zed`
3. `./scripts/bootstrap-upstream.sh native-package`

The publisher materializes a real Git submodule when authenticated access is available. Zed and native package coordinates are recorded in `dependency-contract.yaml`; missing unpublished packages are reported as blocked readiness rather than silently skipped.

## Check tiers

```bash
python3 -m pip install -e '.[test]'
pytest -q
./scripts/readiness.py --offline
./scripts/run-live.sh
```

Pull requests validate the harness and deterministic contract fixtures. Secret-, service-, emulator-, desktop-, database-, provider-, chaos-, scale-, and soak-dependent checks run by schedule or manual dispatch.

A live result must be classified as one of:

- **product regression** — a behavioral invariant fails after dependencies are ready;
- **blocked dependency** — an upstream, credential, package, emulator, provider sandbox, or deployment is unavailable;
- **harness regression** — generated metadata, fixtures, workflow, or runner setup is invalid.

Managed by `github-test-org-factory/1.0.0`.

About

Portable-plan, catalog-signature, and cross-dialect refusal certification across PostgreSQL and CockroachDB.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

0 stars

Watchers

0 watching

Forks

Releases

Packages

Contributors

Languages