Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Only check plugin version integrity in deployment workflow if the plugin actually requires to be deployed #1666

Open
wants to merge 2 commits into
base: trunk
Choose a base branch
from

Conversation

felixarntz
Copy link
Member

Summary

See #1664: This PR attempts to properly fix the underlying issue: We shouldn't check the version integrity of plugins that do not need deployment during the deployment workflow.

Therefore, this PR moves that check after the conditional for whether a deployment is needed. This will still catch problems for any plugins that need to be deployed, but ignore problems from other plugins (which may temporarily exist, and that's okay).

The PR also effectively reverts the short-term fix from #1664, re-including those future changelog entries, as they should no longer be a problem after this.

@felixarntz felixarntz added [Type] Bug An existing feature is broken Infrastructure Issues for the overall performance plugin infrastructure no milestone PRs that do not have a defined milestone for release labels Nov 18, 2024
Copy link

github-actions bot commented Nov 18, 2024

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: felixarntz <[email protected]>
Co-authored-by: westonruter <[email protected]>
Co-authored-by: mukeshpanchal27 <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

Copy link
Member

@mukeshpanchal27 mukeshpanchal27 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the PR. LGTM. Left one non-blocking feedback.

@@ -101,6 +98,10 @@ jobs:

echo "deploy=true" >> $GITHUB_OUTPUT

- name: Check plugin version integrity
if: steps.check-deployment.outputs.deploy == 'true'
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not blocker: Instead of adding if: steps.check-deployment.outputs.deploy == 'true' condition in every steps can we add new step if output is not true the exit and remove condition from all other steps below?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not sure how that would work in GitHub Actions. Maybe it's possible, but I'm not sure there's a way to properly exit out of a GitHub workflow. Do you have an idea about it?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Infrastructure Issues for the overall performance plugin infrastructure no milestone PRs that do not have a defined milestone for release [Type] Bug An existing feature is broken
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants