Add System Application dependency to Test Framework apps#8762
Open
thloke wants to merge 1 commit into
Open
Conversation
Declare an explicit dependency on System Application (63ca2fa4) in the Test Framework library apps (Any, Library Assert, Test Runner, Library Variable Storage). Previously these apps declared no application-level dependency (platform only), so the dependency resolver treated them as compatible across application builds. Tying them to System Application version-gates them to the application, modelling the dependency the same way other first-party apps (e.g. Business Foundation) do. No circular dependency is introduced: the System Application umbrella app declares no dependencies and none of its 111 runtime sub-apps depend on the Test Framework; only the separate System Application Test/Test Library packages consume it, and they sit above the framework in the graph. Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
Contributor
|
Could not find a linked ADO work item. Please link one by using the pattern 'AB#' followed by the relevant work item number. You may use the 'Fixes' keyword to automatically resolve the work item when the pull request is merged. E.g. 'Fixes AB#1234' |
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
1 participant
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.
What
Adds an explicit dependency on System Application (
63ca2fa4-4f03-4f2b-a480-172fef340d3f) to the four Test Framework library apps:Why
These apps previously declared no application-level dependency (platform only). As a result the app dependency resolver treats them as compatible across application builds, so a tenant can end up with a newer build of these apps published than the application schema being applied during an environment upgrade — which blocks the upgrade sync (forward-only schema guard).
Declaring a dependency on System Application version-gates the apps to the application build, modelling the dependency the same way other first-party apps (e.g. Business Foundation) already do.
Circular dependency check
None introduced:
System Applicationapp declaresdependencies: [].System Application/App/depend on any Test Framework app.Test/Test Library/Partner Testpackages, which sit above the framework in the graph.Graph stays acyclic:
System Application (App) -> Test Framework -> System Application Test.Note
Draft / experimental — raised in the context of an upgrade-compatibility investigation. Architectural note: this inverts the conceptual layering (the Test Framework would sit above the entire System Application runtime surface).