v2.0.1

• Docs: the documented setSourceNamespaces() migration registration does not
  find the bundled migration and never has — yiisoft/db-migration matches the
  PSR-4 map by string prefix and resolves into the core package, so
  ./yii migrate:up exits 0 having created nothing. Both READMEs now say so and
  give a working Injector-based recipe until the upstream fix ships.

v2.0.0

Breaking. See UPGRADE.md — an installation that already
applied the migration must rewrite one row in the migration table.

• The bundled migration moved to Rasuvaeff\Yii3FeatureFlagsDb\Migration\M260605000000CreateFeatureFlagsTable
  (src/Migration/, PSR-4 autoloaded) from a global class in migrations/.
  Register it with setSourceNamespaces() instead of a vendor/ path. Being
  autoloadable is what makes it safe to reference in DI at all: with the old
  global class, adding any container definition for it made
  Yiisoft\Di\Container fatal at build time in every request, because
  new ReflectionClass() ran before the migration runner had required the file.
• The documented way to rename the table never worked.
  M...::class => ['__construct()' => ['table' => ...]] is ignored:
  yiisoft/db-migration builds migrations through Injector::make(), which
  resolves arguments by name or type from the container and does not read
  definitions keyed by the migration's class — and a scalar string $table has
  no type to resolve. Users following the README silently got the default name.
• The table name is now a typed value object that Injector can resolve,
  built by config/di.php from params. One source of truth: the migration and
  DbFlagProvider cannot disagree any more (in 1.x the runtime read params while the
  migration used its own default, so configuring params pointed the runtime at a
  table the migration had never created).
• New table_prefix param, prepended to table — a single place to keep
  package tables out of the way of an application's own.
• DbFlagProvider validates the table name (through the same value object) —
  in 1.x it interpolated whatever string it was given straight into the query
  builder, with no identifier check at all.
• The row mapper's integer check is anchored with \z instead of $: PCRE's
  $ also matches before a trailing newline.
• Bump rasuvaeff/property-testing to ^2.6.

v1.0.1

• Add /benchmarks and /Makefile to .gitattributes export-ignore.

All notable changes to this project will be documented in this file.

The format is based on Keep a Changelog,
and this project adheres to Semantic Versioning.

• Migrate test suite from PHPUnit to Testo. Internal change, no public API impact.

v1.0.0

• Initial stable release.
• DbFlagProvider and CachedFlagProvider now implement
  Rasuvaeff\Yii3FeatureFlags\WritableFlagProvider (new in core 1.0.0):
  • save(Flag) — upsert keyed by flag name.
  • remove(string) — idempotent delete.
  • CachedFlagProvider is write-through: after delegating to a writable inner
    provider it clears its cache; on a read-only inner it is a silent no-op.
• FlagRowMapper::encodeEnvironments() (new public static method) is the
  inverse of extractEnvironments() and is used by DbFlagProvider::save().
  The two are round-trip compatible.
• DbFlagProvider::toRow() normalises salt to '' when it equals the flag
  name to preserve the emptySaltFallsBackToName invariant on read-back.
• config/di.php now binds WritableFlagProvider::class to the same instance
  as FlagProvider::class via Yiisoft\Definitions\Reference. One key, one
  vendor — no Duplicate key conflict with the core.
• Requires rasuvaeff/yii3-feature-flags ^1.0 and adds yiisoft/definitions ^3.0.
• FlagRowMapper now wraps \InvalidArgumentException from core (both
  InvalidFlagNameException for name and plain InvalidArgumentException
  for rollout range) into InvalidFlagRowException.