[QUESTION] How to update application dependencies in app.json to only major.minor (not build/revision) with AL-Go updateDependencies? #1772
Unanswered
ivandjordjevic
asked this question in
Q&A
Replies: 2 comments
-
The Get-BCArtifactUrl is also always returning the more recent version (revisions: 33876 and 33893) than what we have in AppSource at the moment (33834):
cc: @freddydk |
Beta Was this translation helpful? Give feedback.
0 replies
-
I don't believe that is configurable at the moment, no. The updateDependencies setting is really just wrapping some existing bccontainerhelper functionality. As far as I can tell, bccontainehelper doesn't support the functionality you're looking for. The workaround would be to update the version numbers when you are updating the artifact version. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
We’re using the
updateDependencies
setting in AL-Go to update theapp.json
for our apps and specify the correct dependency version. However, the exact version is pulled from the actual BC version used during the CI/CD workflow (where we set the first 26.1 version with"artifact": "//26.1/us/first"
).Is there a way for AL-Go to only update the major and minor version (e.g., 26.1.0.0) for dependencies, while keeping build and revision as 0?
For example:
To only update major and minor:
Beta Was this translation helpful? Give feedback.
All reactions