Dependencies satisfied by higher version, but unpublish not allowed
Nobody has claimed this yet.
- Dominant language
- PowerShell
- Stars
- 881
- Forks
- 285
- Avg merge
- 3d 36m
- Merged PRs (30d)
- 1
Description
Describe the bug
If I have two apps. Main 1.0 and Library 1.0. Main 1.0 depends on Library 1.0. If I upgrade Library 1.0 to Library 1.1 I can not unpublish Library 1.0 because it is required by Main 1.0 although the dependency would still be satisfied by having Library 1.1 present.
The error I get is this:
The Extension cannot be unpublished because it is required by the following apps: <...>
To Reproduce
- Publish & install
Library 1.0 - Publish & install
Main 1.0that has a dependency onLibrary 1.0 - Publish & install
Library 1.1 - Try to unpublish
Library 1.0: this step fails
Expected behavior
I expect Library 1.0 to be able to unpublish without problems since - following the principles of minimum version, no breaking changes and backward-compatibility - Library 1.1 must be fully compatible with Library 1.0 and as such Main 1.0 does no longer need Library 1.0 because Library 1.1 is there.
5. Versions:
- AL Language: v5.0.288712
- Business Central Platform: 16.0.14073.14195
- Business Central Application: 16.3.14085.14363
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No source file, test, or entry point is named. Start by reproducing the four-step publish/install/unpublish sequence using the listed Business Central and AL Language versions, then trace the dependency check involved in unpublishing Library 1.0. Done means Library 1.0 can be unpublished while Library 1.1 satisfies Main 1.0's dependency.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- vscode
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100