QBCore breaking-change review checklist
QBCore has multiple independently changing repositories. Determine breakage from the exact Git diff between your deployed commit and target commit.
Review in this order
fxmanifest.lua: dependencies, shared/client/server file order, Lua/runtime requirements.- Config and locale files: renamed keys, changed defaults, new required values.
- Shared data: job, item, vehicle, weapon, gang, and location shape changes.
- Exports/events/callbacks: name, side, argument, return, and authorization changes.
- SQL: tables, columns, constraints, defaults, and data conversion.
- Dependent resources: every consumer of the changed surface.
Acceptance evidence
Document the compared commits, affected integrations, database dry run, focused smoke tests, performance measurement, and rollback result. Absence of a release note is not evidence that a diff is backward compatible.
Found an issue in this guide?
Send the page URL, the affected example, and a source or reproduction to the site maintainer. For a server or resource problem, use the support guide.
QBCore v1 to v2 Migration
Move an older QBCore server toward current upstream commits without relying on a nonexistent universal v2 branch.
Resource Update Guide
Work through a QBCore resource update with a recorded baseline, config conflict resolution, staging acceptance tests and a recoverable rollback.
