~vcs-imports/buddypress/trunk : changes

~vcs-imports/buddypress/trunk » Changes to composer.json from revision 9868

From Revision 9868

Rev	Summary	Authors	Date
9852	Build/test tools: use GitHub Actions to run PHP unit tests Build/test tools: use GitHub Actions to run PHP unit tests We're starting using GitHub Actions with these 4 jobs to do our PHP Unit tests on this matrix : - WP Trunk - PHP 7.4 - WP Trunk - PHP 8.0 - WP 5.7 - PHP 7.4 - WP 5.7 - PHP 8.0 As the future of Travis.org is uncertain, we believe it's an important step to secure our testing tool. Props slaFFik, Huge Props espellcaste 💪 Fixes #8421	imath	3 years ago
9764	Update Composer dependencies to match its v2 requirements Update Composer dependencies to match its v2 requirements - Updates `composer/installers` to 1.10 - Updates `phpcompatibility/phpcompatibility-wp` to 2.1 - Updates `dealerdirect/phpcodesniffer-composer-installer` to 0.7.1 - Updates `wp-phpunit/wp-phpunit` to latest - Adds a dependency to `phpunit/phpunit` v7.5+ to be able to run PHP 8.0 unit tests using `@wordpress/env`. Props slaFFik Fixes #8381 Fixes #8420	imath	3 years ago
9660	Build/Test Tools: include @wordpress/env into BuddyPress Build/Test Tools: include @wordpress/env into BuddyPress `wp-env` requires Docker and the latest Node.js LTS version. It gives us a set of new `npm` commands to easily generate a local WordPress environment to unit test, develop and contribute to BuddyPress code. To enjoy `wp-env`, make sure you have SVN or Git, composer, Node.js and Docker installed on your computer. Get the development version of BuddyPress using our SVN repository or its GitHub read-only mirror from this URL: https://buddypress.org/download/#trunk, and use the command to fetch the code locally into a `buddypress` folder. From your terminal software, move to this folder to install the needed libraries using the following commands. `npm install` `composer install` Once done, you can set up your local development environment using this single command: `npm run wp-env start` You can now access to your local environment and finish the WordPress setup (permalinks etc..) from this URL: `http://localhost:8888/wp-admin/` The administration credentials are: - Username: admin, - Password: password To stop the environment, you can use this command: `npm run wp-env stop` To run PHP unit tests, you can use this command: `npm run test-php` To run PHP unit tests on multisite, you can use this command: `npm run test-php-multisite` You can customize your local development setup using a file named `.wp-env.override.json `. Our default setup is using the WordPress development version and includes the BP REST plugin. For more details about `wp-env`, have a look at this documentation page: https://developer.wordpress.org/block-editor/packages/packages-env/ Props oztaser, mercime, vapvarun Fixes #8317	imath	3 years ago
9555	Update Grunt tasks & .gitignore to match BP Blocks needs Update Grunt tasks & .gitignore to match BP Blocks needs - The `makepot` task is now using the WP CLI `wp i18n make-pot` command. - Exclude JavaScript Files generated by Parcel/Babel from `jsvalidate`, `jshint` & `uglify` tasks. - Add new tasks to build & minify BP Blocks files. See #8048	imath	4 years ago
9334	Another try at adding `exec:phpcompat` Grunt task. Another try at adding `exec:phpcompat` Grunt task. Changeset [12277] didn't properly apply the changes. See #7997.	boonebgorges	5 years ago
9333	Introduce PHP compatibility build/test tools. Introduce PHP compatibility build/test tools. The new `exec:phpcompat` Grunt task uses the phpcompatibility-wp library to do a WordPress-sensitive check for incompatibilities between our codebase and the PHP versions that we support. A new Travis CI job is dedicated to running the `phpcompat` tests. This pattern parallels our `travis:grunt` job. The new `exec:phpcompat` tests supercede the `phplint` task introduced in #7925. See #7997.	boonebgorges	5 years ago
9071	Build: Use tabs for indentaion, follow up to [11946] Build: Use tabs for indentaion, follow up to [11946] See #7733.	netweb	6 years ago
8900	Retire Legacy Forums. Retire Legacy Forums. "Legacy Forums" is what we now call the bundled version of bbPress 1 that has shipped with BuddyPress for over nine years. The Legacy Forums codebase/features are many years stagnant, and it has been almost completely hidden from the UI for the past five years. Legacy Forums were replaced by bbPress 2, which is its own plugin, and we've been promoting its integration with BuddyPress for a long time. Most significantly, bbPress 1 only runs on WordPress versions older than 4.7, because of a BackPress conflict (which is nested inside bbPress 1) with WordPress 4.7's `WP_Taxonomy` class. If your site is still using Legacy Forums, you will need to migrate to bbPress 2 to run BuddyPress 3.0. See https://bpdevel.wordpress.com/2017/12/07/legacy-forums-support-will-be/ for more information. Fixes #5351 See #7502	djpaul	6 years ago
8780	BuddyPress adds community features to WordPress. Member Prof... BuddyPress adds community features to WordPress. Member Profiles, Activity Streams, Direct Messaging, Notifications, and more!	johnjamesjacoby	6 years ago
8490	Update Composer PHP requirement to 5.3+, and shrinkwrap late... Update Composer PHP requirement to 5.3+, and shrinkwrap latest NPM packages. See #7195	djpaul	7 years ago
8328	Move composer.json to root and update Grunt (attempt #2). Move composer.json to root and update Grunt (attempt #2). Basic Composer support was added in v2.2, enabling distribution of BuddyPress via Packagist. As we had no plans to use any developer-facing features of Composer, the config file was placed into the /src/ subfolder (i.e. the root folder of the distribution version of BuddyPress) to simplify our release build process. Moving the Composer config file into the root of the development version of the plugin, while copying it back into place for the distribution version, smooths the way towards enabling us to use Composer to install development-only libraries. This may help us maintain a high-quality codebase. An example tickets where Composer is being considered for use as a development aid is #7228.	djpaul	7 years ago