Translate "Drupal CMS Geo Images - Recipe" Module project into General project

Done, https://packagist.org/packages/drupal/drupal_cms_geo_images will be available soon.

Note: Unfortunately I couldn't find any official guideline that instructs a Drupal Recipe should be created as a "General project". Is it something out there on this?

We should get this documented. Where did you look for the documentation?

thanks a lot @drumm for this quick fix.

Well, of course I looked into the
Drupal.org Recipes page: https://www.drupal.org/docs/extending-drupal/drupal-recipes →
(and nothing from there, and also both in the Distributions and Recipes initiative and the Drupal Recipe Cookbook referenced pages, etc.)

I also think something should / might be clearly mentioned in the following pages:

• How to create a new project → , where the "General Project" is described ...
• the https://www.drupal.org/docs/develop/managing-a-drupalorg-theme-module-or... → , itself ...

Sorry @drumm but I feel to reopen this,
as the following composer require commands:

ddev composer require drupal/drupal_cms_geo_images
ddev composer require drupal/drupal_cms_geo_images:^1.0

are always and still returning the following (same require drupal/core ~8.0) error:

  Problem 1
    - Root composer.json requires drupal/drupal_cms_geo_images * -> satisfiable by drupal/drupal_cms_geo_images[1.0.0, ..., 1.1.0].
    - drupal/drupal_cms_geo_images[1.0.0, ..., 1.1.0] require drupal/core ~8.0 -> found drupal/core[8.0.0-beta6, ..., 8.9.x-dev] but the package is fixed to 11.1.2 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require drupal/drupal_cms_geo_images:*" to figure out if any version is installable, or "composer require drupal/drupal_cms_geo_images:^2.1" if you know which you need.

and also the following

ddev composer show drupal/drupal_cms_geo_images -a

still returns

requires
drupal/core ~8.0

Why is this still not working as expected, and simply

requires
"drupal/core": ">=10.4"

Its code base is indeed the same of this parallel packagist, deployed on the branch 2.x with composer.json name: itamair/drupal_cms_geo_images
and on which the following composer require works and applies fine on Drupal CMS (11.2):

ddev composer require itamair/drupal_cms_geo_images

Could you also test and confirm that I am not doing anything wrong here and what could be wrong still and instead?

I believe this is local caching. Please try composer show drupal/drupal_cms_geo_images -a --no-cache

The full output of composer show might show more clues that your composer is still using packages.drupal.org data instead of switching to packagist.org.

thanks for the tip ...
but no way, still.

~/Sites/Drupal_CMS_package/drupal-cms git:[master]
composer show drupal/drupal_cms_geo_images -a --no-cache
name     : drupal/drupal_cms_geo_images
descrip. : 
keywords : 
versions : 1.1.0, 1.0.6, 1.0.5, 1.0.4, 1.0.3, 1.0.2, 1.0.1, 1.0.0
type     : drupal-module
license  : GNU General Public License v2.0 or later (GPL-2.0-or-later) (OSI approved) https://spdx.org/licenses/GPL-2.0-or-later.html#licenseText
homepage : https://www.drupal.org/project/drupal_cms_geo_images
source   : [git] https://git.drupalcode.org/project/drupal_cms_geo_images.git 1.1.0
dist     : [zip] https://ftp.drupal.org/files/projects/drupal_cms_geo_images-1.1.0.zip 1.1.0
names    : drupal/drupal_cms_geo_images

support
source : https://git.drupalcode.org/project/drupal_cms_geo_images

requires
drupal/core ~8.0

could you also try yourself on a local Drupal CMS instance of you ... or any other Drupal 9 or 10 instance?

I see where our CDN cache was holding onto the old version now, should be actually resolved now.

Thanks! I confirm that it can be correctly required via composer ...

Automatically closed - issue fixed for 2 weeks with no activity.