Repository navigation
fix: deploy employee agent recipes in two batches - #141
Open
dsorajisto wants to merge 1 commit into
Open
dsorajisto wants to merge 1 commit into
dsorajisto wants to merge 1 commit into
Conversation
A single deploy accepts at most 50 AiAuthoringBundle instances on Summer '26 orgs and 100 on the current release, and each bundle counts twice. force-app has 26 bundles, so deploying it in one go fails on Summer '26 orgs. CI, the install scripts and the README now deploy the shared objects and tabs with 01-03 first, then 04 with the shared app and permission sets. Closes trailheadapps#140
Contributor
Author
|
The scratch-org-test failure is the fork limitation: the job stops at "Populate auth file with DEVHUB_SFDX_URL secret" because PRs from forks don't get repository secrets, so the deploy step never runs. I ran the same steps in a fresh scratch org from my own Dev Hub: both deploy batches, the permission sets, the sample data import, the service agent deploy and all 103 Apex tests passed. |
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 does this PR do?
Deploys the employee agent recipes in two batches. On Summer '26 orgs a single deploy accepts at most 50 AiAuthoringBundle instances (100 on the current release), and each bundle counts twice, so the 26 bundles in
force-appno longer fit in one deploy.shared/objects,shared/tabs,01_languageEssentials,02_actionConfiguration,03_reasoningMechanics(16 bundles)04_architecturalPatterns,shared/applications,shared/permissionsets(10 bundles)shared/objectsandshared/tabsgo first becausereasoningInstructionsusesASR_Order__c. The shared app and permission sets go last because they reference objects and tabs from every category.The change is in
ci.yml,ci-pr.yml,bin/install-scratch.sh,bin/install-scratch.batand the README install steps. A new top-level category folder would need to be added to one of the batches.What issues does this PR fix or reference?
Closes #140
The PR fulfills these requirements:
No tests were added because only deploy commands changed. I ran the full CI sequence in a fresh scratch org instead: both batches, permission sets, sample data import, service agent deploy, and all 103 Apex tests passed.
Functionality Before
sf project deploy start --source-dir force-appfails on Summer '26 orgs with "You attempted to deploy 52 instances of AiAuthoringBundle, more than the maximum limit of 50 allowed by the system."Functionality After
Each batch stays under the limit on Summer '26 and current-release orgs, and every deployable file in
force-appis in exactly one batch.