Prepare 1.7.0 release metadata#166
Merged
Merged
Conversation
|
Test on Playground |
This was referenced Jul 6, 2026
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.
Refs #165
Summary
Base Branch
release/1.7.0fix/165-release-1.7.0-metadataScope
Validation
git diff --checkpassedphp -l perform.phppassedcomposer validate --no-check-publishpassedcomposer lintpassedcomposer phpstanpassednpm run plugin-zippassed and produced a release ZIP with plugin files, built assets, and production vendor filesKnown Proof Gaps
composer check-cscurrently fails on existing repository style findings outside this diff, includingconfig/constants.php, JS config/test files, and module interface spacing. This PR does not touch those files.npm run lintis blocked in this local shell because Node isv16.15.1, while this repo requires Node 24 via.nvmrcand.node-version. CI or a local Node 24 environment should provide the authoritative JS lint proof.696e5ba.Release Notes
release/1.7.0Hard Gates
Final production or beta release actions still require explicit owner approval after the release-ready brief.