Skip to content

Conversation

@desrosj
Copy link
Member

@desrosj desrosj commented Dec 12, 2025

This updates the wporg/wporg-mu-plugins and wporg/wporg-parent-2021 dependencies in Composer.

When running yarn setup:tools for the first time, the command will fail due to the pinned commit hashes being removed from these repositories.

It seems like this can happen through rebases, but it's not clear why this is happening for these two repositories.

This is a more targeted change than #549, which seems to run composer update without limiting the command to specific dependencies. I am only seeing these two repositories causing failures. The other dependencies should likely be upgraded more intentionally.

This updates the `wporg/wporg-mu-plugins` and `wporg/wporg-parent-2021` dependencies in Composer.

When running `yarn setup:tools` for the first time, the command will fail due to the pinned commit hashes being removed from the repository.

It seems like this can happen through rebases, but it's not clear why this is happening for these two repositories.
@desrosj desrosj self-assigned this Dec 12, 2025
@desrosj
Copy link
Member Author

desrosj commented Dec 12, 2025

Looks to also be related to #514.

This adjusts the `composer install` command in `setup:tools` to include `|| composer update 'wporg/*`.

This matches the command used in the GitHub Actions `build.yml` workflow and allows the script to continue when commit SHA values disappear.
@desrosj
Copy link
Member Author

desrosj commented Dec 12, 2025

While working on something else, I noticed that build.yml has the following line:
composer install || composer update wporg/*

I've added this || command to the setup:tools script, which should solve the problem for any wporg-* repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants