GGitHubrelease/v0.7.68 (#698)
| 文件 | 最后提交记录 | 最后更新时间 |
|---|---|---|
chore(release): upgrade to the published v0.7.64 components API (api/composer.json and composer.lock): - fleetbase/core-api ^1.6.63 - fleetbase/fleetops-api ^0.6.69 - fleetbase/ai ^0.0.5 - fleetbase/customer-portal-api ^0.0.14 Console (console/package.json, pnpm-workspace.yaml, pnpm-lock.yaml): - @fleetbase/fleetops-engine ^0.6.69 - @fleetbase/fleetops-data ^0.2.2 - @fleetbase/ember-ui ^0.4.3 - @fleetbase/iam-engine ^0.1.12 - @fleetbase/dev-engine ^0.2.16 - @fleetbase/customer-portal-engine ^0.0.14 - @fleetbase/ai-engine ^0.0.5 The ember-ui and fleetops-data overrides follow. minimumReleaseAgeExclude now lists this release's packages, so they install before the release-age window passes. Submodules move to their release tags: ai, core-api, customer-portal, dev-engine, ember-ui, fleetops, fleetops-data and iam-engine. | 24 天前 | |
release/v0.7.68 (#698) * release: v0.7.68 Version bump and release notes. Component upgrades (api composer, console dependencies, submodules) follow once the module releases are published. * fix(api): stop package:discover from connecting to MySQL during composer install (#695) * fix(api): stop package:discover from connecting to MySQL during composer install AppServiceProvider::configureTransactionTripwire() registered its query listener through DB::listen(). The DB facade resolves the default connection, and the spatial MysqlConnection (fleetbase/laravel-mysql-spatial) opens a PDO handle in its constructor to register Doctrine type mappings, so every boot with DB_TXN_TRIPWIRE_ENABLED=true connected to MySQL - including `artisan package:discover` in composer's post-autoload-dump hook, which fails with a PDOException when the database is not reachable. Subscribe to QueryExecuted through the event dispatcher instead, which is exactly what Connection::listen() does, without resolving a connection. Verified `php artisan package:discover` succeeds with an unresolvable DB_HOST. * chore(api): update fleetbase/laravel-mysql-spatial to v1.0.3 v1.0.3 registers its Doctrine geometry type mappings lazily, so resolving a database connection no longer opens a PDO connection. The DB::listen() change in AppServiceProvider remains as defense in depth; with this release nothing in the boot path can connect to MySQL by merely resolving the connection. * docs(readme): point the screenshot hotlinks at their new names (#697) fleetbase.io renamed its screenshot library onto one convention (fleetbase/fleetbase.io#112). Old paths keep resolving through permanent redirects, so this is tidiness rather than a fix — but the README should link the canonical path. Merge after fleetbase.io#112 is live: until then the new paths do not exist. * chore(release): upgrade to the published v0.7.68 components API (api/composer.json and composer.lock): - fleetbase/core-api ^1.6.68 - fleetbase/fleetops-api ^0.6.71 - fleetbase/storefront-api ^0.4.24 - fleetbase/ledger-api ^0.0.12 composer update without -W, so only these four move in the lock. fleetbase/laravel-mysql-spatial 1.0.3, which core-api 1.6.68 requires, is already locked. Console (console/package.json, pnpm-workspace.yaml, pnpm-lock.yaml): - @fleetbase/ember-core ^0.3.25 - @fleetbase/ember-ui ^0.4.5 - @fleetbase/fleetops-engine ^0.6.71 - @fleetbase/storefront-engine ^0.4.24 - @fleetbase/ledger-engine ^0.0.12 - @fleetbase/iam-engine ^0.1.13 - @fleetbase/dev-engine ^0.2.17 The ember-core and ember-ui overrides follow. minimumReleaseAgeExclude now lists this release's packages. Lockfile refreshed with pnpm 11.0.9. Submodules move to their release tags: core-api, dev-engine, ember-core, ember-ui, fleetops, iam-engine, ledger and storefront. * fix(console): sync app/router.js with router.map.js Admin › API Consumers and Rate Limits (added in v0.7.66) were declared in router.map.js but missing from the committed app/router.js. | 12 天前 | |
release/v0.7.65 (#687) | 18 天前 | |
release/v0.7.68 (#698) * release: v0.7.68 Version bump and release notes. Component upgrades (api composer, console dependencies, submodules) follow once the module releases are published. * fix(api): stop package:discover from connecting to MySQL during composer install (#695) * fix(api): stop package:discover from connecting to MySQL during composer install AppServiceProvider::configureTransactionTripwire() registered its query listener through DB::listen(). The DB facade resolves the default connection, and the spatial MysqlConnection (fleetbase/laravel-mysql-spatial) opens a PDO handle in its constructor to register Doctrine type mappings, so every boot with DB_TXN_TRIPWIRE_ENABLED=true connected to MySQL - including `artisan package:discover` in composer's post-autoload-dump hook, which fails with a PDOException when the database is not reachable. Subscribe to QueryExecuted through the event dispatcher instead, which is exactly what Connection::listen() does, without resolving a connection. Verified `php artisan package:discover` succeeds with an unresolvable DB_HOST. * chore(api): update fleetbase/laravel-mysql-spatial to v1.0.3 v1.0.3 registers its Doctrine geometry type mappings lazily, so resolving a database connection no longer opens a PDO connection. The DB::listen() change in AppServiceProvider remains as defense in depth; with this release nothing in the boot path can connect to MySQL by merely resolving the connection. * docs(readme): point the screenshot hotlinks at their new names (#697) fleetbase.io renamed its screenshot library onto one convention (fleetbase/fleetbase.io#112). Old paths keep resolving through permanent redirects, so this is tidiness rather than a fix — but the README should link the canonical path. Merge after fleetbase.io#112 is live: until then the new paths do not exist. * chore(release): upgrade to the published v0.7.68 components API (api/composer.json and composer.lock): - fleetbase/core-api ^1.6.68 - fleetbase/fleetops-api ^0.6.71 - fleetbase/storefront-api ^0.4.24 - fleetbase/ledger-api ^0.0.12 composer update without -W, so only these four move in the lock. fleetbase/laravel-mysql-spatial 1.0.3, which core-api 1.6.68 requires, is already locked. Console (console/package.json, pnpm-workspace.yaml, pnpm-lock.yaml): - @fleetbase/ember-core ^0.3.25 - @fleetbase/ember-ui ^0.4.5 - @fleetbase/fleetops-engine ^0.6.71 - @fleetbase/storefront-engine ^0.4.24 - @fleetbase/ledger-engine ^0.0.12 - @fleetbase/iam-engine ^0.1.13 - @fleetbase/dev-engine ^0.2.17 The ember-core and ember-ui overrides follow. minimumReleaseAgeExclude now lists this release's packages. Lockfile refreshed with pnpm 11.0.9. Submodules move to their release tags: core-api, dev-engine, ember-core, ember-ui, fleetops, iam-engine, ledger and storefront. * fix(console): sync app/router.js with router.map.js Admin › API Consumers and Rate Limits (added in v0.7.66) were declared in router.map.js but missing from the committed app/router.js. | 12 天前 | |
release/v0.7.68 (#698) * release: v0.7.68 Version bump and release notes. Component upgrades (api composer, console dependencies, submodules) follow once the module releases are published. * fix(api): stop package:discover from connecting to MySQL during composer install (#695) * fix(api): stop package:discover from connecting to MySQL during composer install AppServiceProvider::configureTransactionTripwire() registered its query listener through DB::listen(). The DB facade resolves the default connection, and the spatial MysqlConnection (fleetbase/laravel-mysql-spatial) opens a PDO handle in its constructor to register Doctrine type mappings, so every boot with DB_TXN_TRIPWIRE_ENABLED=true connected to MySQL - including `artisan package:discover` in composer's post-autoload-dump hook, which fails with a PDOException when the database is not reachable. Subscribe to QueryExecuted through the event dispatcher instead, which is exactly what Connection::listen() does, without resolving a connection. Verified `php artisan package:discover` succeeds with an unresolvable DB_HOST. * chore(api): update fleetbase/laravel-mysql-spatial to v1.0.3 v1.0.3 registers its Doctrine geometry type mappings lazily, so resolving a database connection no longer opens a PDO connection. The DB::listen() change in AppServiceProvider remains as defense in depth; with this release nothing in the boot path can connect to MySQL by merely resolving the connection. * docs(readme): point the screenshot hotlinks at their new names (#697) fleetbase.io renamed its screenshot library onto one convention (fleetbase/fleetbase.io#112). Old paths keep resolving through permanent redirects, so this is tidiness rather than a fix — but the README should link the canonical path. Merge after fleetbase.io#112 is live: until then the new paths do not exist. * chore(release): upgrade to the published v0.7.68 components API (api/composer.json and composer.lock): - fleetbase/core-api ^1.6.68 - fleetbase/fleetops-api ^0.6.71 - fleetbase/storefront-api ^0.4.24 - fleetbase/ledger-api ^0.0.12 composer update without -W, so only these four move in the lock. fleetbase/laravel-mysql-spatial 1.0.3, which core-api 1.6.68 requires, is already locked. Console (console/package.json, pnpm-workspace.yaml, pnpm-lock.yaml): - @fleetbase/ember-core ^0.3.25 - @fleetbase/ember-ui ^0.4.5 - @fleetbase/fleetops-engine ^0.6.71 - @fleetbase/storefront-engine ^0.4.24 - @fleetbase/ledger-engine ^0.0.12 - @fleetbase/iam-engine ^0.1.13 - @fleetbase/dev-engine ^0.2.17 The ember-core and ember-ui overrides follow. minimumReleaseAgeExclude now lists this release's packages. Lockfile refreshed with pnpm 11.0.9. Submodules move to their release tags: core-api, dev-engine, ember-core, ember-ui, fleetops, iam-engine, ledger and storefront. * fix(console): sync app/router.js with router.map.js Admin › API Consumers and Rate Limits (added in v0.7.66) were declared in router.map.js but missing from the committed app/router.js. | 12 天前 | |
release/v0.7.68 (#698) * release: v0.7.68 Version bump and release notes. Component upgrades (api composer, console dependencies, submodules) follow once the module releases are published. * fix(api): stop package:discover from connecting to MySQL during composer install (#695) * fix(api): stop package:discover from connecting to MySQL during composer install AppServiceProvider::configureTransactionTripwire() registered its query listener through DB::listen(). The DB facade resolves the default connection, and the spatial MysqlConnection (fleetbase/laravel-mysql-spatial) opens a PDO handle in its constructor to register Doctrine type mappings, so every boot with DB_TXN_TRIPWIRE_ENABLED=true connected to MySQL - including `artisan package:discover` in composer's post-autoload-dump hook, which fails with a PDOException when the database is not reachable. Subscribe to QueryExecuted through the event dispatcher instead, which is exactly what Connection::listen() does, without resolving a connection. Verified `php artisan package:discover` succeeds with an unresolvable DB_HOST. * chore(api): update fleetbase/laravel-mysql-spatial to v1.0.3 v1.0.3 registers its Doctrine geometry type mappings lazily, so resolving a database connection no longer opens a PDO connection. The DB::listen() change in AppServiceProvider remains as defense in depth; with this release nothing in the boot path can connect to MySQL by merely resolving the connection. * docs(readme): point the screenshot hotlinks at their new names (#697) fleetbase.io renamed its screenshot library onto one convention (fleetbase/fleetbase.io#112). Old paths keep resolving through permanent redirects, so this is tidiness rather than a fix — but the README should link the canonical path. Merge after fleetbase.io#112 is live: until then the new paths do not exist. * chore(release): upgrade to the published v0.7.68 components API (api/composer.json and composer.lock): - fleetbase/core-api ^1.6.68 - fleetbase/fleetops-api ^0.6.71 - fleetbase/storefront-api ^0.4.24 - fleetbase/ledger-api ^0.0.12 composer update without -W, so only these four move in the lock. fleetbase/laravel-mysql-spatial 1.0.3, which core-api 1.6.68 requires, is already locked. Console (console/package.json, pnpm-workspace.yaml, pnpm-lock.yaml): - @fleetbase/ember-core ^0.3.25 - @fleetbase/ember-ui ^0.4.5 - @fleetbase/fleetops-engine ^0.6.71 - @fleetbase/storefront-engine ^0.4.24 - @fleetbase/ledger-engine ^0.0.12 - @fleetbase/iam-engine ^0.1.13 - @fleetbase/dev-engine ^0.2.17 The ember-core and ember-ui overrides follow. minimumReleaseAgeExclude now lists this release's packages. Lockfile refreshed with pnpm 11.0.9. Submodules move to their release tags: core-api, dev-engine, ember-core, ember-ui, fleetops, iam-engine, ledger and storefront. * fix(console): sync app/router.js with router.map.js Admin › API Consumers and Rate Limits (added in v0.7.66) were declared in router.map.js but missing from the committed app/router.js. | 12 天前 | |
all dependencies licenses updated | 2 年前 | |
release/v0.7.68 (#698) * release: v0.7.68 Version bump and release notes. Component upgrades (api composer, console dependencies, submodules) follow once the module releases are published. * fix(api): stop package:discover from connecting to MySQL during composer install (#695) * fix(api): stop package:discover from connecting to MySQL during composer install AppServiceProvider::configureTransactionTripwire() registered its query listener through DB::listen(). The DB facade resolves the default connection, and the spatial MysqlConnection (fleetbase/laravel-mysql-spatial) opens a PDO handle in its constructor to register Doctrine type mappings, so every boot with DB_TXN_TRIPWIRE_ENABLED=true connected to MySQL - including `artisan package:discover` in composer's post-autoload-dump hook, which fails with a PDOException when the database is not reachable. Subscribe to QueryExecuted through the event dispatcher instead, which is exactly what Connection::listen() does, without resolving a connection. Verified `php artisan package:discover` succeeds with an unresolvable DB_HOST. * chore(api): update fleetbase/laravel-mysql-spatial to v1.0.3 v1.0.3 registers its Doctrine geometry type mappings lazily, so resolving a database connection no longer opens a PDO connection. The DB::listen() change in AppServiceProvider remains as defense in depth; with this release nothing in the boot path can connect to MySQL by merely resolving the connection. * docs(readme): point the screenshot hotlinks at their new names (#697) fleetbase.io renamed its screenshot library onto one convention (fleetbase/fleetbase.io#112). Old paths keep resolving through permanent redirects, so this is tidiness rather than a fix — but the README should link the canonical path. Merge after fleetbase.io#112 is live: until then the new paths do not exist. * chore(release): upgrade to the published v0.7.68 components API (api/composer.json and composer.lock): - fleetbase/core-api ^1.6.68 - fleetbase/fleetops-api ^0.6.71 - fleetbase/storefront-api ^0.4.24 - fleetbase/ledger-api ^0.0.12 composer update without -W, so only these four move in the lock. fleetbase/laravel-mysql-spatial 1.0.3, which core-api 1.6.68 requires, is already locked. Console (console/package.json, pnpm-workspace.yaml, pnpm-lock.yaml): - @fleetbase/ember-core ^0.3.25 - @fleetbase/ember-ui ^0.4.5 - @fleetbase/fleetops-engine ^0.6.71 - @fleetbase/storefront-engine ^0.4.24 - @fleetbase/ledger-engine ^0.0.12 - @fleetbase/iam-engine ^0.1.13 - @fleetbase/dev-engine ^0.2.17 The ember-core and ember-ui overrides follow. minimumReleaseAgeExclude now lists this release's packages. Lockfile refreshed with pnpm 11.0.9. Submodules move to their release tags: core-api, dev-engine, ember-core, ember-ui, fleetops, iam-engine, ledger and storefront. * fix(console): sync app/router.js with router.map.js Admin › API Consumers and Rate Limits (added in v0.7.66) were declared in router.map.js but missing from the committed app/router.js. | 12 天前 | |
chore(release): upgrade to the published v0.7.64 components API (api/composer.json and composer.lock): - fleetbase/core-api ^1.6.63 - fleetbase/fleetops-api ^0.6.69 - fleetbase/ai ^0.0.5 - fleetbase/customer-portal-api ^0.0.14 Console (console/package.json, pnpm-workspace.yaml, pnpm-lock.yaml): - @fleetbase/fleetops-engine ^0.6.69 - @fleetbase/fleetops-data ^0.2.2 - @fleetbase/ember-ui ^0.4.3 - @fleetbase/iam-engine ^0.1.12 - @fleetbase/dev-engine ^0.2.16 - @fleetbase/customer-portal-engine ^0.0.14 - @fleetbase/ai-engine ^0.0.5 The ember-ui and fleetops-data overrides follow. minimumReleaseAgeExclude now lists this release's packages, so they install before the release-age window passes. Submodules move to their release tags: ai, core-api, customer-portal, dev-engine, ember-ui, fleetops, fleetops-data and iam-engine. | 24 天前 | |
release/v0.7.68 (#698) * release: v0.7.68 Version bump and release notes. Component upgrades (api composer, console dependencies, submodules) follow once the module releases are published. * fix(api): stop package:discover from connecting to MySQL during composer install (#695) * fix(api): stop package:discover from connecting to MySQL during composer install AppServiceProvider::configureTransactionTripwire() registered its query listener through DB::listen(). The DB facade resolves the default connection, and the spatial MysqlConnection (fleetbase/laravel-mysql-spatial) opens a PDO handle in its constructor to register Doctrine type mappings, so every boot with DB_TXN_TRIPWIRE_ENABLED=true connected to MySQL - including `artisan package:discover` in composer's post-autoload-dump hook, which fails with a PDOException when the database is not reachable. Subscribe to QueryExecuted through the event dispatcher instead, which is exactly what Connection::listen() does, without resolving a connection. Verified `php artisan package:discover` succeeds with an unresolvable DB_HOST. * chore(api): update fleetbase/laravel-mysql-spatial to v1.0.3 v1.0.3 registers its Doctrine geometry type mappings lazily, so resolving a database connection no longer opens a PDO connection. The DB::listen() change in AppServiceProvider remains as defense in depth; with this release nothing in the boot path can connect to MySQL by merely resolving the connection. * docs(readme): point the screenshot hotlinks at their new names (#697) fleetbase.io renamed its screenshot library onto one convention (fleetbase/fleetbase.io#112). Old paths keep resolving through permanent redirects, so this is tidiness rather than a fix — but the README should link the canonical path. Merge after fleetbase.io#112 is live: until then the new paths do not exist. * chore(release): upgrade to the published v0.7.68 components API (api/composer.json and composer.lock): - fleetbase/core-api ^1.6.68 - fleetbase/fleetops-api ^0.6.71 - fleetbase/storefront-api ^0.4.24 - fleetbase/ledger-api ^0.0.12 composer update without -W, so only these four move in the lock. fleetbase/laravel-mysql-spatial 1.0.3, which core-api 1.6.68 requires, is already locked. Console (console/package.json, pnpm-workspace.yaml, pnpm-lock.yaml): - @fleetbase/ember-core ^0.3.25 - @fleetbase/ember-ui ^0.4.5 - @fleetbase/fleetops-engine ^0.6.71 - @fleetbase/storefront-engine ^0.4.24 - @fleetbase/ledger-engine ^0.0.12 - @fleetbase/iam-engine ^0.1.13 - @fleetbase/dev-engine ^0.2.17 The ember-core and ember-ui overrides follow. minimumReleaseAgeExclude now lists this release's packages. Lockfile refreshed with pnpm 11.0.9. Submodules move to their release tags: core-api, dev-engine, ember-core, ember-ui, fleetops, iam-engine, ledger and storefront. * fix(console): sync app/router.js with router.map.js Admin › API Consumers and Rate Limits (added in v0.7.66) were declared in router.map.js but missing from the committed app/router.js. | 12 天前 | |
release/v0.7.68 (#698) * release: v0.7.68 Version bump and release notes. Component upgrades (api composer, console dependencies, submodules) follow once the module releases are published. * fix(api): stop package:discover from connecting to MySQL during composer install (#695) * fix(api): stop package:discover from connecting to MySQL during composer install AppServiceProvider::configureTransactionTripwire() registered its query listener through DB::listen(). The DB facade resolves the default connection, and the spatial MysqlConnection (fleetbase/laravel-mysql-spatial) opens a PDO handle in its constructor to register Doctrine type mappings, so every boot with DB_TXN_TRIPWIRE_ENABLED=true connected to MySQL - including `artisan package:discover` in composer's post-autoload-dump hook, which fails with a PDOException when the database is not reachable. Subscribe to QueryExecuted through the event dispatcher instead, which is exactly what Connection::listen() does, without resolving a connection. Verified `php artisan package:discover` succeeds with an unresolvable DB_HOST. * chore(api): update fleetbase/laravel-mysql-spatial to v1.0.3 v1.0.3 registers its Doctrine geometry type mappings lazily, so resolving a database connection no longer opens a PDO connection. The DB::listen() change in AppServiceProvider remains as defense in depth; with this release nothing in the boot path can connect to MySQL by merely resolving the connection. * docs(readme): point the screenshot hotlinks at their new names (#697) fleetbase.io renamed its screenshot library onto one convention (fleetbase/fleetbase.io#112). Old paths keep resolving through permanent redirects, so this is tidiness rather than a fix — but the README should link the canonical path. Merge after fleetbase.io#112 is live: until then the new paths do not exist. * chore(release): upgrade to the published v0.7.68 components API (api/composer.json and composer.lock): - fleetbase/core-api ^1.6.68 - fleetbase/fleetops-api ^0.6.71 - fleetbase/storefront-api ^0.4.24 - fleetbase/ledger-api ^0.0.12 composer update without -W, so only these four move in the lock. fleetbase/laravel-mysql-spatial 1.0.3, which core-api 1.6.68 requires, is already locked. Console (console/package.json, pnpm-workspace.yaml, pnpm-lock.yaml): - @fleetbase/ember-core ^0.3.25 - @fleetbase/ember-ui ^0.4.5 - @fleetbase/fleetops-engine ^0.6.71 - @fleetbase/storefront-engine ^0.4.24 - @fleetbase/ledger-engine ^0.0.12 - @fleetbase/iam-engine ^0.1.13 - @fleetbase/dev-engine ^0.2.17 The ember-core and ember-ui overrides follow. minimumReleaseAgeExclude now lists this release's packages. Lockfile refreshed with pnpm 11.0.9. Submodules move to their release tags: core-api, dev-engine, ember-core, ember-ui, fleetops, iam-engine, ledger and storefront. * fix(console): sync app/router.js with router.map.js Admin › API Consumers and Rate Limits (added in v0.7.66) were declared in router.map.js but missing from the committed app/router.js. | 12 天前 | |
v0.7.46 | 3 个月前 | |
release/v0.7.65 (#687) | 18 天前 | |
release/v0.7.68 (#698) * release: v0.7.68 Version bump and release notes. Component upgrades (api composer, console dependencies, submodules) follow once the module releases are published. * fix(api): stop package:discover from connecting to MySQL during composer install (#695) * fix(api): stop package:discover from connecting to MySQL during composer install AppServiceProvider::configureTransactionTripwire() registered its query listener through DB::listen(). The DB facade resolves the default connection, and the spatial MysqlConnection (fleetbase/laravel-mysql-spatial) opens a PDO handle in its constructor to register Doctrine type mappings, so every boot with DB_TXN_TRIPWIRE_ENABLED=true connected to MySQL - including `artisan package:discover` in composer's post-autoload-dump hook, which fails with a PDOException when the database is not reachable. Subscribe to QueryExecuted through the event dispatcher instead, which is exactly what Connection::listen() does, without resolving a connection. Verified `php artisan package:discover` succeeds with an unresolvable DB_HOST. * chore(api): update fleetbase/laravel-mysql-spatial to v1.0.3 v1.0.3 registers its Doctrine geometry type mappings lazily, so resolving a database connection no longer opens a PDO connection. The DB::listen() change in AppServiceProvider remains as defense in depth; with this release nothing in the boot path can connect to MySQL by merely resolving the connection. * docs(readme): point the screenshot hotlinks at their new names (#697) fleetbase.io renamed its screenshot library onto one convention (fleetbase/fleetbase.io#112). Old paths keep resolving through permanent redirects, so this is tidiness rather than a fix — but the README should link the canonical path. Merge after fleetbase.io#112 is live: until then the new paths do not exist. * chore(release): upgrade to the published v0.7.68 components API (api/composer.json and composer.lock): - fleetbase/core-api ^1.6.68 - fleetbase/fleetops-api ^0.6.71 - fleetbase/storefront-api ^0.4.24 - fleetbase/ledger-api ^0.0.12 composer update without -W, so only these four move in the lock. fleetbase/laravel-mysql-spatial 1.0.3, which core-api 1.6.68 requires, is already locked. Console (console/package.json, pnpm-workspace.yaml, pnpm-lock.yaml): - @fleetbase/ember-core ^0.3.25 - @fleetbase/ember-ui ^0.4.5 - @fleetbase/fleetops-engine ^0.6.71 - @fleetbase/storefront-engine ^0.4.24 - @fleetbase/ledger-engine ^0.0.12 - @fleetbase/iam-engine ^0.1.13 - @fleetbase/dev-engine ^0.2.17 The ember-core and ember-ui overrides follow. minimumReleaseAgeExclude now lists this release's packages. Lockfile refreshed with pnpm 11.0.9. Submodules move to their release tags: core-api, dev-engine, ember-core, ember-ui, fleetops, iam-engine, ledger and storefront. * fix(console): sync app/router.js with router.map.js Admin › API Consumers and Rate Limits (added in v0.7.66) were declared in router.map.js but missing from the committed app/router.js. | 12 天前 |