Previously ${FARMOS_COMPOSER_VERSION} was not being set for
tagged releases, causing `composer require farmos/farmos`
to run without a version constraint. This worked for 2.x
releases because it would default to the latest stable release.
This does not work for 3.0.0-betaX releases, because they are
not considered "stable" by Composer, so it falls back on the
latest stable 2.x release (2.2.2).
The official repo (https://git.osgeo.org/gitea/geos/php-geos)
has been failing git clone during GitHub Actions recently.
Using the GitHub mirror will reduce the load we are putting
on OSGeo's self-hosted servers too.
We intentionally include the project in farm.info.yml, because we handle
packaging ourselves via GitHub Actions.
This line was added in https://www.drupal.org/project/farm/issues/3336698
This caused the following CodeSniffer warning:
FILE: /opt/drupal/web/profiles/farm/farm.info.yml
----------------------------------------------------------------------
FOUND 0 ERRORS AND 1 WARNING AFFECTING 1 LINE
----------------------------------------------------------------------
1 | WARNING | Remove "project" from the info file, it will be added
| | by drupal.org packaging automatically
----------------------------------------------------------------------
This fixes the following errors:
- Property Drupal\farm_geo\GeometryWrapper::$geometry has unknown class Geometry as its type.
- Parameter $geometry of method Drupal\farm_geo\GeometryWrapper::__construct() has invalid type Geometry.
- Instantiated class GeometryCollection not found.
By doing this, we will be forcing the end-user to follow best
practice by making an intentional decision about the version
they will use. We do not want farmos/farmos:2.x to be referenced
by default in the docs, otherwise we will be directing folks to
use the development branch, which may not be stable, and may
change if they update the image via `docker pull`. We also don't
want to recommend farmos/farmos:latest, for a similar reason:
when updating between versions it is important to manually run
update.php. By forcing intentional version use and updates, we
encourage best practice for updates as well.