Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Contributor
🚀 Salesforce CI✅ Deployment succeeded✅ All tests passed📦 Workflow run, logs and artifacts 📊 Stats: 1131 total | ✅ 1131 passed | ❌ 0 failed |
0ptaq0
force-pushed
the
ci/deps-from-sfdx-project
branch
from
September 29, 2026 14:53
7a24959 to
8d4bb30
Compare
This branch was successfully deployed
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.
package/andforce-app/held the same classes (globalvspublic), edited by hand twice, and the vendored SOQL and DML copies had their own version pins. Now the repo keeps one public source and the package is built from it.What changed
force-app/stays the public source people clone and deploy.package/is gone.// globalmarkers. Every declaration that isglobalin the package has a// globalline above it: 122 markers, the same set as the released 0.2.0.scripts/prepare-package.mjsmakes marked declarations global, drops@TestVisibleon them and leaves outdependencies/. On the current code it gives back the releasedpackage/source byte for byte (marker lines aside).force-app/main/default/dependencies/is generated bynpm run build:dependencies: the publicSOQL/DMLclasses and tests at the tags pinned insfdx-project.json(SOQL Lib@6.12.0-1->v6.12.0,DML Lib 4.0.0.LATEST->v4.0.0). One place for dependency versions, and a plain clone still deploys everything.salesforce-ci: deploysforce-appthe way people clone it (withdependencies/), runs the tests, uploads coverage.examples/is not deployed.package-check: runsprepare-package.mjs, deploys SOQL Lib and DML Lib from their tags, then the package form, and runs the tests. A missing marker fails here, not at release.dependencies: fails whendependencies/does not matchsfdx-project.json.sf package version create. The summary shows the new 04t and the alias to add.codecov.ymlignoresdependencies/andexamples/..prettierignore:dependencies/(kept verbatim) andREADME.md(prettier turns its Apex blocks into 2-space, 80-column code).Worth a look
// globalabove the declaration. Other options were a list of declarations in the script (the async-lib way) or splitting API and internals into separate files.dependencies/now comes verbatim from the tags, soSOQL_Test/DML_Testlose the localtestForand use the deps'apiVersion66.0.ci.ymlback tocicd-template@mainonce feat: deploy dependencies from sfdx-project cicd-template#6 is merged, and droptemplate-ref.