RC v0.1.0#185
Draft
jeroenrinzema wants to merge 347 commits intorelease/v0.1.0-rcfrom
Draft
Conversation
…nfigurations Remove unused rate limiting config from providers
* Initial plan * Publish project.created NATS event on project creation - Add EventProjectCreated constant and ProjectEvent schema - Add ProjectEventsProcess subject function - Add StreamProjects and ConsumerProjectEventsProcess constants - Bootstrap project events stream and consumer - Add pubsub.Publisher to ProjectsController - Publish project.created event in CreateProject handler - Add test for NATS event publication on project creation Co-authored-by: jeroenrinzema <3440116+jeroenrinzema@users.noreply.github.com> * Make NATS event publish non-blocking on failure The project is already committed to the database when the NATS event is published, so a publish failure should not fail the HTTP response. Co-authored-by: jeroenrinzema <3440116+jeroenrinzema@users.noreply.github.com> * Publish project.created NATS event on project creation Co-authored-by: jeroenrinzema <3440116+jeroenrinzema@users.noreply.github.com> * Move NATS publish before tx.Commit so failures rollback the transaction The publish now happens inside the transaction scope. If it fails, the handler returns an error and the deferred tx.Rollback() cleans up. Added TestCreateProjectRollbackOnPublishFailure to verify this behavior. Co-authored-by: jeroenrinzema <3440116+jeroenrinzema@users.noreply.github.com> * feat: include more data in project.created event --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: jeroenrinzema <3440116+jeroenrinzema@users.noreply.github.com> Co-authored-by: Jeroen Rinzema <jeroen.rinzema@wellsync.com>
…lity-to-run-journeys
…eview list changes
…n-journeys Feat/ include the ability to run journeys
# Conflicts: # console/src/views/campaign/CampaignDetails.tsx # console/src/views/campaign/setup/Setup.tsx # console/src/views/users/rules/OrganizationEventRuleEdit.tsx
Feat/push notifications
Address PR review issues by removing unsafe raw HTML rendering, preserving valid link schemes, and fixing sticky node sizing defaults/persistence so resizing behaves predictably.
…markup-run-button Fix/journey editor sticky note markup run button
feat(campaigns): add transactional/subscriptions campaigns support
Switch user_subscription.state from integer to VARCHAR with a check constraint. Update code to use 'unsubscribed' string instead of integer constant. Simplify IsUserUnsubscribed logic.
Feat/issue 192
Refactor WASM module build and registry to use a unified internal/integrations/modules directory for both providers and actions. Update Makefiles, Dockerfile, and CI to match. Introduce unified IntegrationManifest and Capability types. Update provider modules to declare capabilities. Refactor action and provider registries to use the new integration loader. Update code and tests for new structure.
Switch rule-generated JSON equality predicates from path extraction to `@>` with `jsonb_build_object` so PostgreSQL can use existing GIN indexes on data columns. Keep `is set` semantics and non-equality operators unchanged, and update query tests to match the new SQL output.
Replace HasProvider and HasActions with ProviderSpec and ActionsSpec checks. Update related logic and tests accordingly. Also unify "Add member" aria-labels in organization members view.
- Move all provider and action modules to a flat `modules/` directory - Update Makefiles and import paths to match new structure - Update integration registry to support unified loading for actions and providers - Update WASM registry facades for providers and actions - Update test WASM binaries - Update router and integration setup in console for new module paths - Update documentation and references to reflect new module locations
…patibility fallbacks
fix(rules): use jsonb containment for data equality filters
feat: improved WASM module architecture into a single module interface
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
First release candidate for Lunogram is taking shape. Feedback welcome.