search

wp-cli / wp-config-transformer

Programmatically edit a wp-config.php file
MIT License
81 stars 25 forks source link

Update wp-coding-standards/wpcs requirement from ^0.14.0 to ^0.14.0 || ^1.0.0 || ^2.0.0 #20

Closed dependabot-preview[bot] closed 5 years ago

dependabot-preview[bot] commented 5 years ago

Updates the requirements on wp-coding-standards/wpcs to permit the latest version.

Release notes *Sourced from [wp-coding-standards/wpcs's releases](https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/releases).* > ## 2.1.1 > ### Changed > - The `WordPress.WP.CapitalPDangit` will now ignore misspelled instances of `WordPress` within constant declarations. > This covers both constants declared using `defined()` as well as constants declared using the `const` keyword. > - The default value for `minimum_supported_wp_version`, as used by a [number of sniffs detecting usage of deprecated WP features](https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/wiki/Customizable-sniff-properties#minimum-wp-version-to-check-for-usage-of-deprecated-functions-classes-and-function-parameters), has been updated to `4.9`. > > ### Removed > - `paginate_comments_links()` from the list of auto-escaped functions `Sniff::$autoEscapedFunctions`. > This affects the `WordPress.Security.EscapeOutput` sniff. > > ### Fixed > - The `$current_blog` and `$tag_ID` variables have been added to the list of WordPress global variables. > This fixes some false positives from the `WordPress.NamingConventions.PrefixAllGlobals` and the `WordPress.WP.GlobalVariablesOverride` sniffs. > - The generic `TestCase` class name has been added to the `$test_class_whitelist`. > This fixes some false positives from the `WordPress.NamingConventions.FileName`, `WordPress.NamingConventions.PrefixAllGlobals` and the `WordPress.WP.GlobalVariablesOverride` sniffs. > - The `WordPress.NamingConventions.ValidVariableName` sniff will now correctly recognize `$tag_ID` as a WordPress native, mixed-case variable. > - The `WordPress.Security.NonceVerification` sniff will now correctly recognize nonce verification within a nested closure or anonymous class.
Changelog *Sourced from [wp-coding-standards/wpcs's changelog](https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/blob/develop/CHANGELOG.md).* > ## [2.1.1] - 2019-05-21 > > ### Changed > - The `WordPress.WP.CapitalPDangit` will now ignore misspelled instances of `WordPress` within constant declarations. > This covers both constants declared using `defined()` as well as constants declared using the `const` keyword. > - The default value for `minimum_supported_wp_version`, as used by a [number of sniffs detecting usage of deprecated WP features](https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/wiki/Customizable-sniff-properties#minimum-wp-version-to-check-for-usage-of-deprecated-functions-classes-and-function-parameters), has been updated to `4.9`. > > ### Removed > - `paginate_comments_links()` from the list of auto-escaped functions `Sniff::$autoEscapedFunctions`. > This affects the `WordPress.Security.EscapeOutput` sniff. > > ### Fixed > - The `$current_blog` and `$tag_ID` variables have been added to the list of WordPress global variables. > This fixes some false positives from the `WordPress.NamingConventions.PrefixAllGlobals` and the `WordPress.WP.GlobalVariablesOverride` sniffs. > - The generic `TestCase` class name has been added to the `$test_class_whitelist`. > This fixes some false positives from the `WordPress.NamingConventions.FileName`, `WordPress.NamingConventions.PrefixAllGlobals` and the `WordPress.WP.GlobalVariablesOverride` sniffs. > - The `WordPress.NamingConventions.ValidVariableName` sniff will now correctly recognize `$tag_ID` as a WordPress native, mixed-case variable. > - The `WordPress.Security.NonceVerification` sniff will now correctly recognize nonce verification within a nested closure or anonymous class. > > > ## [2.1.0] - 2019-04-08 > > ### Added > - New `WordPress.PHP.IniSet` sniff to the `WordPress-Extra` ruleset. > This sniff will detect calls to `ini_set()` and `ini_alter()` and warn against their use as changing configuration values at runtime leads to an unpredictable runtime environment, which can result in conflicts between core/plugins/themes. > - The sniff will not throw notices about a very limited set of "safe" ini directives. > - For a number of ini directives for which there are alternative, non-conflicting ways to achieve the same available, the sniff will throw an `error` and advise using the alternative. > - `doubleval()`, `count()` and `sizeof()` to `Sniff::$unslashingSanitizingFunctions` property. > While `count()` and its alias `sizeof()`, don't actually unslash or sanitize, the output of these functions is safe to use without unslashing or sanitizing. > This affects the `WordPress.Security.ValidatedSanitizedInput` and the `WordPress.Security.NonceVerification` sniffs. > - The new WP 5.1 `WP_UnitTestCase_Base` class to the `Sniff::$test_class_whitelist` property. > - New `Sniff::get_array_access_keys()` utility method to retrieve all array keys for a variable using multi-level array access. > - New `Sniff::is_class_object_call()`, `Sniff::is_token_namespaced()` utility methods. > These should help make the checking of whether or not a function call is a global function, method call or a namespaced function call more consistent. > This also implements allowing for the [namespace keyword being used as an operator](https://www.php.net/manual/en/language.namespaces.nsconstants.php#example-258). > - New `Sniff::is_in_function_call()` utility method to facilitate checking whether a token is (part of) a parameter passed to a specific (set of) function(s). > - New `Sniff::is_in_type_test()` utility method to determine if a variable is being type tested, along with a `Sniff::$typeTestFunctions` property containing the names of the functions this applies to. > - New `Sniff::is_in_array_comparison()` utility method to determine if a variable is (part of) a parameter in an array-value comparison, along with a `Sniff::$arrayCompareFunctions` property containing the names of the relevant functions. > - New `Sniff::$arrayWalkingFunctions` property containing the names of array functions which apply a callback to the array, but don't change the array by reference. > - New `Sniff::$unslashingFunctions` property containing the names of functions which unslash data passed to them and return the unslashed result. > > ### Changed > - Moved the `WordPress.PHP.StrictComparisons`, `WordPress.PHP.StrictInArray` and the `WordPress.CodeAnalysis.AssignmentInCondition` sniff from the `WordPress-Extra` to the `WordPress-Core` ruleset. > - The `Squiz.Commenting.InlineComment.SpacingAfter` error is no longer included in the `WordPress-Docs` ruleset. > - The default value for `minimum_supported_wp_version`, as used by a [number of sniffs detecting usage of deprecated WP features](https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/wiki/Customizable-sniff-properties#minimum-wp-version-to-check-for-usage-of-deprecated-functions-classes-and-function-parameters), has been updated to `4.8`. > - The `WordPress.WP.DeprecatedFunctions` sniff will now detect functions deprecated in WP 5.1. > - The `WordPress.Security.NonceVerification` sniff now allows for variable type testing, comparisons, unslashing and sanitization before the nonce check. A nonce check within the same scope, however, is still required. > - The `WordPress.Security.ValidatedSanitizedInput` sniff now allows for using a superglobal in an array-value comparison without sanitization, same as when the superglobal is used in a scalar value comparison. > - `WordPress.NamingConventions.PrefixAllGlobals`: some of the error messages have been made more explicit. > - The error messages for the `WordPress.Security.ValidatedSanitizedInput` sniff will now contain information on the index keys accessed. > ... (truncated)
Commits - [`bd9c331`](https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/commit/bd9c33152115e6741e3510ff7189605b35167908) Merge pull request [#1709](https://github-redirect.dependabot.com/WordPress-Coding-Standards/WordPress-Coding-Standards/issues/1709) from WordPress-Coding-Standards/develop - [`97d6fbf`](https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/commit/97d6fbf1e95215140cf54e229bbfb341b9bd72c4) Changelog for WPCS 2.1.1 ([#1707](https://github-redirect.dependabot.com/WordPress-Coding-Standards/WordPress-Coding-Standards/issues/1707)) - [`4b5091b`](https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/commit/4b5091b16c3594af670dcdd25e409e7dc9074f9a) Update default minimum_supported_version to WP 4.9 ([#1708](https://github-redirect.dependabot.com/WordPress-Coding-Standards/WordPress-Coding-Standards/issues/1708)) - [`3aadeee`](https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/commit/3aadeeea8b28c3580841c3962e0cb40308519c5b) Update default minimum_supported_version to WP 4.9 - [`3a2f289`](https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/commit/3a2f289e36f5a54650d54a53d1d74e11f1c5d6e0) Sniff::is_test_class(): recognize `TestCase` ([#1706](https://github-redirect.dependabot.com/WordPress-Coding-Standards/WordPress-Coding-Standards/issues/1706)) - [`79b6855`](https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/commit/79b68552a94e618525856585f73d837de26aaf32) Sniff::is_test_class(): recognize `TestCase` - [`c7dcd23`](https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/commit/c7dcd238a77995a6a00f7e8953db3e58ad39b0cb) CapitalPDangit: ignore misspellings in constant declarations ([#1699](https://github-redirect.dependabot.com/WordPress-Coding-Standards/WordPress-Coding-Standards/issues/1699)) - [`d7d3a0d`](https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/commit/d7d3a0dda55d7cbd5c068105e3cf5a49a4e104c6) Merge pull request [#1701](https://github-redirect.dependabot.com/WordPress-Coding-Standards/WordPress-Coding-Standards/issues/1701) from dingo-d/feature/remove-unsafe-functions - [`85c1a10`](https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/commit/85c1a10829e6d9288c7bb6cd28a219748a3bb9f2) Remove paginate_comments_links from escaped functions list - [`8677d51`](https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/commit/8677d51483995738eb45b92842197d09ae348ea4) Accept tag_ID as variable name ([#1697](https://github-redirect.dependabot.com/WordPress-Coding-Standards/WordPress-Coding-Standards/issues/1697)) - Additional commits viewable in [compare view](https://github.com/WordPress-Coding-Standards/WordPress-Coding-Standards/compare/0.14.0...2.1.1)


Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

Note: This repo was added to Dependabot recently, so you'll receive a maximum of 5 PRs for your first few update runs. Once an update run creates fewer than 5 PRs we'll remove that limit.

You can always request more updates by clicking Bump now in your Dependabot dashboard.

Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot ignore this [patch|minor|major] version` will close this PR and stop Dependabot creating any more for this minor/major version (unless you reopen the PR or upgrade to it yourself) - `@dependabot ignore this dependency` will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself) - `@dependabot use these labels` will set the current labels as the default for future PRs for this repo and language - `@dependabot use these reviewers` will set the current reviewers as the default for future PRs for this repo and language - `@dependabot use these assignees` will set the current assignees as the default for future PRs for this repo and language - `@dependabot use this milestone` will set the current milestone as the default for future PRs for this repo and language - `@dependabot badge me` will comment on this PR with code to add a "Dependabot enabled" badge to your readme Additionally, you can set the following in your Dependabot [dashboard](https://app.dependabot.com): - Update frequency (including time of day and day of week) - Automerge options (never/patch/minor, and dev/runtime dependencies) - Pull request limits (per update run and/or open at any time) - Out-of-range updates (receive only lockfile updates, if desired) - Security updates (receive only security updates, if desired) Finally, you can contact us by mentioning @dependabot.

Dependabot has been acquired by GitHub 🎉