Skip nodes where published_version is not present #4321
Merged
Conversation
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
Member
|
@entantoencuanto what's the status of this PR? |
Member
Author
|
It's ready. There is an underlying issue I'm reviewing, this PR fixes the unexpected effects of it so it's ready to merge |
ferblape
approved these changes
Jan 4, 2026
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.
✌️ What does this PR do?
This PR prevents exceptions that happen when a project of a Plan is published but its published version is not set. This should not happen (published without version) but the exception can be prevented since it is related with a scope that should only operate on projects with a published version. The PR causes projects without a published version to be ignored from this scope.
🔍 How should this be manually tested?
👀 Screenshots
Before this PR
After this PR
.env.example?config/application.yml?config/secrets.yml?(Changes in these files might need to update the role in Ansible)
📖 Does this PR require updating the documentation?