Repository navigation
release: v0.1.11 - #42
Merged
Merged
Conversation
purchased.hbs passed @extension, but ExtensionCard reads @resource, so every purchased card rendered with no name or icon, a Free badge, an empty Last Modified, and a click handler that dereferenced undefined. Also fix the card's footer, which read @extension.description and so never showed a description on any page, and rename the misspelled onExtenstionUpdated action to the onExtensionUpdated name its did-update modifier binds.
Console requests in test mode switch database.default and fleetbase.connection.db to sandbox. registry-bridge disables sandbox migrations, so every registry_* table exists only in the live database and the registry endpoints failed with 1146 Table 'fleetbase_sandbox.registry_extensions' doesn't exist. - Pin every model in server/src/Models to the mysql connection. - Resolve RegistryExtension::category() against the live connection. - Run the categories query (Category whereHas registryExtensions) on the live connection, since the whereHas subquery runs on the parent query's connection. - Add a two-connection SQLite harness that switches into sandbox and proves the models and the categories, engines, install status, installed and purchased paths stay on live. - Add laravel/framework ^10 as a dev dependency so the controllers can load in tests, and allow symfony/var-dumper ^6.2 alongside ^5.4. Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Claude <noreply@anthropic.com>
Co-Authored-By: Claude <noreply@anthropic.com>
fix: pass @resource to ExtensionCard on the purchased page
chore(deps): ember-ui 0.4.6 and ember-core 0.3.26
fix: pin registry data to the live connection in sandbox mode
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.
Release v0.1.11. Merging this PR into
maintagsv0.1.11through the release workflow.Included
#41. These fix PRs target this branch; merge them here first.
Part of the Fleetbase Cloud sandbox (test mode) incident fix: core-api v1.6.71, fleetops v0.6.73, billing v0.1.28, internals v0.0.40 and registry-bridge v0.1.11. After all five are tagged, bump them in the fleetbase repo's
api/composer.jsonfor the Cloud deploy. No migrations are needed.The version files and
RELEASE.mdalready name v0.1.11. UpdateRELEASE.mdif anything else lands on this branch.🤖 Generated with Claude Code