According to this URL,Packagist Semver Checker, this module does not have a publicly accessible alpha release.

Perhaps Composer gets releases from other places, but I wanted to make sure that other modules, specifically default_content_deploy are able to see release alpha8 and future releases.

(This whole thing might hinge on a misunderstanding of composer mechanics from my side. If so, my apologies, and please disregard and close.)

Thanks for the great module!

Comments

arnaldop created an issue. See original summary.

larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
commented
Category: Bug report » Feature request
Status: Active » Postponed (maintainer needs more info)

Are you using the Drupal packagist endpoint? i.e does your composer.json have this:

"repositories": {
        "packages.drupal": {
            "type": "composer",
            "url": "https://packages.drupal.org/8"
        }
}
larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
commented
Category: Feature request » Support request
Status: Postponed (maintainer needs more info) » Active

Are you using the Drupal packagist endpoint? i.e does your composer.json have this:

"repositories": {
        "packages.drupal": {
            "type": "composer",
            "url": "https://packages.drupal.org/8"
        }
}
arnaldop’s picture

arnaldop
Location St Cloud, FL
commented

Yes, I do. It is possible that the online tool I was using doesn't use the same repos.

You can go ahead and close this ticket because I think it's a red herring somewhere else.

Thanks so much!

larowlan’s picture

larowlan
Location 🇦🇺🏝.au GMT+10
commented
Status: Active » Closed (works as designed)

Sure, or you could too!

But yeah, I'd imagine that the tool doesn't know about the Drupal packagist repo

Phil Wolstenholme’s picture

Phil Wolstenholme commented
Status: Closed (works as designed) » Needs review

@larowlan I'm working for a client that has a private instance of Packagist. In our composer.json file we have their private Packagist instance at the top of the repositories list, so it overrides the Drupal.org one.

Their instance has picked up on https://packagist.org/packages/drupal/default_content which points to an out of date Github repo: https://github.com/larowlan/default_content and blocks us from using Default Content on D9.

Would you be able to remove https://packagist.org/packages/drupal/default_content or at least point it at the Drupal.org Gitlab repo for Default Content so it has access to the latest versions of the module please?

Phil Wolstenholme’s picture

Phil Wolstenholme commented

If anyone is having the same issue as me above, you can filter Default Content out of a specific Composer repository like so:

"repositories": {
    "private-packagist": {
        "type": "composer",
        "url": "https://repo.packagist.com/nameofclient",
        "exclude": ["drupal/default_content"]
    }
}
damienmckenna’s picture

damienmckenna
Location TN, USA
commented

This should be closed as a "works as designed".

thejimbirch’s picture

thejimbirch commented
Status: Needs review » Closed (works as designed)