Skip to content

Changelog

tilttek/luck-tokens-bundle

All notable changes to tilttek/luck-tokens-bundle will be documented in this file.

Updates should follow the Keep a CHANGELOG principles.

0.1.0-alpha - 2026-11-20

Added

  • TilttekLuckTokensBundle and its configuration tilttek_luck_tokens: the store of the ledgers, Doctrine DBAL or memory, and its connection; the rules of the tables from the configuration, the database or a service of the application, the configured tables checked when the container is compiled; the clock; the size of a ledger; who controls the tokens of whom — each holder their own, the security voters, or a service —; the locks; the kind of a member for the privacy bundle.
  • LuckTokens registered with the rules, the ledger, the application's event dispatcher, the access and the clock, so that the events reach the application's listeners.
  • Infrastructure\Doctrine\DbalTokenLedger: the ledgers in tilttek_luck_tokens_entry, the table and the position the primary key, the entries of an operation inserted in one transaction after the last position is read again there, another writer at the same position, a deadlock or a lock timeout answered by LedgerConflict; each balance read from the index of the holder's last entry of the kind, the entries of an operation from an index ordered by position; a member erased under a pseudonym by two updates in one transaction.
  • Infrastructure\Doctrine\DbalTokenRules: the rules of each table as JSON in tilttek_luck_tokens_rules, saved, removed and read back checked.
  • Infrastructure\Doctrine\LuckTokensTables and LuckTokensSchemaListener: the tables added to the schema the ORM generates for their connection, the rules' table only when the rules are kept there; on MySQL and MariaDB, the texts compared byte by byte.
  • Infrastructure\Rules\ConfiguredTokenRules: the rules of the tables of the configuration, read once.
  • Application\LockedLuckTokens and Application\LockScope: the operations under a Symfony lock — of each holder, both holders of a transfer in one order, or of the whole table; the table for a session, the member for an erasure —, released even when the operation fails.
  • Infrastructure\Security\SecurityHolderAccess, HolderControlVoter and HolderControl: the access of actors to holders asked of the security voters, the bundle's voter granting each holder their own tokens and abstaining otherwise.
  • Infrastructure\Privacy\LuckTokensPrivacy: the erasure of a member for phil/privacy-bundle, under their lock when the locks are enabled, reported as pseudonymised.
  • The stores' tests on SQLite, MySQL 8.4 and PostgreSQL 17, four processes granting at once with and without the locks, and a benchmark of a spending after 10 000 entries in the database.
  • The Flex recipe in recipe/0.1: the bundle and config/packages/tilttek_luck_tokens.yaml.
  • The documentation in doc/, one file per topic, indexed by the README.
  • CONTRIBUTING.md, SECURITY.md and CODE_OF_CONDUCT.md.