grunt-patch-wordpress 1.0.0

I am proud to announce the immediate release of grunt-patchpatch A special text file that describes changes to code, by identifying the files and lines which are added, removed, and altered. It may also be referred to as a diff. A patch can be applied to a codebase for testing.-wordpress version 1.0.0 which brings in the ability to change the location of files, reformats all of the code to bring it inline with the current WordPress coding standards, and fixes a small number of bugs. This release also bumps the minimum version of node.js to be inline with the current WordPress coreCore Core is the set of software required to run WordPress. The Core Development Team builds WordPress. minimum version.

File mapping is the big feature, as that will help with #43055 and any other future file reorganizations. 

Using the file_mappings option

If you'd like to map old file paths in your patch to new file paths during the patching process, you can pass a file mappings object as an option. Using this option can be helpful when the file paths in the project have been changed since you've created your patch.

The file mappings object should contain old file paths and the corresponding new file paths. In the Gruntfile.js of your project, this would look like this:

patch: {
	options: {
		file_mappings: {
			'old_path1': 'new_path1',
			'old_path2': 'new_path2',
			'old_path3': 'new_path3',

In this example, the patch task will look for 'old_path1', 'old_path2' and 'old_path3' in your patch and replace them during patching with 'new_path1', 'new_path2', and 'new_path3' respectively.

Thanks to @pento, @netweb, @boblinthorst, @ireneyoast, @omarreiss, and @herregroen for contributing to this release and to all of the contributors who have helped make grunt-patch- wordpress what it is today.