Repository navigation
Move the wordpress-configs pins to its current trunk - #22
Merged
Merged
Conversation
The template pinned wordpress-configs at 3cbd985, whose release has no archive-entry-file input, so the wordpress.org recipe's step for a plugin that keeps its 1.x main file had to hedge on the configs version, and a plugin generated from the template could not follow it. The 13 workflow refs, package.json's git dependency and both locks move to configs f420c38, which merges the input, and the recipe step drops its hedge. Each lock changes only the configs entry. Assisted-by: Claude Code:claude-opus-5-5
4 of 10 tasks
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.
Summary
The template pinned wordpress-configs at
3cbd985, whose release has noarchive-entry-fileinput, so the wordpress.org recipe's step for a plugin that keeps its 1.x main file had to hedge on the configs version, and a plugin generated from the template could not follow it. This follows #21, which merged before the commit reached it.package.json's git dependency and both locks move to configsf420c38, the merge of Let a release ship the main plugin file under another name wordpress-configs#58. Each lock changes only the configs entry; npm's integrity hash is unchanged, because configs' npm package files did not change.Workflows +13 −13 (7 files),
package.jsonand the two locks +7 −7, docs +1 −1.Type of change
Checklist
composer changelog:add): none; the v2 rebuild ships as "Initial release."composer quality-checkpasses locallyTesting.
composer quality-checkpasses: validate, changelog validation, PHPCS on both profiles, PHPStan, Unit 6 and Integration 81.npm run test:e2epasses (3 of 3), andlint:scripts,lint:styles,lint:types, actionlint, zizmor and shellcheck are clean.