Skip to content

Add disaster recovery automation with runbooks#517

Open
Chidubemkingsley wants to merge 18 commits into
Smartdevs17:mainfrom
Chidubemkingsley:Add-disaster-recovery-automation-with-runbooks
Open

Add disaster recovery automation with runbooks#517
Chidubemkingsley wants to merge 18 commits into
Smartdevs17:mainfrom
Chidubemkingsley:Add-disaster-recovery-automation-with-runbooks

Conversation

@Chidubemkingsley
Copy link
Copy Markdown
Contributor

Pull Request Checklist

Quality Gates (All must pass before merge)

  • Lint: Code passes ESLint and Prettier checks
  • Type Check: TypeScript compilation succeeds
  • Tests: All tests pass
  • Build: Project builds successfully
  • Rust Format: Smart contract formatting is correct
  • Rust Clippy: Smart contract linting passes
  • Rust Tests: All smart contract tests pass
  • Rust Build: Smart contracts compile successfully

Additional Requirements

  • New code has appropriate TypeScript types
  • No hardcoded secrets or credentials
  • New features have corresponding tests
  • Documentation updated if needed

Reviewers

  • At least 1 approval required for merge
  • All CI checks must be green

--- closes #431

This PR will not be mergeable until all quality gates pass.

@drips-wave
Copy link
Copy Markdown

drips-wave Bot commented Jun 1, 2026

@Chidubemkingsley Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

@Smartdevs17
Copy link
Copy Markdown
Owner

⚠️ Merge failed — check CI status.

🤖 Drips Wave Merge Agent

@Chidubemkingsley Chidubemkingsley force-pushed the Add-disaster-recovery-automation-with-runbooks branch 2 times, most recently from 09ce28d to 1ccae18 Compare June 2, 2026 09:09
The rustix crate v0.36.5 uses nightly-only attributes
(rustc_layout_scalar_valid_range_start/end) that fail to compile
on newer rustc versions. Switching to prebuilt binary via
cargo-binstall avoids the compilation entirely.
…ary/react-native

- Replaced react-hooks import with react-native renderHook/act in ThemeContext.test.tsx
- Replaced react-hooks import with react-native renderHook/act in useFilteredSubscriptions.test.ts
- Updated ThemeContext test 'throws outside provider' to match new error handling behavior
- Removed @testing-library/react-hooks from package.json (incompatible with React 19 types)
- All tests passing after migration
…rties

The E2E Android build fails because react-native 0.85 gradle-plugin is
compiled with Kotlin 2.1.20 but the Expo Kotlin Gradle plugin defaults
to 1.9.0, causing a metadata version mismatch.

Install expo-build-properties plugin and pin kotlinVersion to 2.1.20.
…E build

iOS: .detoxrc.js workspace/scheme was lowercase 'subtrackr' -> 'SubTrackr'
Android: install expo-build-properties@0.12.5 with kotlinVersion 2.1.20
to match react-native 0.85's Kotlin 2.1.20 gradle-plugin compilation.
Expo SDK 53 ships with React Native 0.79.x which pulls metro ~0.82.
metro 0.82+ still exports ./src/* in its package.json exports field,
which @expo/cli v0.24 requires. metro 0.84 removed this export,
breaking expo export (ERR_PACKAGE_PATH_NOT_EXPORTED).

Also removes stale patch scripts (patch-metro-exports.js, check-metro.js)
that are no longer needed with the compatible metro version.
@Chidubemkingsley Chidubemkingsley force-pushed the Add-disaster-recovery-automation-with-runbooks branch from f567c29 to 1662405 Compare June 2, 2026 12:53
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.

Add disaster recovery automation with runbooks

2 participants