Insert text into rich-text editors with insertText
2026-11-11 · 02:15Adds an insertText action so Reticle can type into Tiptap, ProseMirror and other rich-text editors, where fill and type were refused and press inserted nothing.
A running record of work done — projects, open-source contributions, feature additions, fixes, and infrastructure changes.
Adds an insertText action so Reticle can type into Tiptap, ProseMirror and other rich-text editors, where fill and type were refused and press inserted nothing.
Shared saved views expose a calendar feed.
paramInfo now reports the accepted values of every enum parameter. It reads them off the enum that enforces them, the same way it already reads numeric bounds off the number that enforces them, so the shown values cannot drift from the checked ones.
Adds a Delete for completed issues action to the inbox. It deletes notifications for completed and canceled issues, including unread ones, after a confirmation dialog.
Adds task-list checkboxes to issue descriptions.
The platform reverted to the original local Kafka and schema registry settings, removing the Confluent-specific configuration from several services. Unused Kafka entries were cleaned from application files and an audit service policy was added, while the infrastructure repository updated Kafka settings. These changes simplify local development and ensure the services run with the intended Kafka setup.
Adds an Upload Markdown button to the Docs header. Selecting a .md or .markdown file creates a page whose title is the file name without the extension and whose content is the file text, then opens it in the existing Markdown editor.
The portal introduced a global router with pending and error components, unified error mapping to toast notifications, and an EmptyState component for tables and lists, improving error visibility and handling across all views. The UI was rebranded from Vantage to Arya Banking, updating brand assets, meta tags, mock user domains, and disabling search indexing, which aligned the portal's appearance with the product name and removed demo references.
The portal removed the Lovable AI error reporting, CLI assist, and AI review panel components. This eliminated unused AI functionality and simplified the codebase, reducing maintenance overhead. Users no longer see AI-related UI elements or error reports.
A command line shell with login support was added to the portal, allowing terminal-based interaction. AI-powered CLI suggestions and an AI review panel for approvals were integrated, improving productivity and decision support. Multi-factor authentication was added to the sign-in flow, strengthening security.
Finished KafkaAdminController in admin-service: POST /api/admin/topics (create) and GET /api/admin/topics/describe alongside listing, backed by lazy AdminClientManager, TopicListing/TopicDescription mappers, 5s timeouts, and ResponseDto success envelope with TopicCreationException (TOPIC_CREATION_FAILED_400) on failure. Shipped arya-banking-common 2.0.2 (ResponseDto, TopicCreationException) and arya-banking-bom 2.0.2; admin-service now on BOM 2.0.2 with kafka, mongo, kafka-clients and vault-config deps. Added kafka-ops → ROLE_ADMIN and migrated Vault update to @AllowedRoles.
Released arya-banking-common 2.0.1: KafkaConfiguration now forwards security.protocol (SASL_SSL), sasl.mechanism/jaas.config, and Schema Registry basic.auth USER_INFO only when set — local PLAINTEXT keeps working. Removed local docker-compose files; Confluent Cloud is canonical. Bumped arya-banking-bom 2.0.0 → 2.0.1. Onboarded auth-service, user-service and admin-service to spring-cloud-starter-vault-config with Vault confluent.kafka.api/schema placeholders; auth dropped local spring.kafka block in favor of Config Server defaults. Admin added topic-listing endpoint and batch VaultSecretDto (service + List<VaultSecret>).
Migrated arya-banking-configs application.yml from localhost:9092 / :8081 to Confluent Cloud broker (pkc-41p56) + Schema Registry (psrc-81q7m7) with SASL PLAIN / SASL_SSL, session timeout, client.id and USER_INFO Schema Registry auth. Replaced hard-coded SASL password with Vault placeholders, fixed schema auth to use schema.key (was api.key). Gateway routes already on lb:// discovery. Services inherit broker wiring from Config Server and supply only Vault confluent.* keys.
Refactored arya-banking-common from a monolithic Spring Boot app into a multi-module reactor with 5 independent modules: core (domain models, exceptions, DTOs), mongo (MongoDB config), kafka (Kafka/Avro support, Avro IDL schemas), feign (Feign client config), and oauth2 (OAuth2 client credentials). Each module publishes as a separate artifact to GitHub Packages. Removed spring-boot-starter-parent, switched to standalone reactor POM. All 4 consuming services (user, auth, admin, outbox) migrated to use the new modular structure.
Created arya-banking-bom — a standalone Bill of Materials repository that centralizes versions for all 5 common modules, outbox-service, and third-party dependencies (lombok, mapstruct, gson, avro, confluent, commons-io). Imports spring-boot-dependencies and spring-cloud-dependencies BOMs. Services now import the BOM and declare module dependencies without versions. Published v2.0.0 to GitHub Packages.
Extracted MetadataInitializer and MetadataLoaderApplication from arya-banking-common into a separate repository (arya-banking-common-metadata-loader). Standalone Spring Boot app that depends on the core module and runs independently against MongoDB and Vault. No longer bundled in the common library build.
Migrated user-service, auth-service, admin-service, and outbox-service to use arya-banking-bom for dependency management. Updated all Java imports from org.arya.banking.common.* to module-specific packages (core, kafka, mongo, feign). Added build pipelines (build.yml) to all services. Removed SonarCloud analysis workflows. Outbox-service version bumped to 2.0.0.
Added EventContextAop aspect in arya-banking-common to automatically clear ThreadLocal-based EventContext (correlationId, causedEventId) after every @KafkaListener method execution. Eliminates ThreadLocal memory leaks and cross-message context pollution in Kafka consumer thread pools. Enabled @EnableAspectJAutoProxy in user-service. First production AOP aspect shipped across the platform.
Added Kafka event listeners and producers to auth-service: KafkaListenerConfig with @KafkaListener for user events, UserEventProducer for publishing UserCreateEvent and UserLockEvent to Kafka with Avro serialization, and UserUpdateEventListener consuming user update events. Updated KeyCloakServiceImpl with enhanced Keycloak user management. Services now emit and consume user lifecycle events via Kafka topics.
Released arya-banking-common 1.2.3 with new correlation ID utilities: CorrelationIdContext (thread-local correlation ID propagation), EventContext (event processing context holder), EventMetadataFactory (standardized EventMetadata creation with trace IDs), and GsonParser (JSON-Avro parsing helper). Updated EventMetadata.avdl schema and KafkaConstants with new topic definitions. Published to GitHub Packages Maven registry.
Implemented UserEventListeners with @KafkaListener for consuming user events from auth-service. Added UserValidator for input validation. Updated UserServiceImpl to publish UserCreateEvent via transactional outbox pattern when creating users. Integrated with arya-banking-outbox-service for guaranteed at-least-once event delivery. User registration now triggers downstream account creation via event choreography.
Added MethodSecurityConfig with @EnableMethodSecurity for annotation-based access control (@PreAuthorize, @PostAuthorize). Implemented VaultPolicyServiceImpl with CRUD operations for Vault policies (create, read, update, delete, list). Added KeycloakRoleMapperImpl and VaultResponseMapperImpl for DTO mapping. Admin service now enforces role-based access on sensitive operations and manages Vault policies programmatically.
Implemented CorrelationIdGlobalFilter as a Spring Cloud Gateway filter to extract or generate correlation IDs (X-Correlation-ID header) and propagate them downstream to all microservices. Added request/response logging with correlation IDs for distributed tracing. Gateway now acts as the correlation ID entry point for the entire platform.
Created arya-banking-outbox-service v1.0.0 — a Spring Boot starter implementing the transactional outbox pattern. Outbox records persist to MongoDB in the same transaction as the business change, then a scheduled relay publishes to Kafka with bounded retries (PENDING → COMPLETED / RETRY_PENDING → FAILED), guaranteeing at-least-once delivery. Avro events published via OutboxKafkaEvent against Confluent Schema Registry.
Standed up the GitHub Packages Maven registry and published arya-banking-common 1.2.3 and arya-banking-outbox-service 1.0.0 with idempotent deploy workflows — a pre-deploy probe skips re-publishing versions that already exist. Services now consume shared Avro schemas and outbox events as internal artifacts.
Added explicit OpenApiConfig.java to admin-service to stop SpringDoc from auto-generating 'host.docker.internal:8089' as the server URL. Explicit server entries set for API Gateway (8085) and direct (8089).
Audited all 7 service POMs for dependency redundancy, identified scope issues (lombok compile vs provided), missing transitive deps (commons-io, commons-codec), and version drift (SB 3.5.3 vs 3.5.4). Proposed centralized arya-banking-bom and added to platform roadmap.