Repository navigation
chore(release): wp-phpcs and wp-phpstan 1.0.1, npm configs 1.1.0, wp-tooling 2.0.0 - #75
Merged
Merged
Conversation
… versions - rtcamp/wp-phpcs and rtcamp/wp-phpstan 1.0.1: LICENSE, README and Packagist metadata only, so a patch. Released by the v1.0.1 tag. - @rtcamp/eslint-config, @rtcamp/stylelint-config and @rtcamp/tailwind-config 1.1.0: engines.node raised to >=22.19. - @rtcamp/wp-tooling 2.0.0: scaffolds target rtcamp/wp-primitives ^2.0 (breaking), plus everything else under Unreleased. None of the npm packages is published yet, and each CHANGELOG already records 1.0.0 as the 2026-07-30 state, so the first publish uses these versions. npm version also normalised the files array indentation in wp-tooling's package.json.
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
Release versions are consistent across manifests, changelogs, and the lockfile.
Review effort: Balanced
Findings: None
What changed in this PR
Cuts coordinated public release versions across npm and Composer packages.
Changes:
- Bumps npm packages to 1.1.0 and
wp-toolingto 2.0.0. - Cuts dated changelog sections for all six packages.
- Synchronizes workspace versions in the lockfile.
| File | Description |
|---|---|
package-lock.json |
Synchronizes npm workspace versions. |
node-packages/wp-tooling/package.json |
Bumps version to 2.0.0. |
node-packages/wp-tooling/CHANGELOG.md |
Cuts the 2.0.0 release. |
node-packages/tailwind-config/package.json |
Bumps version to 1.1.0. |
node-packages/tailwind-config/CHANGELOG.md |
Cuts the 1.1.0 release. |
node-packages/stylelint-config/package.json |
Bumps version to 1.1.0. |
node-packages/stylelint-config/CHANGELOG.md |
Cuts the 1.1.0 release. |
node-packages/eslint-config/package.json |
Bumps version to 1.1.0. |
node-packages/eslint-config/CHANGELOG.md |
Cuts the 1.1.0 release. |
composer-packages/phpstan/CHANGELOG.md |
Cuts the 1.0.1 release. |
composer-packages/phpcs/CHANGELOG.md |
Cuts the 1.0.1 release. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
…g READMEs npm stores each README at publish time, so these are the package pages. - @rtcamp/wp-tooling: describes what ships (the 14 commands, the 46 scaffolds by group and the 10 library entry points), adds a quick start, requirements and documentation links, installs with --save-dev, and drops the line that listed the lint configs as part of this package. Links are absolute, and package.json gains repository.directory, so they resolve on npmjs.com. - eslint-config, stylelint-config and tailwind-config: the same header as the other rtCamp packages (license, npm version and Node badges, one-line summary) and the Node.js 22.19+ requirement.
- The wp-tooling 2.0.0 notes said rtcamp/wp-phpcs is not on Packagist and that the config packages 404 on npm. Both stop being true with this release, so the two sentences now describe the state when each fix was made. - AGENTS.md described npm releases as subtree-split only and said npm install @rtcamp/wp-tooling does not resolve from the registry. It now says the npm packages publish to npmjs.com with their own versions, keeps the npm/<dirname> branches as the git-URL path, and warns never to use a v* tag for an npm release.
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
The required rtcamp/wp-primitives v2.0.0 dependency has not yet been tagged, so publishing wp-tooling 2.0.0 would produce unresolvable scaffold dependencies.
Review effort: Balanced
Findings: 1
Open (1)
Resolved since last review (2)
AnuragVasanwala
approved these changes
Oct 1, 2026
github-actions Bot
pushed a commit
that referenced
this pull request
Oct 1, 2026
…tooling 2.0.0 (#75) * chore(release): cut wp-phpcs and wp-phpstan 1.0.1 and the npm package versions - rtcamp/wp-phpcs and rtcamp/wp-phpstan 1.0.1: LICENSE, README and Packagist metadata only, so a patch. Released by the v1.0.1 tag. - @rtcamp/eslint-config, @rtcamp/stylelint-config and @rtcamp/tailwind-config 1.1.0: engines.node raised to >=22.19. - @rtcamp/wp-tooling 2.0.0: scaffolds target rtcamp/wp-primitives ^2.0 (breaking), plus everything else under Unreleased. None of the npm packages is published yet, and each CHANGELOG already records 1.0.0 as the 2026-07-30 state, so the first publish uses these versions. npm version also normalised the files array indentation in wp-tooling's package.json. * docs(npm): rewrite the wp-tooling README and add headers to the config READMEs npm stores each README at publish time, so these are the package pages. - @rtcamp/wp-tooling: describes what ships (the 14 commands, the 46 scaffolds by group and the 10 library entry points), adds a quick start, requirements and documentation links, installs with --save-dev, and drops the line that listed the lint configs as part of this package. Links are absolute, and package.json gains repository.directory, so they resolve on npmjs.com. - eslint-config, stylelint-config and tailwind-config: the same header as the other rtCamp packages (license, npm version and Node badges, one-line summary) and the Node.js 22.19+ requirement. * docs: keep the release notes and AGENTS.md true after the first publish - The wp-tooling 2.0.0 notes said rtcamp/wp-phpcs is not on Packagist and that the config packages 404 on npm. Both stop being true with this release, so the two sentences now describe the state when each fix was made. - AGENTS.md described npm releases as subtree-split only and said npm install @rtcamp/wp-tooling does not resolve from the registry. It now says the npm packages publish to npmjs.com with their own versions, keeps the npm/<dirname> branches as the git-URL path, and warns never to use a v* tag for an npm release.
github-actions Bot
pushed a commit
that referenced
this pull request
Oct 1, 2026
…tooling 2.0.0 (#75) * chore(release): cut wp-phpcs and wp-phpstan 1.0.1 and the npm package versions - rtcamp/wp-phpcs and rtcamp/wp-phpstan 1.0.1: LICENSE, README and Packagist metadata only, so a patch. Released by the v1.0.1 tag. - @rtcamp/eslint-config, @rtcamp/stylelint-config and @rtcamp/tailwind-config 1.1.0: engines.node raised to >=22.19. - @rtcamp/wp-tooling 2.0.0: scaffolds target rtcamp/wp-primitives ^2.0 (breaking), plus everything else under Unreleased. None of the npm packages is published yet, and each CHANGELOG already records 1.0.0 as the 2026-07-30 state, so the first publish uses these versions. npm version also normalised the files array indentation in wp-tooling's package.json. * docs(npm): rewrite the wp-tooling README and add headers to the config READMEs npm stores each README at publish time, so these are the package pages. - @rtcamp/wp-tooling: describes what ships (the 14 commands, the 46 scaffolds by group and the 10 library entry points), adds a quick start, requirements and documentation links, installs with --save-dev, and drops the line that listed the lint configs as part of this package. Links are absolute, and package.json gains repository.directory, so they resolve on npmjs.com. - eslint-config, stylelint-config and tailwind-config: the same header as the other rtCamp packages (license, npm version and Node badges, one-line summary) and the Node.js 22.19+ requirement. * docs: keep the release notes and AGENTS.md true after the first publish - The wp-tooling 2.0.0 notes said rtcamp/wp-phpcs is not on Packagist and that the config packages 404 on npm. Both stop being true with this release, so the two sentences now describe the state when each fix was made. - AGENTS.md described npm releases as subtree-split only and said npm install @rtcamp/wp-tooling does not resolve from the registry. It now says the npm packages publish to npmjs.com with their own versions, keeps the npm/<dirname> branches as the git-URL path, and warns never to use a v* tag for an npm release.
github-actions Bot
pushed a commit
that referenced
this pull request
Oct 1, 2026
…tooling 2.0.0 (#75) * chore(release): cut wp-phpcs and wp-phpstan 1.0.1 and the npm package versions - rtcamp/wp-phpcs and rtcamp/wp-phpstan 1.0.1: LICENSE, README and Packagist metadata only, so a patch. Released by the v1.0.1 tag. - @rtcamp/eslint-config, @rtcamp/stylelint-config and @rtcamp/tailwind-config 1.1.0: engines.node raised to >=22.19. - @rtcamp/wp-tooling 2.0.0: scaffolds target rtcamp/wp-primitives ^2.0 (breaking), plus everything else under Unreleased. None of the npm packages is published yet, and each CHANGELOG already records 1.0.0 as the 2026-07-30 state, so the first publish uses these versions. npm version also normalised the files array indentation in wp-tooling's package.json. * docs(npm): rewrite the wp-tooling README and add headers to the config READMEs npm stores each README at publish time, so these are the package pages. - @rtcamp/wp-tooling: describes what ships (the 14 commands, the 46 scaffolds by group and the 10 library entry points), adds a quick start, requirements and documentation links, installs with --save-dev, and drops the line that listed the lint configs as part of this package. Links are absolute, and package.json gains repository.directory, so they resolve on npmjs.com. - eslint-config, stylelint-config and tailwind-config: the same header as the other rtCamp packages (license, npm version and Node badges, one-line summary) and the Node.js 22.19+ requirement. * docs: keep the release notes and AGENTS.md true after the first publish - The wp-tooling 2.0.0 notes said rtcamp/wp-phpcs is not on Packagist and that the config packages 404 on npm. Both stop being true with this release, so the two sentences now describe the state when each fix was made. - AGENTS.md described npm releases as subtree-split only and said npm install @rtcamp/wp-tooling does not resolve from the registry. It now says the npm packages publish to npmjs.com with their own versions, keeps the npm/<dirname> branches as the git-URL path, and warns never to use a v* tag for an npm release.
github-actions Bot
pushed a commit
that referenced
this pull request
Oct 1, 2026
…tooling 2.0.0 (#75) * chore(release): cut wp-phpcs and wp-phpstan 1.0.1 and the npm package versions - rtcamp/wp-phpcs and rtcamp/wp-phpstan 1.0.1: LICENSE, README and Packagist metadata only, so a patch. Released by the v1.0.1 tag. - @rtcamp/eslint-config, @rtcamp/stylelint-config and @rtcamp/tailwind-config 1.1.0: engines.node raised to >=22.19. - @rtcamp/wp-tooling 2.0.0: scaffolds target rtcamp/wp-primitives ^2.0 (breaking), plus everything else under Unreleased. None of the npm packages is published yet, and each CHANGELOG already records 1.0.0 as the 2026-07-30 state, so the first publish uses these versions. npm version also normalised the files array indentation in wp-tooling's package.json. * docs(npm): rewrite the wp-tooling README and add headers to the config READMEs npm stores each README at publish time, so these are the package pages. - @rtcamp/wp-tooling: describes what ships (the 14 commands, the 46 scaffolds by group and the 10 library entry points), adds a quick start, requirements and documentation links, installs with --save-dev, and drops the line that listed the lint configs as part of this package. Links are absolute, and package.json gains repository.directory, so they resolve on npmjs.com. - eslint-config, stylelint-config and tailwind-config: the same header as the other rtCamp packages (license, npm version and Node badges, one-line summary) and the Node.js 22.19+ requirement. * docs: keep the release notes and AGENTS.md true after the first publish - The wp-tooling 2.0.0 notes said rtcamp/wp-phpcs is not on Packagist and that the config packages 404 on npm. Both stop being true with this release, so the two sentences now describe the state when each fix was made. - AGENTS.md described npm releases as subtree-split only and said npm install @rtcamp/wp-tooling does not resolve from the registry. It now says the npm packages publish to npmjs.com with their own versions, keeps the npm/<dirname> branches as the git-URL path, and warns never to use a v* tag for an npm release.
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.
Cuts the versions for the first public releases. No code changes: CHANGELOG headings and
package.jsonversions only.rtcamp/wp-phpcsv1.0.1tag,release-php.ymlrtcamp/wp-phpstanv1.0.1tag,release-php.yml@rtcamp/eslint-configengines.noderaised to>=22.19npm publish@rtcamp/stylelint-configengines.noderaised to>=22.19npm publish@rtcamp/tailwind-configengines.noderaised to>=22.19npm publish@rtcamp/wp-toolingrtcamp/wp-primitives ^2.0(#70), plus everything under Unreleasednpm publishNone of the npm packages is on npm yet. Each CHANGELOG already records
1.0.0as the 2026-07-30 state, so the first publish uses the versions above rather than 1.0.0.READMEs (the npm package pages)
npm stores each README at publish time, so they are updated here, before the first publish:
@rtcamp/wp-tooling: rewritten to describe what ships (14 commands, 46 scaffolds by group, 10 library entry points), with a quick start, requirements and documentation links. Install uses--save-dev, and the line that listed the lint configs as part of this package is gone. Links are absolute, andpackage.jsongainsrepository.directory, so they resolve on npmjs.com.eslint-config,stylelint-config,tailwind-config: the same header as the other rtCamp packages, plus the Node.js 22.19+ requirement.After merge
v1.0.1):maincheckout (2FA prompt):npm ci && npm publish -w node-packages/eslint-config -w node-packages/stylelint-config -w node-packages/tailwind-config -w node-packages/wp-tooling@rtcamp/eslint-config@1.1.0, ...) so a later Changesets setup starts from published versions.Checked
npm run check: lint clean, 1,375 tests passingnpm pack --dry-run: eslint-config 4 files, stylelint-config 4, tailwind-config 6, wp-tooling 234npm publish --dry-run: "Publishing to https://registry.npmjs.org/ with tag latest and public access"package-lock.jsondiff: the four workspace versions only