Feature/savings insights contributions

[teethaking]

Closes #895

Overview

---

This PR implements API versioning for the Nestera backend using a URI-based versioning strategy. The goal is to support backward compatibility and enable future breaking changes without affecting existing consumers.

Changes Made

---

API Versioning Strategy

• Adopted URI-based versioning ("/v1", "/v2", etc.) as the standard versioning approach.
• Established a scalable structure for introducing future API versions.

Backend Updates

---

• Configured API versioning middleware within the NestJS application.
• Migrated all existing API endpoints to the "/v1" namespace.
• Ensured existing functionality remains unchanged under the new versioned routes.

Documentation

• Added API version information to the project documentation.
• Documented the versioning strategy and guidelines for future versions.

---

Deprecation Policy

---

• Introduced an API version deprecation policy outlining:
  • Version support timelines
  • Deprecation announcements
  • Removal procedures for outdated versions

Frontend Integration

---

• Updated frontend API calls to consume versioned endpoints ("/v1/*").

Acceptance Criteria Checklist

---

• Design versioning strategy (URI-based)
• Implement versioning middleware
• Migrate existing endpoints to "/v1"
• Create version deprecation policy
• Add version to API documentation
• Update frontend to use versioned endpoints

Testing

---

• Verified all existing endpoints are accessible through "/v1".
• Confirmed frontend requests successfully communicate with versioned APIs.
• Ensured no regressions in existing API functionality.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
nestera	Skipped		Jun 2, 2026 7:31am