Conversation
Contributor
|
For this to work, I think we might also need to explicitly give a version for |
Contributor
Author
|
Sounds right. |
This branch has not been 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.
Enable Release Please's
node-workspaceplugin to make release generation aware of workspace package dependencies.Problem
Dashboard depends on both
workflows-libandrelay-workflows-lib, but Release Please currently treats these packages independently.This means changes in the shared libraries can affect Dashboard functionality without triggering a new Dashboard release. As a result, no new Dashboard image is published and there is nothing new for ArgoCD to deploy.
Solution
Enabled the
node-workspaceplugin so Release Please can understand the dependency relationships between workspace packages.Expected behaviour:
workflows-liborrelay-workflows-libcan trigger a Dashboard version bump when appropriate.