chore(release): v0.6.0#1023
Open
ashleyshaw wants to merge 815 commits into
Open
Conversation
…gin README frontmatter Phase 3 of Wave 5 README audit covers 12 .github subdirectory and plugin README files. - plugins/lightspeed-github-ops/README.md — Add standardized frontmatter - plugins/lightspeed-github-ops/hooks/README.md — Add comprehensive frontmatter - .github/DISCUSSION_TEMPLATE/README.md — Update frontmatter; fix field ordering - .github/ISSUE_TEMPLATE/README.md — Update last_updated; standardize fields - .github/PULL_REQUEST_TEMPLATE/README.md — Update last_updated; standardize fields - .github/SAVED_REPLIES/README.md — Add missing standard fields - .github/metrics/README.md — Remove deprecated references field; update dates - .github/projects/README.md — Fix title mismatch; update frontmatter - .github/reports/README.md — Add comprehensive frontmatter - .github/prompts/README.md — Reconstruct malformed file with proper frontmatter - .github/schemas/README.md — Remove deprecated references field; update dates - .github/instructions/.archive/README.md — Add missing standard fields All Phase 3 files now follow consistent format: - title, description, file_type (documentation) - version, last_updated (2026-05-31), created_date - authors, maintainer (LightSpeed Team), license (GPL-3.0) - tags, domain (governance), stability - All markdown files validated - All frontmatter schema compliant - All internal links verified (where applicable) Relates to #670 Phase 3 completion.
- Fix .github/projects/README.md content mismatch (Reports → Projects) - Simplify redundant relative path segments in .github/prompts/README.md - Ensure all content accurately reflects directory purpose Addresses Gemini code review comments on PR #703.
## Schema Compliance Fixes - Fix invalid stability values: beta → experimental, archived → incubating - Add required 'name' field to discussion_template and issue_template files - Fix broken AUTOMATION_GOVERNANCE link (../ → ../../docs/) - Update projects README to reflect actual directory structure (active, archived) ## Files Fixed - plugins/lightspeed-github-ops/README.md — stability: experimental - plugins/lightspeed-github-ops/hooks/README.md — stability: experimental - .github/prompts/README.md — fix link path, stability: experimental - .github/DISCUSSION_TEMPLATE/README.md — add name field - .github/ISSUE_TEMPLATE/README.md — add name field - .github/instructions/.archive/README.md — stability: incubating - .github/projects/README.md — match actual directory structure All changes now comply with frontmatter schema validation.
* Wave 5 Issue #670 Phase 3: Standardize .github subdirectories and plugin README frontmatter Phase 3 of Wave 5 README audit covers 12 .github subdirectory and plugin README files. - plugins/lightspeed-github-ops/README.md — Add standardized frontmatter - plugins/lightspeed-github-ops/hooks/README.md — Add comprehensive frontmatter - .github/DISCUSSION_TEMPLATE/README.md — Update frontmatter; fix field ordering - .github/ISSUE_TEMPLATE/README.md — Update last_updated; standardize fields - .github/PULL_REQUEST_TEMPLATE/README.md — Update last_updated; standardize fields - .github/SAVED_REPLIES/README.md — Add missing standard fields - .github/metrics/README.md — Remove deprecated references field; update dates - .github/projects/README.md — Fix title mismatch; update frontmatter - .github/reports/README.md — Add comprehensive frontmatter - .github/prompts/README.md — Reconstruct malformed file with proper frontmatter - .github/schemas/README.md — Remove deprecated references field; update dates - .github/instructions/.archive/README.md — Add missing standard fields All Phase 3 files now follow consistent format: - title, description, file_type (documentation) - version, last_updated (2026-05-31), created_date - authors, maintainer (LightSpeed Team), license (GPL-3.0) - tags, domain (governance), stability - All markdown files validated - All frontmatter schema compliant - All internal links verified (where applicable) Relates to #670 Phase 3 completion. * fix: address Gemini review feedback for Phase 3 - Fix .github/projects/README.md content mismatch (Reports → Projects) - Simplify redundant relative path segments in .github/prompts/README.md - Ensure all content accurately reflects directory purpose Addresses Gemini code review comments on PR #703. * fix: address Copilot validation issues in Phase 3 ## Schema Compliance Fixes - Fix invalid stability values: beta → experimental, archived → incubating - Add required 'name' field to discussion_template and issue_template files - Fix broken AUTOMATION_GOVERNANCE link (../ → ../../docs/) - Update projects README to reflect actual directory structure (active, archived) ## Files Fixed - plugins/lightspeed-github-ops/README.md — stability: experimental - plugins/lightspeed-github-ops/hooks/README.md — stability: experimental - .github/prompts/README.md — fix link path, stability: experimental - .github/DISCUSSION_TEMPLATE/README.md — add name field - .github/ISSUE_TEMPLATE/README.md — add name field - .github/instructions/.archive/README.md — stability: incubating - .github/projects/README.md — match actual directory structure All changes now comply with frontmatter schema validation. * Update .github/instructions/.archive/README.md Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> Signed-off-by: Ash Shaw <ashley@lightspeedwp.agency> * Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Signed-off-by: Ash Shaw <ashley@lightspeedwp.agency> * Potential fix for pull request finding Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Signed-off-by: Ash Shaw <ashley@lightspeedwp.agency> --------- Signed-off-by: Ash Shaw <ashley@lightspeedwp.agency> Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: coderabbitai[bot] <136622811+coderabbitai[bot]@users.noreply.github.com> Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Signed-off-by: Ash Shaw <ashley@lightspeedwp.agency>
Co-authored-by: Copilot Autofix powered by AI <175728472+Copilot@users.noreply.github.com> Signed-off-by: Ash Shaw <ashley@lightspeedwp.agency>
Signed-off-by: Ash Shaw <ashley@lightspeedwp.agency>
Signed-off-by: Ash Shaw <ashley@lightspeedwp.agency>
Wave 5: Mermaid Accessibility Compliance + README Frontmatter Updates
feat(#670): Phase 2 Complete — Comprehensive README Frontmatter Standardization
chore: trailing whitespace cleanup
Updated presentation content for WordCamp 2026, focusing on design and accessibility guidelines, including color standards and font sizes. Signed-off-by: Ash Shaw <ashley@lightspeedwp.agency>
* fix(ci): auto-approve dependabot PRs so Mergify can squash-merge them The previous Mergify config never merged dependabot PRs because: 1. No `approve:` action — if branch protection requires ≥1 review, Mergify's queue action can never complete the merge (and may refuse to enqueue at all). 2. Redundant security/non-security split — `dependabot-security-label.yml` applies `meta:dependabot-security` to virtually every dependabot PR via the broad `/\bto fix\b/i` pattern, so the non-security rule (`-label=meta:dependabot-security`) never matched. Both rules queued to the same place anyway, so they have been merged into one. Changes: - `.github/mergify.yml`: consolidate two dependabot rules → one with `approve:` + `queue:` actions; add `allow_checks_interruption: false` to the queue rule to prevent CI-cancellation races. - `.github/workflows/dependabot-automerge.yml`: belt-and-suspenders GitHub Actions backup — triggers via `workflow_run` when CI passes on a dependabot PR, then approves the PR and enables GitHub squash auto-merge independently of Mergify. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Dm73CCVtnGNofnRNiVqkKw * fix(ci): correct Mergify action name and add CHANGELOG entry - Replace invalid `approve:` action with `review: type: APPROVE` - Remove invalid `allow_checks_interruption` queue option - Add CHANGELOG entry for the dependabot auto-merge fix Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Dm73CCVtnGNofnRNiVqkKw --------- Co-authored-by: Claude <noreply@anthropic.com>
Bumps [actions/checkout](https://github.com/actions/checkout) from 4 to 7. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](actions/checkout@v4...v7) --- updated-dependencies: - dependency-name: actions/checkout dependency-version: '7' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Ash Shaw <ashley@lightspeedwp.agency> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Bumps [mergifyio/gha-mergify-ci](https://github.com/mergifyio/gha-mergify-ci) from 14 to 22. - [Release notes](https://github.com/mergifyio/gha-mergify-ci/releases) - [Commits](Mergifyio/gha-mergify-ci@v14...v22) --- updated-dependencies: - dependency-name: mergifyio/gha-mergify-ci dependency-version: '22' dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Ash Shaw <ashley@lightspeedwp.agency> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
Bumps [@babel/preset-typescript](https://github.com/babel/babel/tree/HEAD/packages/babel-preset-typescript) from 7.29.7 to 8.0.1. - [Release notes](https://github.com/babel/babel/releases) - [Changelog](https://github.com/babel/babel/blob/main/CHANGELOG.md) - [Commits](https://github.com/babel/babel/commits/v8.0.1/packages/babel-preset-typescript) --- updated-dependencies: - dependency-name: "@babel/preset-typescript" dependency-version: 8.0.1 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Ash Shaw <ashley@lightspeedwp.agency> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
…8.0.1 Bumps [@babel/plugin-transform-runtime](https://github.com/babel/babel/tree/HEAD/packages/babel-plugin-transform-runtime) from 7.29.7 to 8.0.1. - [Release notes](https://github.com/babel/babel/releases) - [Changelog](https://github.com/babel/babel/blob/main/CHANGELOG.md) - [Commits](https://github.com/babel/babel/commits/v8.0.1/packages/babel-plugin-transform-runtime) --- updated-dependencies: - dependency-name: "@babel/plugin-transform-runtime" dependency-version: 8.0.1 dependency-type: direct:development update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com> Co-authored-by: dependabot[bot] <49699333+dependabot[bot]@users.noreply.github.com> Co-authored-by: Ash Shaw <ashley@lightspeedwp.agency> Co-authored-by: mergify[bot] <37929162+mergify[bot]@users.noreply.github.com>
* chore(templates): update release issue template to match v0.6.0 structure Rewrites 18-release.md (v1.0.1 → v2.0.0) to align with the enriched structure established in release issue #968. Key additions: - Exact release initiation commands (pre-flight gates, dry-run, live run, rollback) so any maintainer can kick off a release without referencing external docs - "Open PRs — merge before tagging" section for pre-release PR tracking - "Scope & Proposed Inclusions" section (merged PRs + recommended additions) - "Changelog Summary" section for Added/Changed/Fixed entries - Expanded milestones covering pre-release PRs, execution steps, and post-merge verification - Updated acceptance criteria: tag on main, release notes format (no H1 duplication, highlights + breaking changes sections always present) - Revised DoR/DoD aligned to the real agent-driven release process Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VuvMYk9n1Gw2ZC4WSAJBKJ * Update .github/ISSUE_TEMPLATE/18-release.md Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> Signed-off-by: Ash Shaw <ashley@lightspeedwp.agency> * Update .github/ISSUE_TEMPLATE/18-release.md Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com> Signed-off-by: Ash Shaw <ashley@lightspeedwp.agency> * fix(templates): remove description field from release template frontmatter and add changelog entry - Remove duplicate `description` field from 18-release.md (keep only `about` per GitHub template contract and check-template-labels.js validator) - Add CHANGELOG.md [Unreleased] entry for the v2.0.0 release template rewrite Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01VuvMYk9n1Gw2ZC4WSAJBKJ --------- Signed-off-by: Ash Shaw <ashley@lightspeedwp.agency> Co-authored-by: Claude <noreply@anthropic.com> Co-authored-by: gemini-code-assist[bot] <176961590+gemini-code-assist[bot]@users.noreply.github.com>
Part of release/v0.6.0 preparation. Closes #968
Bumps version from 0.5.0 to 0.6.0 (minor release). Closes #968
Contributor
|
✅ Template check passed after update. Thanks for fixing the PR description. |
Contributor
|
Important Review skippedToo many files! This PR contains 299 files, which is 149 over the limit of 150. To get a review, narrow the scope: Upgrade to a paid plan to raise the limit. ⚙️ Run configurationConfiguration used: Path: .coderabbit.yml Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (299)
You can disable this status message by setting the Use the checkbox below for a quick retry:
Note
|
Contributor
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request implements a comprehensive set of updates to the repository's governance, templates, and automation configurations, including the addition of a CodeRabbit configuration specification, the standardization of issue and pull request templates, and the restructuring of active project planning files. Feedback highlights a critical metadata corruption issue across multiple saved replies where file paths were incorrectly added to the labels list instead of a dedicated references key, as well as a minor redundancy in the .codespellrc ignore list.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
Comment on lines
6
to
9
| labels: | ||
| - area:community | ||
| - status:needs-triage | ||
| references: | ||
| - "../../CODE_OF_CONDUCT.md" |
Contributor
There was a problem hiding this comment.
The frontmatter in this saved reply appears to be corrupted. The references: key was removed, and its value (a file path) was incorrectly added to the labels list. This mixes semantically different data under one key, which could break metadata parsers and cause confusion.
This issue is present in numerous other SAVED_REPLIES files modified in this pull request. Please ensure that file paths are stored under a dedicated references: key to maintain a clean and valid metadata structure.
Suggested change
| labels: | |
| - area:community | |
| - status:needs-triage | |
| references: | |
| - "../../CODE_OF_CONDUCT.md" | |
| labels: | |
| - area:community | |
| - status:needs-triage | |
| references: | |
| - "../../CODE_OF_CONDUCT.md" |
| [codespell] | ||
| # LightSpeedWP shared dictionary for governance and WordPress terminology. | ||
| ignore-words-list = | ||
| LightspeedWP,LightSpeedWP,Codex,Copilot,Gemini,Claude,WordPress,Gutenberg,themejson,blockjson,frontmatter,labeler,WPCS,PHPCS |
Contributor
There was a problem hiding this comment.
The ignore-words-list contains both LightspeedWP and LightSpeedWP. Since codespell is case-insensitive by default, one of these is redundant. To keep the configuration clean, I suggest removing the lowercase s version.
LightSpeedWP,Codex,Copilot,Gemini,Claude,WordPress,Gutenberg,themejson,blockjson,frontmatter,labeler,WPCS,PHPCS
Member
Author
|
@Mergifyio rebase |
Contributor
☑️ Nothing to do, the required conditions are not metDetails
|
Signed-off-by: Ash Shaw <ashley@lightspeedwp.agency>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 578054448d
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| GITHUB_EVENT_NAME: ${{ github.event_name }} | ||
| GITHUB_ACTOR: ${{ github.actor }} | ||
| GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }} | ||
| run: node scripts/workflows/release/trigger-telemetry.cjs |
There was a problem hiding this comment.
In the release workflow, this job runs node scripts/workflows/release/trigger-telemetry.cjs before any actions/checkout step. GitHub-hosted jobs start without the repository files, so every workflow_dispatch or workflow_call run will fail here with MODULE_NOT_FOUND, preventing the telemetry outputs and blocking the downstream lint/test/release jobs; add a checkout before invoking the repo script.
Useful? React with 👍 / 👎.
| ); | ||
| } | ||
|
|
||
| // Step 6: Create tag | ||
| createTag(nextVersion, { dryRun }); | ||
| provider.createTag(nextVersion, { dryRun }); |
There was a problem hiding this comment.
When the workflow or CLI is run with provider: mcp, createTag, createReleasePR, and createRelease return Promises, but this orchestration calls them without await. Their API failures bypass the surrounding try/catch, and the agent can proceed to later steps or print the success banner before the tag, PR, or GitHub Release is actually created; await these provider calls in sequence.
Useful? React with 👍 / 👎.
| throw new Error("GITHUB_TOKEN not available for authorization check"); | ||
| } | ||
|
|
||
| const checkCmd = `curl -s -H "Authorization: token ${token}" https://api.github.com/orgs/lightspeedwp/teams/maintainers/memberships/${actor}`; |
There was a problem hiding this comment.
When the telemetry script runs, this interpolates GITHUB_TOKEN directly into a curl command string executed by execSync. That exposes the token in the child process arguments and can also place it in command-failure messages before masking, so use fetch/https with an Authorization header or another non-shell path for the membership check.
Useful? React with 👍 / 👎.
ashleyshaw
added this to the
Release v0.6.0 — Community Health, Governance Docs, and Meta Agent Foundations milestone
…y [Unreleased] after release roll The test was reading the real CHANGELOG.md from disk. After the v0.6.0 release roll, [Unreleased] is empty, causing the agent preflight to reject with "No unreleased changes in CHANGELOG". Also adds the [0.5.0] entry to the fixture so the release notes formatter can resolve the target version. Closes #968
Member
Author
|
Release workflow follow-up fix applied. Summary:
This should address the prior failure/annotations from run 27830462374 and keep subsequent runs clean. |
ashleyshaw
changed the title
- Revert @babel/core to 7.29.7 for stability - Revert all Babel plugins to v7 versions for compatibility - Keep Babel v7 configuration in babel.config.cjs - Fix duplicate import in validate-main-branch-pr.test.js - Fix validate-main-branch-pr.cjs main() function structure - Remove stray JSDoc comments and duplicate module.exports Reason: Babel v8 migration introduced too many compatibility issues with test suite and coverage tooling. Deferring v8 migration to post-release PR. Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01RiCAmG1XAwuMMJffZESC7x
Contributor
🎨 Mermaid Diagram Validation✅ All Mermaid diagram checks passed.
|
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.
Linked issues & merged PRs
Closes #968 — Release v0.6.0 — Community Health, Governance Docs, and Meta Agent Foundations
Key merged PRs in this release:
aboutfield, align with 25 org issue types, and polish #966 — Community health audit — PR templates, governance docs, and README alignmentChangelog
Added
Fixed
Changed
Checklist (Global DoD / PR)
VERSIONbumped to0.6.0CHANGELOG.mdrolled[Unreleased]→[0.6.0] - 2026-06-19[Unreleased]section present for next cyclemain(release cycle only)