Repository navigation
Release v0.7.1 - #430
Merged
Merged
Release v0.7.1#430
Conversation
…vel 12 stack The Laravel 12 release has shipped and fleetbase's Laravel 12 branch is gone, so the l12 stack can no longer be checked out and the contract fails before booting. The file is restored to its content before the l12 stack changes.
MySQL does not roll back DDL. The v0.8.0 production deploy failed at order_configs, after order_offers, driver_ratings and the orders columns had been created, so a re-run would fail on "table already exists". Each table and column is now created only if missing, and down() drops only what exists.
fix(migrations): make the adhoc dispatch migration safe to re-run
ci(contract): restore the contract workflow as it was before the Laravel 12 stack
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #430 +/- ##
===========================================
Coverage 100.00% 100.00%
Complexity 14702 14702
===========================================
Files 676 676
Lines 51313 51313
===========================================
Hits 51313 51313
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
MySQL 8.4 turns on restrict_fk_on_non_standard_key by default, and then rejects any ALTER of a parent whose foreign keys point at a non-unique key with "1553 Cannot drop index '<unknown key name>'". order_configs.uuid has a plain index referenced from orders, service_rates and storefront's stores and networks, which is what stopped the v0.8.0 production deploy. Column changes now run with the setting off for the session and restore it afterwards. Where the variable doesn't exist (MySQL 8.0, MariaDB, SQLite) nothing changes.
MySQL 8.4 turns on restrict_fk_on_non_standard_key by default, and then rejects any ALTER of a parent whose foreign keys point at a non-unique key with "1553 Cannot drop index '<unknown key name>'". order_configs.uuid has a plain index referenced from orders, service_rates and storefront's stores and networks, which is what stopped the v0.8.0 production deploy. Column changes now run with the setting off for the session and restore it afterwards. Where the variable doesn't exist (MySQL 8.0, MariaDB, SQLite) nothing changes.
fix(migrations): allow the order_configs change on MySQL 8.4
fix(migrations): allow the order_configs change on MySQL 8.4
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 PR for
v0.7.1. Merging it intomaintagsv0.7.1throughrelease.yml.Merge order
main.Then the root app's lock needs
fleetbase/fleetops-api0.7.1 before the next deploy.