v1.1.0 - Goal Improvements: New Fields & Auto-Status

Backend v1.1.0

New Goal Fields

• progress (0-100) — completion percentage
• targetDate — goal target date
• category — enum: HEALTH, FINANCE, LEARNING, TRAVEL, FITNESS, OTHER

Business Logic

• Auto-status update based on progress:
  • 0 → PENDING
  • 1-99 → IN_PROGRESS
  • 100 → COMPLETED

Updated DTOs

• CreateGoalDto → new optional fields
• UpdateGoalDto → new optional fields

v1.0.2 – Goals permissions and ordering fixes

This release improves the goals system by fixing permission logic and ensuring consistent ordering of goals across endpoints.

Fixes & Improvements:

• Fixed goal permissions so partners cannot modify or delete private goals they do not own.
• Enforced editing rules:

• Owners can fully edit their goals.
• Partners can edit shared goals but cannot change structural fields like goal type.
  • Added validation to prevent creating shared goals when no partner is connected.
  • Improved goal update logic to correctly handle switching between PRIVATE and SHARED goals.
  • Ensured consistent goal ordering by returning newest goals first (ORDER BY createdAt DESC).
  • Improved access control checks for viewing, editing, and deleting goals.

These changes make the goals system more secure, predictable, and aligned with the frontend behavior.

v1.0.1 – Production stabilization

Stabilization release for the backend API after the initial v1.0.0 deployment.

Included fixes and improvements:

Goals module

• Fixed goals service logic for personal and shared goals
• Improved goals controller endpoints and request handling
• Added proper validation when creating shared goals without a linked partner
• Fixed goal type update behavior between PRIVATE and SHARED
• Ensured partner assignment is handled correctly when updating goals
• Improved authorization rules so only the owner or linked partner can access a goal
• Fixed reload consistency with goals-related operations

Database and TypeORM

• Updated TypeORM configuration to use DATABASE_URL
• Fixed local database connection issues caused by incorrect environment configuration
• Improved PostgreSQL connection setup for local and production environments
• Added production-aware SSL configuration for Railway/PostgreSQL
• Kept entity autoloading and synchronization aligned with current project setup

API and app configuration

• Improved backend runtime configuration for cloud deployment
• Fixed environment-related issues affecting production stability
• Refined general API behavior for deployed environments

CORS and integration

• Updated CORS configuration to allow proper frontend-backend communication
• Fixed integration issues between deployed frontend and backend services

General stabilization

• Multiple bug fixes after initial production deployment
• Better reliability for deployed API behavior
• General cleanup and stabilization of backend flows