bedrock 1.26.0 released

system · December 14, 2024, 4:23pm

What’s Changed

Bump requirements to PHP 8.1 by @retlehs (https://github.com/roots/bedrock/pull/747)
Add dev container by @retlehs (https://github.com/roots/bedrock/pull/748)
PER-CS coding standards, switch from PHPCS to Pint by @retlehs (https://github.com/roots/bedrock/pull/749)
Disable script concatenation by default by @retlehs (https://github.com/roots/bedrock/pull/717)
Don’t leak env values into $_SERVER by @swalkinshaw (https://github.com/roots/bedrock/pull/598)
Bump oscarotero/env to v2.1.1 (https://github.com/roots/bedrock/pull/745)

Full Changelog: Comparing 1.25.1...1.26.0 · roots/bedrock · GitHub

andronocean · January 8, 2025, 5:33pm

Is the dev container mentioned here for Bedrock’s own build pipeline integration tests, or is a test suite boilerplate coming soon?

ben · January 9, 2025, 2:31pm

The dev container is just for Bedrock’s basic integration test right now

janez33 · April 16, 2025, 1:23pm

Hello , thanks for the great work on Bedrock template.

Quick question: we’ve been using PHPCS (PHP_CodeSniffer) with WordPress Coding Standards in our Bedrock-based WooCommerce project. Now that you’ve switched to Pint and PER-CS, would you recommend we drop PHPCS entirely, or is there value in keeping it alongside Pint?

We’re considering keeping PHPCS (since it catches some WP-specific things) and maybe adding Pint just to stay aligned with upstream (even if we don’t actively use it). Would love your thoughts on best practices here. Thanks!

ben · April 16, 2025, 2:55pm

Roots projects have never used the outdated and unattractive WordPress coding standards, and never will

Bedrock is a boilerplate, and we have always encouraged folks to modify it to best suit their own needs