Back

Changelog

v2.100

Releases

February 2026(29)September 2025(1)July 2025(1)June 2025(8)
View on GitHub

What's New in DeRahm

Every merged pull request is a release. This page tracks all changes shipped to DeRahm, from new features and improvements to bug fixes and infrastructure work.

February 2026

v0.4.9
1 weeks ago

Redesign calendar avatars and enable public connection routes

•Redesigned the `CalendarAvatar` component using ghost avatars and a text-dominant hierarchy to improve visual clarity.
•Enabled public access to connection routes, allowing unauthenticated users to view connection-related pages.

[v0 Session](https://v0.app/chat/pksbQa6ojNS)

azide0x37azide0x37
#99
v0.4.8
1 weeks ago

Enable public access to connection routes

•Removed authentication requirements for `/connection` routes to allow public access.
•Updated project configuration in `settings.json`.

[v0 Session](https://v0.app/chat/pksbQa6ojNS)

azide0x37azide0x37
#98
v0.4.7
3 weeks ago

fix: correct typo in showShareLink references

This PR addresses a typo in `showShareLink` references to ensure correct functionality. **Problem/Issue/Goal:**

•References to `showShareLinkDialog` were incorrect due to a typo.

**Fix/Solution:**

•Corrected the typo in `showShareLink` references in three locations.

Chat link: https://v0.app/chat/BiLxlvTWIyG

azide0x37azide0x37
#97
v0.4.6
3 weeks ago

Update project files

This PR includes 30 commits with various updates and improvements. Chat link: https://v0.app/chat/wh25es6JzVn

azide0x37azide0x37
#96
v0.4.5
3 weeks ago

feat: enhance changelog, data handling, and calendar sync

This PR introduces a changelog, enhances data handling and calendar synchronization, and improves the overall user interface. **Problem/Issue/Goal:**

•**Changelog & Versioning:** Needed a clear way to communicate updates and features, ensure public access to documentation, and optimize changelog generation.
•**Data & Backend Reliability:** Encountered issues with DynamoDB credentials, schema consistency, silent data loading failures, and cron secret validation.
•**Calendar Synchronization:** Faced challenges with Google Calendar filtering, iCal duplicate keys, recurring event handling, and general sync robustness.
•**User Experience:** Required layout improvements for better navigation and content visibility on larger screens.

**Fix/Solution:**

•**Changelog & Versioning:** Implemented a version badge and a publicly accessible changelog page, refactored to build-time generation for improved performance.
•**Data & Backend Reliability:** Resolved DynamoDB credential and schema issues, centralized data loading with robust error handling, added debug logging for cron secrets, and updated the data layer for a consistent schema.

+ 3 more lines...

azide0x37azide0x37
#95
v0.4.4
3 weeks ago

feat: enhance changelog, improve data handling, and fix calendar sync

This PR introduces significant improvements to calendar synchronization, enhances data handling robustness, and refactors the changelog system for better reliability and user experience. **Problem/Issue/Goal:**

•Existing DynamoDB configurations led to credential, key schema, and table schema mismatches, affecting data operations.
•The application lacked a version badge and a dedicated changelog page, and existing changelog content was not publicly accessible or prone to runtime errors.
•Data loading mechanisms were susceptible to silent failures, lacking proper error states and diagnostic logging.
•Calendar synchronization (Google Calendar, iCal) suffered from several issues, including incorrect filtering, duplicate key errors, flawed recurring event handling, Blob token retrieval problems, and a lack of robust error handling for API interactions.

**Fix/Solution:**

•**Database & Data Reliability:**
•Resolved DynamoDB credential, key schema, and table schema mismatches.

+ 12 more lines...

azide0x37azide0x37
#94
v0.4.3
3 weeks ago

feat: Implement changelog, improve data handling, and enhance calendar sync

This PR introduces a changelog, significantly improves data handling and stability, and enhances calendar synchronization capabilities. **Problem/Issue/Goal:**

•Lack of a public changelog and version tracking.
•Frequent DynamoDB credential and schema issues on Vercel, leading to instability.
•Silent failures in data loading and lack of clear error states for users.
•Inefficient runtime changelog generation causing potential API errors.
•Inaccurate Google Calendar filtering and synchronization issues, including duplicate key errors and problems with recurring events in iCal.
•Need for better diagnostics for cron secret validation.

**Fix/Solution:**

+ 8 more lines...

azide0x37azide0x37
#93
v0.4.2
3 weeks ago

feat: implement changelog, enhance data, and fix database & iCal

This PR introduces a changelog page, significantly improves data handling, and resolves critical issues related to database schema, credentials, and calendar synchronization. **Problem/Issue/Goal:**

•Lack of a version badge and a centralized changelog for users.
•Inconsistent and error-prone data loading, leading to silent failures.
•Persistent DynamoDB credential and schema mismatches affecting application stability.
•Inefficient changelog generation causing runtime API errors.
•Inaccurate Google Calendar filtering and recurring event synchronization issues.

**Fix/Solution:**

•Implemented a version badge and a dedicated changelog page, ensuring public accessibility.

+ 6 more lines...

azide0x37azide0x37
#92
v0.4.1
3 weeks ago

Update project files

This PR includes 19 commits with various updates and improvements. Chat link: https://v0.app/chat/wh25es6JzVn

azide0x37azide0x37
#91
v0.4.0
3 weeks ago

feat: enhance changelog, improve data handling, and fix database issues

This PR introduces a changelog page, significantly improves data handling and error reporting, and addresses various critical database and credential issues. **Problem/Issue/Goal:**

•Users needed a way to view version history and changes.
•DynamoDB credential and key schema issues were causing deployment and data access problems.
•Data loading mechanisms were prone to silent failures, leading to a poor user experience.
•Certain public-facing content (changelog) was unintentionally restricted.
•Debugging for cron secret validation was insufficient.
•Google calendar integration required specific filtering.

**Fix/Solution:**

+ 8 more lines...

azide0x37azide0x37
#90
v0.3.9
3 weeks ago

feat: Implement changelog, improve data handling, and fix database

This PR introduces a changelog and version badge feature, significantly improves data loading and error handling, and addresses critical DynamoDB configuration and schema issues. **Problem/Issue/Goal:**

•Lack of a clear way to track product versions and changes for users.
•Silent failures in data loading hooks led to an inconsistent user experience.
•Persistent DynamoDB credential and key schema mismatches on Vercel caused data access failures.
•Changelog pages were not publicly accessible, hindering information dissemination.
•Difficulty in diagnosing cron secret validation failures.

**Fix/Solution:**

•Implemented a version badge and a dedicated changelog page, populated by merged PRs.

+ 6 more lines...

azide0x37azide0x37
#89
v0.3.8
3 weeks ago

feat: Implement changelog, enhance data handling, and fix issues

This PR introduces a changelog page, improves data loading and error handling, and resolves several critical issues related to DynamoDB and public access. **Problem/Issue/Goal:**

•DynamoDB credential and schema mismatches were causing application errors.
•The application lacked a public changelog and version tracking.
•Data loading had silent failures, leading to poor user experience.
•Certain public pages and APIs were unintentionally restricted.
•Difficulty diagnosing cron secret validation failures.

**Fix/Solution:**

•Resolved DynamoDB credential issues on Vercel and fixed key schema mismatches.

+ 5 more lines...

azide0x37azide0x37
#88
v0.3.7
3 weeks ago

feat: Implement changelog, enhance data handling, and fix issues

This PR introduces a changelog page, enhances data loading mechanisms, and resolves several backend and access-related issues. **Problem/Issue/Goal:**

•DynamoDB credential and key schema mismatches caused data access and persistence problems.
•Data loading mechanisms were silently failing, leading to an inconsistent user experience and poor error handling.
•The changelog and its API routes were not publicly accessible, hindering information dissemination.
•There was a lack of a dedicated version badge and a comprehensive changelog page for users.
•Issues on the landing page for authenticated users needed to be resolved.

**Fix/Solution:**

•Resolved DynamoDB credential and key schema inconsistencies, including table recreation with the correct composite key.

+ 5 more lines...

azide0x37azide0x37
#87
v0.3.6
3 weeks ago

feat: Add changelog, improve data handling, and fix issues

This PR introduces a new changelog page and version badge, centralizes data loading with robust error handling, and resolves several critical issues to improve application stability and user experience. **Problem/Issue/Goal:**

•DynamoDB credential and key schema mismatches led to application instability.
•Data hooks experienced silent failures, and backend issues were not properly communicated.
•Changelog and related API endpoints were restricted, requiring authentication.
•Lack of a clear way to display application version and recent changes to users.

**Fix/Solution:**

•Addressed DynamoDB credential and key schema issues for improved database reliability.
•Centralized data loading and implemented proper error handling to surface backend failures and provide clear error states.

+ 3 more lines...

azide0x37azide0x37
#86
v0.3.5
3 weeks ago

feat: implement version badge and changelog page

This PR introduces a version badge and changelog page, enhancing transparency and user information, while also addressing critical backend and frontend stability issues. **Problem/Issue/Goal:**

•Lack of clear versioning and change history for users.
•Critical DynamoDB credential and key schema mismatches affecting application stability.
•Inconsistent landing page experience for authenticated users.

**Fix/Solution:**

•Implemented a version badge and a dedicated changelog page, powered by an API route for merged PRs.
•Resolved DynamoDB credential issues on Vercel and corrected key schema mismatches.
•Refined landing page logic by separating hooks for authenticated users.

+ 1 more lines...

azide0x37azide0x37
#85
v0.3.4
3 weeks ago

feat: add version badge and changelog page

This PR introduces new features for version tracking and a changelog, while also resolving a critical credential issue for DynamoDB on Vercel. **Problem/Issue/Goal:**

•DynamoDB operations were failing on Vercel due to credential misconfiguration.
•Users lacked a clear way to identify the current application version.
•There was no centralized location to view release notes or recent changes.

**Fix/Solution:**

•Addressed and resolved DynamoDB credential issues specifically impacting Vercel deployments.
•Implemented a version badge component to display the application's current version.
•Developed a dedicated changelog page, populated by fetching merged PRs, to provide release notes.

+ 1 more lines...

azide0x37azide0x37
#84
v0.3.3
3 weeks ago

fix: resolve DynamoDB credential issues on Vercel

This PR resolves critical DynamoDB credential issues, ensuring proper database functionality on Vercel deployments. **Problem/Issue/Goal:**

•DynamoDB operations were failing due to incorrect or missing credentials when deployed on Vercel.

**Fix/Solution:**

•Implemented a fix to correctly configure and resolve DynamoDB credentials for Vercel environments.
•Ensures stable and reliable database interactions for the application.

Chat link: https://v0.app/chat/wh25es6JzVn

azide0x37azide0x37
#83
v0.3.2
3 weeks ago

feat: implement OpenTelemetry tracing

This PR integrates OpenTelemetry tracing into the Derahm application to enhance observability and corrects an environment variable used for DynamoDB table access. **Problem/Issue/Goal:**

•The application lacked distributed tracing capabilities, making it difficult to monitor request flows and performance.
•Initial attempts to implement tracing had incorrect package imports and configurations.
•An incorrect environment variable name was being used for the DynamoDB table, potentially leading to access issues.

**Fix/Solution:**

•Implemented OpenTelemetry tracing utilities and instrumented critical operations throughout the Derahm app.
•Corrected OpenTelemetry package imports, configurations, and usage within the tracing module.
•Updated all references from `DERAHM_DDB_TABLE` to `DYNAMODB_TABLE_NAME` for accurate DynamoDB table identification.

+ 1 more lines...

azide0x37azide0x37
#82
v0.3.1
3 weeks ago

fix: Update DynamoDB table env var name

This PR corrects the environment variable used for the DynamoDB table name, ensuring proper application configuration. **Problem/Issue/Goal:**

•An incorrect environment variable (`DERAHM_DDB_TABLE`) was being referenced for the DynamoDB table name.
•This could lead to misconfiguration or failure to connect to the correct DynamoDB table.

**Fix/Solution:**

•Updated all references from `DERAHM_DDB_TABLE` to `DYNAMODB_TABLE_NAME`.
•Ensures the application correctly identifies and uses the DynamoDB table name.

Chat link: https://v0.app/chat/4aOaFfkpK7h

azide0x37azide0x37
#81
v0.3.0
3 weeks ago

feat: add custom tracking events and update cron schedule

This PR introduces custom tracking events and updates the cron schedule to enhance monitoring and task automation. **Problem/Issue/Goal:**

•Needed to implement custom tracking for specific events.
•Required an update to the existing cron schedule.
•Needed to add tracking to action links.

**Fix/Solution:**

•Added custom tracking events.
•Updated the `vercel.json` cron schedule.
•Implemented tracking for action links.

+ 1 more lines...

azide0x37azide0x37
#80
v0.2.9
3 weeks ago

feat: Integrate Clerk auth, optimize navigation, and update branding

This PR introduces Clerk for authentication, significantly enhances navigation performance, and updates the application's branding and legal documentation. **Problem/Issue/Goal:**

•Implement a robust and scalable authentication system.
•Resolve existing authentication flow issues like infinite loading states and redirect handling.
•Improve overall navigation performance and layout stability.
•Add essential legal compliance pages (Privacy, Terms of Service).
•Update application branding and design elements.

**Fix/Solution:**

•Integrated Clerk with Google Calendar OAuth, including necessary components and server actions.

+ 7 more lines...

azide0x37azide0x37
#77
v0.2.8
3 weeks ago

fix: Remove route protection and update privacy policy

This PR enhances public access to key information pages and ensures compliance by updating documentation regarding Google Calendar API scopes. **Problem/Issue/Goal:**

•Critical information pages (`/privacy`, `/trust`) were inaccessible to the public due to route protection.
•Debugging components were present and needed removal for a cleaner production environment.
•The privacy policy and documentation did not accurately reflect the Google Calendar API scopes in use.

**Fix/Solution:**

•Removed route protection for `/privacy` and `/trust`, making them publicly accessible.
•Eliminated debug pane and associated logging elements.
•Updated the privacy policy and relevant documentation to correctly detail Google Calendar API scopes.

+ 1 more lines...

azide0x37azide0x37
#79
v0.2.7
3 weeks ago

fix: Remove route protection and debug elements

This PR addresses access restrictions and removes debugging components to streamline the application. **Problem/Issue/Goal:**

•The `/privacy` and `/trust` routes were protected, preventing public access.
•Debugging elements (pane and logs) were present in the application.

**Fix/Solution:**

•Removed route protection for `/privacy` and `/trust` to make them publicly accessible.
•Eliminated the debug pane and associated logs from the application.

Chat link: https://v0.app/chat/Yh1b7xPzKIl

azide0x37azide0x37
#78
v0.2.6
3 weeks ago

feat: Integrate Clerk auth, optimize navigation & add legal pages

This PR integrates Clerk for robust authentication, significantly optimizes navigation performance, and adds essential legal compliance pages. **Problem/Issue/Goal:**

•Existing authentication needed a robust solution, including Google Calendar OAuth.
•Clerk authentication flow had issues with loading states and redirect handling.
•Navigation performance was suboptimal, leading to full page redraws and layout instability.
•Missing critical Privacy and Terms of Service pages for legal compliance.

**Fix/Solution:**

•Integrated Clerk with Google Calendar OAuth, including `ClerkProvider` and middleware.
•Improved Clerk auth flow by removing blocking loading states, using built-in components, and setting proper redirect URLs.

+ 5 more lines...

azide0x37azide0x37
#76
v0.2.5
3 weeks ago

feat: Integrate Clerk auth and enhance navigation

This PR introduces Clerk for user authentication and significantly enhances the application's navigation performance and stability. **Problem/Issue/Goal:**

•Lack of a robust and secure authentication system.
•Inefficient state-based navigation leading to full page redraws and poor performance.
•Existing authentication flow had issues like infinite loading states and improper redirect handling.
•Layout instability and Cumulative Layout Shift (CLS) during navigation.
•Need for Google Calendar OAuth integration.

**Fix/Solution:**

•Integrated Clerk for comprehensive user authentication, including ClerkProvider, middleware, and server actions.

+ 5 more lines...

azide0x37azide0x37
#75
v0.2.4
3 weeks ago

feat: Integrate Clerk auth and optimize navigation

This PR introduces Clerk for user authentication, including Google Calendar OAuth, and significantly enhances application performance by optimizing navigation and routing. **Problem/Issue/Goal:**

•**Navigation Performance:** State-based navigation led to full page redraws and poor performance, especially for the sidebar.
•**Authentication:** Lacked a robust and secure user authentication system with OAuth capabilities (e.g., Google Calendar).
•**Clerk Integration Issues:** Initial Clerk setup faced problems like blocking loading states, incorrect redirect handling, and infinite loading loops.

**Fix/Solution:**

•**Optimized Navigation:** Converted sidebar to URL-based routing and implemented scoped view transitions to prevent full page redraws, resulting in smoother navigation.
•**Clerk Authentication:** Integrated Clerk for user authentication, including `ClerkProvider`, middleware, and server actions for Google Calendar OAuth.
•**Improved Auth Flow:** Refined Clerk's authentication flow by removing blocking loading states, utilizing Clerk's built-in components, and configuring dedicated sign-in/sign-up pages with correct redirect URLs.

+ 2 more lines...

azide0x37azide0x37
#74
v0.2.3
3 weeks ago

feat: Integrate Clerk OAuth and optimize navigation

This PR integrates Clerk for robust user authentication with Google Calendar OAuth and significantly improves navigation performance by optimizing routing and view transitions. **Problem/Issue/Goal:**

•Existing state-based navigation led to full page redraws, impacting performance.
•Lack of a robust and secure user authentication system.
•Clerk authentication flow needed improvements for better user experience and redirect handling.

**Fix/Solution:**

•Optimized navigation by converting the sidebar to URL-based routing and scoping view transitions.
•Integrated Clerk for user authentication, including Google Calendar OAuth, ClerkProvider, middleware, and server actions.
•Improved Clerk auth flow by removing blocking loading states, using built-in components, and creating dedicated sign-in/sign-up pages with proper redirect URLs.

+ 1 more lines...

azide0x37azide0x37
#73
v0.2.2
3 weeks ago

feat: Integrate Clerk OAuth and optimize navigation

This PR introduces Google Calendar OAuth integration and significantly enhances application performance through navigation and routing optimizations. **Problem/Issue/Goal:**

•Existing state-based navigation led to inefficient full page redraws.
•Sidebar navigation and overall routing performance needed improvement.
•A secure and robust authentication solution with Google Calendar OAuth was required.

**Fix/Solution:**

•Implemented Clerk for user authentication, including ClerkProvider and middleware.
•Integrated Google Calendar server actions to support OAuth.
•Optimized state-based navigation to prevent full page redraws.

+ 2 more lines...

azide0x37azide0x37
#72
v0.2.1
3 weeks ago

fix: Optimize navigation and routing performance

This PR optimizes the application's navigation system by transitioning to URL-based routing, significantly improving performance and user experience. **Problem/Issue/Goal:**

•Existing state-based navigation caused full page redraws, leading to performance issues.
•Inefficient navigation negatively impacted user experience.

**Fix/Solution:**

•Converted sidebar to URL-based routing for improved navigation.
•Optimized existing state-based navigation to prevent full page redraws.
•Implemented scoped view transitions to enhance performance.

Chat link: https://v0.app/chat/T5Ts5i9L2PK

azide0x37azide0x37
#71

September 2025

v0.2.0codex
5 months ago

Add support, marketing, and privacy pages

Summary

•add support, marketing, and privacy pages for app store submission
•test support, marketing, and privacy pages

Testing

•`npm run lint`
•`npm test`
•`npx vitest run --coverage` *(fails: Coverage for lines (20.41%) does not meet global threshold (50%))*

https://chatgpt.com/codex/tasks/task_e_68bb609b5f4083249fcd877cc57174e8

azide0x37azide0x37
#70

July 2025

v0.1.9codex
7 months ago

Add calendar integration test

Summary

•test parsing a real calendar file

Testing

•`npm test`

https://chatgpt.com/codex/tasks/task_e_686e7d268ff08324b381c88d2b61c520

azide0x37azide0x37
#69

June 2025

v0.1.8codex
8 months ago

Improve ical.js parsing and add tests

Summary

•fix docs in `public/ical.js`
•preserve original string when throwing duration parse error
•correct comments for the Binary base64 helpers
•add unit tests for `public/ical.js`

Testing

•`npm test --silent`

https://chatgpt.com/codex/tasks/task_e_686146715df88324b3da776e0562e4dd

azide0x37azide0x37
#67
v0.1.7codex
8 months ago

Update color picker props and add tests

Summary

•update `ColorPicker` prop names in `CalendarColorEditor`
•add unit tests for `handleColorChange` covering success, failure and error cases

Testing

•`pnpm test` *(fails: vitest not found)*

https://chatgpt.com/codex/tasks/task_e_686146b1d32c8324904e871b0f5d4739

azide0x37azide0x37
#66
v0.1.6
8 months ago

test configuration tuning

azide0x37azide0x37
#65
v0.1.5codex
8 months ago

Add sync note injection on dispatch

Summary

•inject DeRahm sync note when dispatching iCal events
•set LAST-MODIFIED timestamp on dispatched events
•test dispatch payload modification and failure fallback

Testing

•`pnpm install`
•`npm test`

https://chatgpt.com/codex/tasks/task_e_685e1dc66c308324942d426686c005e9

azide0x37azide0x37
#62
v0.1.4codex
8 months ago

Fix duplicate connection creation

Summary

•stop double create by disabling the form submit
•move the new connection page into a modal so you can add connections directly from the list

Testing

•`pnpm test`

https://chatgpt.com/codex/tasks/task_e_685da691f69c832486bdeff59a8dd9a1

azide0x37azide0x37
#61
v0.1.3codex
8 months ago

Add Vitest coverage report workflow

Summary

•configure Vitest to output coverage info
•run tests on pull requests and post coverage summary

Testing

•`pnpm exec vitest run --coverage.enabled true`

https://chatgpt.com/codex/tasks/task_e_685d568506f88324adec1a4fd227ce65

azide0x37azide0x37
#60
v0.1.2codex
8 months ago

Add progress tracking metrics

Summary

•expand progress store to track success and error metrics
•compute CalDAV diffs before dispatching operations
•record operation results for added, updated, and deleted counts
•show final sync summary in progress indicator
•update tests for new progress logic

Testing

•`npm test`

+ 1 more lines...

azide0x37azide0x37
#55
v0.1.1codex
8 months ago

Implement real CalDAV sync

Summary

•remove simulation restriction from dispatch
•store rule in AGENTS about avoiding simulation
•implement actual CalDAV operations in `/api/sync/dispatch`

Testing

•`pnpm install`
•`pnpm test` *(fails: Test Files 1 failed | 10 passed)*

https://chatgpt.com/codex/tasks/task_e_685c3b6d54c88324845c354ab05f97b3

azide0x37azide0x37
#54

This changelog is automatically generated from merged pull requests in the DeRahm repository.