BREAKING CHANGES - nself-org/nchat GitHub Wiki
Version: 0.8.0 Release Date: February 1, 2026
v0.8.0 contains NO breaking changes.
This release is fully backward compatible with v0.7.0. All existing features, APIs, database schemas, and configurations remain unchanged.
Your existing nChat deployment will work without any modifications:
- Web Application: Continues to work exactly as before
- API Endpoints: All existing endpoints unchanged
- Database Schema: No schema migrations required
- Configuration: Existing config files compatible
- User Data: No data migrations needed
- Third-Party Integrations: All integrations work as-is
v0.8.0 adds new platforms and features without modifying existing ones:
New Platforms:
- iOS app (new)
- Android app (new)
- Desktop apps (new)
New Features:
- Offline mode (optional)
- Background sync (optional)
- Mobile-specific APIs (new)
All new features are optional and don't affect existing functionality.
| Component | v0.7.0 | v0.8.0 | Compatible |
|---|---|---|---|
| Web App | ✅ | ✅ | ✅ Yes |
| API | ✅ | ✅ | ✅ Yes |
| Database | ✅ | ✅ | ✅ Yes |
| Config | ✅ | ✅ | ✅ Yes |
| Auth | ✅ | ✅ | ✅ Yes |
| Integrations | ✅ | ✅ | ✅ Yes |
| iOS App | ❌ | ✅ | N/A New |
| Android App | ❌ | ✅ | N/A New |
| Desktop Apps | ❌ | ✅ | N/A New |
Because there are no breaking changes, you can upgrade with zero downtime:
- Deploy v0.8.0 web app (standard deployment)
- No database migrations (schema unchanged)
- No config changes (existing config works)
- No user data changes (data format unchanged)
If you need to rollback for any reason:
- Redeploy v0.7.0 web app
- No database rollback needed (schema unchanged)
- No data cleanup needed (no data changes)
Note: Mobile apps are independent. Rollback doesn't affect mobile users.
None. No features have been deprecated in v0.8.0.
All v0.7.0 features remain fully supported:
- ✅ Web chat interface
- ✅ Channel management
- ✅ Direct messages
- ✅ File sharing
- ✅ Video/audio calls
- ✅ Search
- ✅ Integrations
- ✅ Admin dashboard
- ✅ User management
- ✅ All other v0.7.0 features
None planned for v0.9.0.
We are committed to backward compatibility. Any future deprecations will:
- Be announced at least 2 major versions in advance
- Include migration guides
- Maintain support during deprecation period
- Provide automated migration tools where possible
All v0.7.0 API endpoints work identically in v0.8.0:
// v0.7.0 code works unchanged in v0.8.0
import { useMessages } from '@/hooks/use-messages'
import { useChannels } from '@/hooks/use-channels'
// All existing hooks, utilities, and components work as-isNew optional APIs added in v0.8.0:
// New mobile-specific APIs (optional)
import { offlineSync } from '@/lib/offline-sync'
import { pushNotifications } from '@/lib/push-notifications'
import { biometrics } from '@/lib/biometrics'
// Existing code doesn't need to use these
// They're available if you want mobile featuresThe database schema is identical to v0.7.0:
- Same tables
- Same columns
- Same indexes
- Same constraints
- Same relationships
# No migrations needed
# This would normally run migrations:
pnpm db:migrate
# But there are none for v0.8.0
# Output: "No pending migrations"All v0.7.0 configuration works in v0.8.0:
# v0.7.0 .env file works unchanged
NEXT_PUBLIC_GRAPHQL_URL=...
NEXT_PUBLIC_AUTH_URL=...
# ... all other v0.7.0 configNew optional environment variables for mobile features:
# Optional: Firebase for mobile analytics
NEXT_PUBLIC_FIREBASE_API_KEY=...
NEXT_PUBLIC_FIREBASE_PROJECT_ID=...
# Optional: Sentry for mobile crash reporting
NEXT_PUBLIC_SENTRY_DSN_IOS=...
NEXT_PUBLIC_SENTRY_DSN_ANDROID=...
# Optional: Capacitor app config
CAPACITOR_APP_ID=io.nself.chat
CAPACITOR_APP_NAME=nChatAll are optional. Apps work without them (mobile features disabled).
All major dependencies remain at compatible versions:
- ✅
next@^15.5.10(same major version) - ✅
react@^19.0.0(same major version) - ✅
@apollo/client@^3.14.0(same major version) - ✅ All other core dependencies unchanged
New dependencies for mobile platforms:
{
"@capacitor/android": "^6.2.0",
"@capacitor/ios": "^6.2.0",
"@capacitor-firebase/analytics": "^6.1.0",
"@sentry/capacitor": "^0.18.0",
"@sentry/electron": "^4.19.0",
"detox": "^20.29.3",
"appium": "^2.15.2"
}These don't affect web app. They're only used for mobile/desktop builds.
Web build process unchanged:
# Same build commands as v0.7.0
pnpm build # Works identically
pnpm start # Works identically
pnpm deploy # Works identicallyNew optional build commands for mobile/desktop:
# Optional: Build mobile apps
pnpm ios:build
pnpm android:build
# Optional: Build desktop apps
pnpm electron:build
# These are additive, not required for web deploymentAll v0.7.0 tests work unchanged:
# Same test commands
pnpm test # All tests pass
pnpm test:e2e # All E2E tests passNew optional test suites for mobile:
# Optional: Mobile E2E tests
pnpm test:e2e:ios
pnpm test:e2e:androidWeb users experience no breaking changes:
- ✅ Same UI
- ✅ Same features
- ✅ Same workflows
- ✅ Same performance
- ✅ No retraining needed
Mobile users get new options (opt-in):
- ✅ Download iOS app (optional)
- ✅ Download Android app (optional)
- ✅ Download desktop app (optional)
- ✅ Continue using web app (still fully supported)
- Review release notes (RELEASE-NOTES.md)
- Review features (FEATURES.md)
- Backup database (standard precaution)
- Test in staging (recommended)
- Deploy v0.8.0 web app (standard deployment)
- Verify web app (smoke test)
- Monitor logs (check for errors)
- Verify all features (web app works)
- Check analytics (monitor usage)
- Build mobile apps (optional)
- Distribute mobile apps (optional)
- Redeploy v0.7.0 (simple rollback)
- No data cleanup (no data changes)
- Verify rollback (web app works)
If you encounter any issues:
- Check documentation: docs/releases/v0.8.0/
- Review troubleshooting: TROUBLESHOOTING.md
- GitHub Issues: https://github.com/nself/nself-chat/issues
- Discord: https://discord.gg/nchat
- Email: [email protected]
If you believe you've found a breaking change:
- Verify: Check if it's actually breaking (not just new feature)
- Search: Check existing GitHub issues
-
Report: Create detailed issue with:
- What broke
- How to reproduce
- Expected vs actual behavior
- v0.7.0 vs v0.8.0 comparison
v0.8.0 is a safe, backward-compatible upgrade.
- ✅ No breaking changes
- ✅ No code modifications required
- ✅ No database migrations
- ✅ No configuration changes
- ✅ Zero-downtime deployment
- ✅ Simple rollback if needed
Upgrade with confidence!
Added:
- iOS app (new platform)
- Android app (new platform)
- Desktop apps (new platforms)
- Offline mode (new feature)
- Background sync (new feature)
- Mobile APIs (new APIs)
- Mobile tests (new tests)
- Mobile docs (new documentation)
Modified:
- Nothing (all changes are additive)
Removed:
- Nothing (no features removed)
Deprecated:
- Nothing (no features deprecated)
| Version | Compatible with v0.8.0 |
|---|---|
| v0.7.0 | ✅ Yes (100%) |
| v0.6.0 | ✅ Yes (via v0.7.0) |
| v0.5.0 | |
| <v0.5.0 |
Recommendation: If on v0.6.0 or earlier, upgrade to v0.7.0 first, then v0.8.0.
Questions? Contact [email protected]