Releases: Ooops-Studio/core
@ooopsstudio/workload@0.1.0
Minor Changes
-
#1
c213e96
Thanks @italiour! - feat: establish monorepo infrastructure with package validationdd comprehensive package structure and validation system for managing multiple packages with strict dependency boundaries.
Added
- Level 0-3 package architecture with downhill-only imports
- Package-specific ESLint configuration for dependency enforcement
- Dependency-cruiser rules for import boundary validation
- YAML registry files for ports, tokens, services, and engines
- JSON schemas for registry file validation
- Validation script for schema compliance checking
Changed
- ESLint configuration to support package-level rules
- Build pipeline to include package-specific validation
Why
This establishes a robust foundation for managing multiple packages with clear separation of concerns and automated validation of package boundaries and registry schemas.
@ooopsstudio/security@0.1.0
Minor Changes
-
#1
c213e96
Thanks @italiour! - feat: establish monorepo infrastructure with package validationdd comprehensive package structure and validation system for managing multiple packages with strict dependency boundaries.
Added
- Level 0-3 package architecture with downhill-only imports
- Package-specific ESLint configuration for dependency enforcement
- Dependency-cruiser rules for import boundary validation
- YAML registry files for ports, tokens, services, and engines
- JSON schemas for registry file validation
- Validation script for schema compliance checking
Changed
- ESLint configuration to support package-level rules
- Build pipeline to include package-specific validation
Why
This establishes a robust foundation for managing multiple packages with clear separation of concerns and automated validation of package boundaries and registry schemas.
@ooopsstudio/runtime@0.3.0
Minor Changes
-
#1
c213e96
Thanks @italiour! - feat: establish monorepo infrastructure with package validationdd comprehensive package structure and validation system for managing multiple packages with strict dependency boundaries.
Added
- Level 0-3 package architecture with downhill-only imports
- Package-specific ESLint configuration for dependency enforcement
- Dependency-cruiser rules for import boundary validation
- YAML registry files for ports, tokens, services, and engines
- JSON schemas for registry file validation
- Validation script for schema compliance checking
Changed
- ESLint configuration to support package-level rules
- Build pipeline to include package-specific validation
Why
This establishes a robust foundation for managing multiple packages with clear separation of concerns and automated validation of package boundaries and registry schemas.
@ooopsstudio/root@0.1.0
Minor Changes
-
#1
c213e96
Thanks @italiour! - feat: establish monorepo infrastructure with package validationdd comprehensive package structure and validation system for managing multiple packages with strict dependency boundaries.
Added
- Level 0-3 package architecture with downhill-only imports
- Package-specific ESLint configuration for dependency enforcement
- Dependency-cruiser rules for import boundary validation
- YAML registry files for ports, tokens, services, and engines
- JSON schemas for registry file validation
- Validation script for schema compliance checking
Changed
- ESLint configuration to support package-level rules
- Build pipeline to include package-specific validation
Why
This establishes a robust foundation for managing multiple packages with clear separation of concerns and automated validation of package boundaries and registry schemas.
@ooopsstudio/observability@0.3.0
Minor Changes
-
#1
c213e96
Thanks @italiour! - feat: establish monorepo infrastructure with package validationdd comprehensive package structure and validation system for managing multiple packages with strict dependency boundaries.
Added
- Level 0-3 package architecture with downhill-only imports
- Package-specific ESLint configuration for dependency enforcement
- Dependency-cruiser rules for import boundary validation
- YAML registry files for ports, tokens, services, and engines
- JSON schemas for registry file validation
- Validation script for schema compliance checking
Changed
- ESLint configuration to support package-level rules
- Build pipeline to include package-specific validation
Why
This establishes a robust foundation for managing multiple packages with clear separation of concerns and automated validation of package boundaries and registry schemas.
@ooopsstudio/logging@0.1.0
Minor Changes
-
#1
c213e96
Thanks @italiour! - feat: establish monorepo infrastructure with package validationdd comprehensive package structure and validation system for managing multiple packages with strict dependency boundaries.
Added
- Level 0-3 package architecture with downhill-only imports
- Package-specific ESLint configuration for dependency enforcement
- Dependency-cruiser rules for import boundary validation
- YAML registry files for ports, tokens, services, and engines
- JSON schemas for registry file validation
- Validation script for schema compliance checking
Changed
- ESLint configuration to support package-level rules
- Build pipeline to include package-specific validation
Why
This establishes a robust foundation for managing multiple packages with clear separation of concerns and automated validation of package boundaries and registry schemas.
@ooopsstudio/errors@0.1.0
Minor Changes
-
#1
c213e96
Thanks @italiour! - feat: establish monorepo infrastructure with package validationdd comprehensive package structure and validation system for managing multiple packages with strict dependency boundaries.
Added
- Level 0-3 package architecture with downhill-only imports
- Package-specific ESLint configuration for dependency enforcement
- Dependency-cruiser rules for import boundary validation
- YAML registry files for ports, tokens, services, and engines
- JSON schemas for registry file validation
- Validation script for schema compliance checking
Changed
- ESLint configuration to support package-level rules
- Build pipeline to include package-specific validation
Why
This establishes a robust foundation for managing multiple packages with clear separation of concerns and automated validation of package boundaries and registry schemas.
@ooopsstudio/engines@0.1.0
Minor Changes
-
#1
c213e96
Thanks @italiour! - feat: establish monorepo infrastructure with package validationdd comprehensive package structure and validation system for managing multiple packages with strict dependency boundaries.
Added
- Level 0-3 package architecture with downhill-only imports
- Package-specific ESLint configuration for dependency enforcement
- Dependency-cruiser rules for import boundary validation
- YAML registry files for ports, tokens, services, and engines
- JSON schemas for registry file validation
- Validation script for schema compliance checking
Changed
- ESLint configuration to support package-level rules
- Build pipeline to include package-specific validation
Why
This establishes a robust foundation for managing multiple packages with clear separation of concerns and automated validation of package boundaries and registry schemas.
@ooopsstudio/edges@0.1.0
Minor Changes
-
#1
c213e96
Thanks @italiour! - feat: establish monorepo infrastructure with package validationdd comprehensive package structure and validation system for managing multiple packages with strict dependency boundaries.
Added
- Level 0-3 package architecture with downhill-only imports
- Package-specific ESLint configuration for dependency enforcement
- Dependency-cruiser rules for import boundary validation
- YAML registry files for ports, tokens, services, and engines
- JSON schemas for registry file validation
- Validation script for schema compliance checking
Changed
- ESLint configuration to support package-level rules
- Build pipeline to include package-specific validation
Why
This establishes a robust foundation for managing multiple packages with clear separation of concerns and automated validation of package boundaries and registry schemas.
@ooopsstudio/cache@0.1.0
Minor Changes
-
#1
c213e96
Thanks @italiour! - feat: establish monorepo infrastructure with package validationdd comprehensive package structure and validation system for managing multiple packages with strict dependency boundaries.
Added
- Level 0-3 package architecture with downhill-only imports
- Package-specific ESLint configuration for dependency enforcement
- Dependency-cruiser rules for import boundary validation
- YAML registry files for ports, tokens, services, and engines
- JSON schemas for registry file validation
- Validation script for schema compliance checking
Changed
- ESLint configuration to support package-level rules
- Build pipeline to include package-specific validation
Why
This establishes a robust foundation for managing multiple packages with clear separation of concerns and automated validation of package boundaries and registry schemas.