v1.7.1

What's Changed

Patches

• Add rush update to wf publish npm
• Support UUID contains and beginsWith filters

Updates

• Added tests for partition key generation functions and removed the unused partitionKeyForIndexByEntity function from the Azure provider

Others

Also documentation has been updated

Pull requests

• doc: Fix unit tests commands in CONTRIBUTING by @NickSeagull in #1317
• doc(cicd): Document the CI/CD process by @NickSeagull in #1309
• build(deps): Bump http-cache-semantics from 4.1.0 to 4.1.1 in /website by @dependabot in #1330
• Added tests for partition key generation functions by @javiertoledo in #1360
• Added beta disclaimer to the ask-me page in the docs by @jfsagasti in #1363
• Add provisional ask me logo by @jfsagasti in #1365
• Visibilized Ask AI bot and improved UX by @jfsagasti in #1366
• Fix import path (Github Action failing) by @jfsagasti in #1367
• Reset changes and fix import by @NickSeagull in #1368
• Revert "Reset changes and fix import" by @NickSeagull in #1369
• Update Ask AI copy by @jfsagasti in #1370
• Add new AskToAI service URL by @adrian-lorenzo in #1371
• Add new URL for analytics by @adrian-lorenzo in #1372
• New PrivateGPT design + little UI improvements by @jfsagasti in #1373
• Test change for VPN compatibility by @jfsagasti in #1375
• Answer reaction by @damienvieira in #1374
• Updated docs for azure provider setup to keep it up with API changes. by @JYCabello in #1380
• Add GitHub workflow and action to update AI Assistant by @damienvieira in #1386
• Updated rockets documentation by @javiertoledo in #1387
• Move Azure region to East US by @gonzalogarciajaubert in #1396
• Action azure region east us (workflows) by @gonzalogarciajaubert in #1397
• Support UUID contains filters by @gonzalojaubert in #1379
• Add rush update to wf publish npm yml by @gonzalogarciajaubert in #1399

New Contributors

• @JYCabello made their first contribution in #1380

Full Changelog: v1.7.0...v1.7.1

v1.7.0

This release do not introduce API changes, but it includes a significant update of the Booster core logic, including bug fixes and optimizations:

• An exception raised in a reducer no longer stops the entire event pipeline (Solving #1254)
• Now, when a reducer can't process an event, the entity reduction process is stopped and logged. Events represent already committed changes that can't be rejected, so a failing event reducer is considered a bug that needs to be fixed. Once the bug is fixed, Booster will retry the failing events and continue, making it easier to recover from failures.
• The ways that entity state were calculated when updating read models or responding to a Booster.entity read have been unified.
• Entity snapshots are now calculated lazily and are cached to avoid the same list of events being reprocessed several times. Reprocessing events can still happen in situations of very high throughput, but this operation is idempotent and won't have any effect.
• An eventual failure (i.e., quick network outage) while storing a snapshot will no longer throw an error, as snapshots are just cached data. A new snapshot will be created and cached the next time the entity state is visited.
• The processes to store an event or store a snapshot have been logically separated and are now type checked.

v1.6.2

Minor change to remove the flusher property from the interface of the user-exposed Register object, as this was intended for internal framework use only.

v1.6.1

Azure is no longer tagged as "Experimental" in the documentation and the CLI.

v1.6.0

Now you can create notification events (events that are not associated to any entity)

v1.5.1

Fixed a bug that prevented reading the correct state for migrated read models.

v1.5.0

This release fixes an issue with rockets in the local provider, which allowed only one rocket to be used when a new message arrived. Before, the system used an environment variable to determine which rocket to call. This caused problems when there were multiple rockets, as the variable would get overwritten. The change now asks the provider for the ID of the specific rocket to be called. For local, the ID is provided in the request, while for others, it is still obtained from the environment variable because, in that case, each rocket will provide its own lambda.

v1.4.1

• Now, when Booster CLI commands need to build the user project, Booster will check if a "compile" script is defined in the user's package.json file. It will run it instead of the default "build" script if it exists. This was implemented to improve backward compatibility when upgrading projects created with Booster versions under v1.0.0

v1.4.0

Add register.flush method

v1.3.5

Make CLI error messages more readable