Repository navigation
Releases
Releases · Staxless/staxless
v2.26.0
v2.25.10
What's New (25 Features, 10 Fixes since v2.0.0)
Frontend Features
- Replace home page with 17 modular sales components
- Add centralized user context for auth state management
- Add settings dialog with account and subscription sections
- Add error and not-found pages with brand styling
- Add comprehensive loading states with skeletons
- Enhance magic link auth flow with proper UX
- Add centralized error handling system
- Simplify checkout and pricing with unified layout
- Optimize logout with instant redirect and clear state
- Update dashboard settings components
- Update UI components with brand config styling
- Update auth forms and provider hook
- Update middleware with improved route handling
- Add favicon, logo image, and SVG icon for branding
- Update Tailwind CSS configuration
- Add TypeScript interfaces for cookie store management
Backend Features
- Update Kong gateway routes and service configuration
- Update auth-service magic link and OAuth configuration
- Refactor OAuth providers with secrets manager and enhanced security
- Implement secure secret loader with caching for production
- Add health check endpoint
- Enable prefetch admin dashboard to reduce cold starts
- Implement blog post functionality
- Add subscription support alongside one-time payments
- Add production deployment infrastructure with GitHub Actions
Bug Fixes
- Update @staxless/cli dependency to ^2.0.1
- Resolve RSC serialization errors and email service issues
- Fix API gateway URL environment variable for production
- Correct mobile menu brand config
- Correct waitlist brand config
- Correct API path
- Fix Tailwind path for global CSS file
- Correct regex to include base route
- Restore deleted code from linting
- Reset brand config to template
Documentation
- Update README to match staxless-cli style
v2.0.0
2.0.0 (2025-06-25)
🚀 Major Release: Event-Driven Architecture Overhaul
This release marks a significant milestone for the Staxless platform, transitioning our core backend services (auth-service, email-service, stripe-service, and user-service) to a robust, event-driven architecture powered by Apache Kafka. This overhaul replaces synchronous API-based communication with asynchronous Kafka topic-based event production and consumption, enhancing scalability, decoupling services, and improving fault tolerance. This is a breaking change, requiring updates to client integrations and service configurations to align with the new event-driven model.
✨ Features
- Event-Based Architecture Transition (2a3b6d4)
- auth-service:
- Refactored
MagicLinkProviderto produce magic link email events to theauth.magic-linktopic, replacing direct email sending. - Reworked session validation and user logout handlers to consume events from
auth.session.validateandauth.logouttopics, eliminating direct API endpoints. - Added Kafka client configuration with producer and consumer utilities in
kafka/client.js. - Implemented a dedicated authentication event consumer for processing Kafka messages.
- Updated server initialization to start the authentication event consumer.
- Refactored
- email-service:
- Removed email-related API routes, adopting Kafka-based event consumption for magic link emails.
- Added Kafka client configuration and consumer functions in
kafka/email-consumer.js. - Developed a handler for processing
auth.magic-linktopic events. - Updated server initialization to start the email event consumer.
- stripe-service:
- Integrated Kafka for payment events, producing subscription updates to the
stripe.subscription.updatetopic. - Added Kafka client configuration and producer functions in
kafka/stripe-producer.js. - Modified webhook handling to emit events to Kafka instead of direct processing.
- Updated server initialization to start the user event consumer.
- Integrated Kafka for payment events, producing subscription updates to the
- user-service:
- Transitioned subscription update processing to consume
stripe.subscription.updatetopic events. - Added Kafka client configuration and consumer functions in
kafka/user-consumer.js. - Implemented a handler for processing subscription update events.
- Updated server initialization to start the user event consumer.
- Transitioned subscription update processing to consume
- auth-service:
🐛 Bug Fixes
- Admin Route Correction (43cef73)
- Updated the admin route destination to use the correct port, ensuring proper routing and accessibility.
⚠️ BREAKING CHANGES
- Event-Driven Architecture:
- Replaced direct API calls with Kafka-based event-driven communication across all services. Clients relying on synchronous API endpoints for magic link emails, session validation, logout, or subscription updates must now interact with Kafka topics or adapt to the event-based flow.
- Action Required:
- Update client integrations to handle Kafka-based events.
- Configure services with Kafka broker details (e.g.,
bootstrap.servers,group.id) and topic subscriptions. - Deploy all services simultaneously to avoid communication mismatches.
- Ensure Kafka brokers are accessible and topics (
auth.magic-link,auth.session.validate,auth.logout,stripe.subscription.update) are created with appropriate partitions and replication factors.
📝 Deployment Notes
- Verify Kafka broker connectivity and topic creation before deployment.
- Update environment variables with Kafka broker details and consumer group IDs.
- Monitor consumer lag and topic partitioning post-deployment to ensure performance.
- Review updated documentation for guidance on the new event-driven flow.
v1.40.0
v1.39.0
v1.38.0
1.38.0 - 2025-06-12
🚀 Features
- Automated CI/CD Releases: Implemented setup for automated CI/CD releases using GitHub Actions. (b5f525b)
Full Changelog: v1.37.2...v1.38.0
Release v1.37.2: Merge pull request #16 from Staxless/dev (Cumulative)
Changelog v1.37.2
What's Changed
🚀 Features & Enhancements
- Development Updates: Incremental improvements and bug fixes to core functionality. (@zacharybenson in #9)
- Project Structure Refactor: Enhanced project structure with API Gateway integration and improved monitoring capabilities. (@zacharybenson in #10)
- New Features & Branding: Added new application features, updated branding, and improved documentation. (@zacharybenson in #11)
- Development Updates: Further development enhancements and optimizations. (@zacharybenson in #12)
- Development Updates: Additional improvements to core systems and performance. (@zacharybenson in #13)
- Authentication Enhancements: Introduced magic link authentication and dynamic container naming for improved user experience. (@zacharybenson in #14)
- TypeScript Migration: Converted microservices to TypeScript for better type safety and maintainability. (@zacharybenson in #15)
- TypeScript Conversion Continued: Further advancements in TypeScript migration for microservices. (@zacharybenson in #16)
📚 Full Changelog
- Compare changes: v1.37.0...v1.37.2