App Versions
Current version per platform, sourced from each app's package.json/app.json. This is what QA should be testing against right now.
| App | Version | Platform | Notes |
|---|---|---|---|
Mobile App buyootna | 1.1.0 | iOS & Android (Expo SDK ~54.0.33) | Bundle id com.youssefusfdev.buyootna. No buildNumber/versionCode is set in app.json — check the EAS Build dashboard for the actual store build number tied to a given release, don't infer it from this version string alone. |
API api | 0.0.1 | NestJS backend | Not bumped per release. Production deploys automatically on every push to main via the CD pipeline (.github/workflows/cd.yml) — the deployed git commit SHA on main is the real source of truth for 'what's in prod right now', not this version number. |
Web Landing @buyootna/web-landing | 0.1.0 | Next.js (landing.buyootna.cloud) | Static package version, not bumped per deploy. |
Web Companies @buyootna/web-companies | 0.1.0 | Next.js (companies.buyootna.cloud) | Auth-only shell today — see the Web Companies user stories. |
Web Offices @buyootna/web-offices | 0.1.0 | Next.js (offices.buyootna.cloud) | Auth-only shell today — see the Web Offices user stories. |
Web Management @buyootna/web-management | 0.1.0 | Next.js (management.buyootna.cloud) | Auth-only shell today — see the Web Management user stories. |
Web Admin @buyootna/web-admin | 0.1.0 | Next.js (admin.buyootna.cloud) | Most actively developed web portal — see the Web Admin user stories for what's real vs. placeholder. |
Web Docs @buyootna/web-docs | 0.1.0 | Next.js (docs.buyootna.cloud) | This site. |
Versions aren't currently bumped per release — every web app sits at the Next.js scaffold default (0.1.0) and the API at 0.0.1, while only the mobile app's version (1.1.0) reflects real app-store submissions. Because the CD pipeline deploys straight from main on every push, the git commit SHA at deploy time is the actual source of truth for "what's in production" for the API and web apps — reference that commit (not this table) when filing a bug against a specific web/API build. Recommend adopting real semver bumps (or at least deploy-time commit tagging visible in the UI) if precise build-to-bug-report traceability becomes a priority.