Tribe Libs is a collection of libraries created by Modern Tribe for use with Square One-based WordPress projects. It is required by the Square One core plugin.

Versions

Tribe Libs Version	PHP Constraints	Notes
3.x	7.2-7.4	Master branch. No longer maintained.
4.x	7.4+	For use in legacy Square One PHP 7.4 projects where the host is upgrading to PHP 8.0.
5.x+	8.0+	For use in new Square One projects.

Installation

composer require moderntribe/tribe-libs

Usage

All usage documentation lives in the Square One repository.

Support

Usage of Tribe Libs is not actively supported by Modern Tribe outside of client contracts. Pull requests and suggestions are welcome and will be addressed based on business need.

Release Process

This library comprises a large collection of smaller libraries that can be included in whole or in part on Square One projects. These libraries are developed following the monorepo model. All changes are committed to this, the parent project. Maintenance of the individual packages is managed using the Monorepo Builder utility.

Releasing a new version

IMPORTANT: branches must already exist in the sub-repos, use the Create Sub-Repo Branch GitHub Workflow to create them if they don't already exist.

1. Ensure that all code for the release is merged to the branch that matches the release number, e.g. if you're planning to release an update 4.1.0, that code should live in the 4.x branch. A release such as 5.2.6 should live in the 5.x branch.
2. Ensure that all updates for the release are logged in CHANGELOG.md under ## Unreleased.
3. Run the release script, with the version number for the release (format: <major>.<minor>.<patch>): Dry run example for a 4.x release:

   git checkout 4.x && git pull && ./monorepo.sh release 4.1.0 --dry-run

   Real release example for a 4.x release:

   git checkout 4.x && git pull && ./monorepo.sh release 4.1.0

4. The script will handle several steps for you automatically:
   1. Set any package interdependencies to the new version.
   2. Update CHANGELOG.md with the appropriate version number.
   3. Create the git tag and push it to GitHub, tagged to the branch you have checked out.
   4. Bump the current branch you have checked out version's to the next version number
5. When the tag is pushed to GitHub, an Action there will automatically split the monorepo and deploy the tag to all of the package repos. (Note: The GH Action will run as a bot user with appropriate permissions to write to all of the package repositories. Those repositories are read-only for normal usage.)

Adding Packages

1. Create a new directory for the package in src. Create your code there, include an independent composer.json for the package (you can copy the sample), and commit it to tribe-libs.
2. Create an empty public GitHub repository for the package (you probably need to be an org admin to complete this step). Follow the naming convention moderntribe/square1-*. Ensure that the user tr1b0t has write access to the repo. Use the script dev/monorepo/scripts/create-package-repo.sh to create the repo and add the tr1b0t user automatically.

   ./dev/monorepo/scripts/create-package-repo.sh square1-my-new-repo

3. Add a single commit (a blank readme is fine) and push it up.
4. Run the Create Sub-Repo Branch GitHub Workflow to create any missing version branches, e.g. master,4.x, 5.x etc...
5. Run the script to merge the package composer.json files to the root composer.json file:

   ./monorepo.sh merge

6. After the next release, Register the package on Packagist.

Adding Composer Dependencies

1. Add the dependency to composer.json in the sub-package(s) that needs it.
2. Run the merge command to merge dependencies up to the root composer.json

   ./monorepo.sh merge

Update the development version

You will rarely need to do this, but it is documented here just in case.

1. Set the master branch alias for all packages:

   ./monorepo.sh set-alias 5.0

2. Bump the interdependencies among the packages to the same version.

   ./monorepo.sh bump-interdependency "^5.0"