Revisions to My created contrib theme not available from composer require, but release created on project page and on git.drupal.org - what's incorrect/missing?

evidence of dev release of another module being installable via composer

Source Link

edited Aug 8 at 19:03

2.4k
3
32
60

I've created a contrib theme project page https://www.drupal.org/project/thisisme and pushed code to git.drupal.org and created releases.

But I can't get the module using composer require, e.g.

composer require drupal/thisisme

Gives:

./composer.json has been updated
Running composer update drupal/thisisme
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires drupal/thisisme, it could not be found in any version, there may be a typo in the package name.

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.
 - It's a private package and you forgot to add a custom repository to find it

I've also tried releases suffixes e.g.

composer require drupal/thisisme:1.0.x-dev

My minimum stablity is set to dev in composer.json

I've created a contrib module in the recent past and that has worked fine with composer require-ing it: https://www.drupal.org/project/smart_date_time_tbc/ and I am able to use that with composer require drupal/smart_date_time_tbc:1.0.x-dev . Therefore

Therefore, just having an identified development version seems to be enough to be able to use it in composer. - which is evidenced here: https://www.drupal.org/project/smart_date_time_tbc/releases/1.0.x-dev and screenshot below:

As an aside - my confusion about version numbering in different places (is this related to my problem)?

As an aside, I am a bit confused by why the versioning is in three places and with the possibility of differing version numbers, i.e.:

in the thisisme.info.yml file we could have:

version: 1.0

(or maybe even, anything we like?!)

In git.drupal.org, the branch is 1.0.x
And on the project page a created release is 1.0.x-dev, not 1.0.x - named after the branch name.

How does composer package manager "connect" to git.drupal.org such that composer require can fetch a drupal project, what does composer need to see?

Related research:

I've created a contrib theme project page https://www.drupal.org/project/thisisme and pushed code to git.drupal.org and created releases.

But I can't get the module using composer require, e.g.

composer require drupal/thisisme

Gives:

./composer.json has been updated
Running composer update drupal/thisisme
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires drupal/thisisme, it could not be found in any version, there may be a typo in the package name.

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.
 - It's a private package and you forgot to add a custom repository to find it

I've also tried releases suffixes e.g.

composer require drupal/thisisme:1.0.x-dev

My minimum stablity is set to dev in composer.json

I've created a contrib module in the recent past and that has worked fine with composer require-ing it: https://www.drupal.org/project/smart_date_time_tbc/ and I am able to use that with composer require drupal/smart_date_time_tbc:1.0.x-dev . Therefore, just having an identified development version seems to be enough to be able to use it in composer.

As an aside - my confusion about version numbering in different places (is this related to my problem)?

As an aside, I am a bit confused by why the versioning is in three places and with the possibility of differing version numbers, i.e.:

in the thisisme.info.yml file we could have:

version: 1.0

(or maybe even, anything we like?!)

In git.drupal.org, the branch is 1.0.x
And on the project page a created release is 1.0.x-dev, not 1.0.x - named after the branch name.

How does composer package manager "connect" to git.drupal.org such that composer require can fetch a drupal project, what does composer need to see?

Related research:

I've created a contrib theme project page https://www.drupal.org/project/thisisme and pushed code to git.drupal.org and created releases.

But I can't get the module using composer require, e.g.

composer require drupal/thisisme

Gives:

./composer.json has been updated
Running composer update drupal/thisisme
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires drupal/thisisme, it could not be found in any version, there may be a typo in the package name.

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.
 - It's a private package and you forgot to add a custom repository to find it

I've also tried releases suffixes e.g.

composer require drupal/thisisme:1.0.x-dev

My minimum stablity is set to dev in composer.json

I've created a contrib module in the recent past and that has worked fine with composer require-ing it: https://www.drupal.org/project/smart_date_time_tbc/ and I am able to use that with composer require drupal/smart_date_time_tbc:1.0.x-dev .

Therefore, just having an identified development version seems to be enough to be able to use it in composer - which is evidenced here: https://www.drupal.org/project/smart_date_time_tbc/releases/1.0.x-dev and screenshot below:

As an aside - my confusion about version numbering in different places (is this related to my problem)?

As an aside, I am a bit confused by why the versioning is in three places and with the possibility of differing version numbers, i.e.:

in the thisisme.info.yml file we could have:

version: 1.0

(or maybe even, anything we like?!)

In git.drupal.org, the branch is 1.0.x
And on the project page a created release is 1.0.x-dev, not 1.0.x - named after the branch name.

How does composer package manager "connect" to git.drupal.org such that composer require can fetch a drupal project, what does composer need to see?

Related research:

added more info about: I had outlined a previous successful dev version of module with composer but didn't detail the actual module involved

Source Link

edited Aug 8 at 8:36

therobyouknow

2.4k
3
32
60

I've created a contrib theme project page https://www.drupal.org/project/thisisme and pushed code to git.drupal.org and created releases.

But I can't get the module using composer require, e.g.

composer require drupal/thisisme

Gives:

./composer.json has been updated
Running composer update drupal/thisisme
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires drupal/thisisme, it could not be found in any version, there may be a typo in the package name.

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.
 - It's a private package and you forgot to add a custom repository to find it

I've also tried releases suffixes e.g.

composer require drupal/thisisme:1.0.x-dev

My minimum stablity is set to dev in composer.json

I've created a contrib module in the recent past and that has worked fine with composer require-ing it: https://www.drupal.org/project/smart_date_time_tbc/ and I am able to use that with composer require drupal/smart_date_time_tbc:1.0.x-dev . Therefore, just having an identified development version seems to be enough to be able to use it in composer.

As an aside - my confusion about version numbering in different places (is this related to my problem)?

As an aside, I am a bit confused by why the versioning is in three places and with the possibility of differing version numbers, i.e.:

in the thisisme.info.yml file we could have:

version: 1.0

(or maybe even, anything we like?!)

In git.drupal.org, the branch is 1.0.x
And on the project page a created release is 1.0.x-dev, not 1.0.x - named after the branch name.

How does composer package manager "connect" to git.drupal.org such that composer require can fetch a drupal project, what does composer need to see?

Related research:

I've created a contrib theme project page https://www.drupal.org/project/thisisme and pushed code to git.drupal.org and created releases.

But I can't get the module using composer require, e.g.

composer require drupal/thisisme

Gives:

./composer.json has been updated
Running composer update drupal/thisisme
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires drupal/thisisme, it could not be found in any version, there may be a typo in the package name.

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.
 - It's a private package and you forgot to add a custom repository to find it

I've also tried releases suffixes e.g.

composer require drupal/thisisme:1.0.x-dev

My minimum stablity is set to dev in composer.json

I've created a contrib module in the recent past and that has worked fine with composer require-ing it.

As an aside - my confusion about version numbering in different places (is this related to my problem)?

As an aside, I am a bit confused by why the versioning is in three places and with the possibility of differing version numbers, i.e.:

in the thisisme.info.yml file we could have:

version: 1.0

(or maybe even, anything we like?!)

In git.drupal.org, the branch is 1.0.x
And on the project page a created release is 1.0.x-dev, not 1.0.x - named after the branch name.

How does composer package manager "connect" to git.drupal.org such that composer require can fetch a drupal project, what does composer need to see?

Related research:

I've created a contrib theme project page https://www.drupal.org/project/thisisme and pushed code to git.drupal.org and created releases.

But I can't get the module using composer require, e.g.

composer require drupal/thisisme

Gives:

./composer.json has been updated
Running composer update drupal/thisisme
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires drupal/thisisme, it could not be found in any version, there may be a typo in the package name.

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.
 - It's a private package and you forgot to add a custom repository to find it

I've also tried releases suffixes e.g.

composer require drupal/thisisme:1.0.x-dev

My minimum stablity is set to dev in composer.json

I've created a contrib module in the recent past and that has worked fine with composer require-ing it: https://www.drupal.org/project/smart_date_time_tbc/ and I am able to use that with composer require drupal/smart_date_time_tbc:1.0.x-dev . Therefore, just having an identified development version seems to be enough to be able to use it in composer.

As an aside - my confusion about version numbering in different places (is this related to my problem)?

As an aside, I am a bit confused by why the versioning is in three places and with the possibility of differing version numbers, i.e.:

in the thisisme.info.yml file we could have:

version: 1.0

(or maybe even, anything we like?!)

In git.drupal.org, the branch is 1.0.x
And on the project page a created release is 1.0.x-dev, not 1.0.x - named after the branch name.

How does composer package manager "connect" to git.drupal.org such that composer require can fetch a drupal project, what does composer need to see?

Related research:

composer <-> git.drupal.org relationship

Source Link

edited Aug 8 at 0:14

therobyouknow

2.4k
3
32
60

I've created a contrib theme project page https://www.drupal.org/project/thisisme and pushed code to git.drupal.org and created releases.

But I can't get the module using composer require, e.g.

composer require drupal/thisisme

Gives:

./composer.json has been updated
Running composer update drupal/thisisme
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires drupal/thisisme, it could not be found in any version, there may be a typo in the package name.

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.
 - It's a private package and you forgot to add a custom repository to find it

I've also tried releases suffixes e.g.

composer require drupal/thisisme:1.0.x-dev

My minimum stablity is set to dev in composer.json

I've created a contrib module in the recent past and that has worked fine with composer require-ing it.

As an aside - my confusion about version numbering in different places (is this related to my problem)?

As an aside, I am a bit confused by why the versioning is in three places and with the possibility of differing version numbers, i.e.:

in the thisisme.info.yml file we could have:

version: 1.0

(or maybe even, anything we like?!)

In git.drupal.org, the branch is 1.0.x
And on the project page a created release is 1.0.x-dev, not 1.0.x - named after the branch name.

How does composer package manager "connect" to git.drupal.org such that composer require can fetch a drupal project, what does composer need to see?

Related research:

How to create a full project on drupal.org?

I've created a contrib theme project page https://www.drupal.org/project/thisisme and pushed code to git.drupal.org and created releases.

But I can't get the module using composer require, e.g.

composer require drupal/thisisme

Gives:

./composer.json has been updated
Running composer update drupal/thisisme
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires drupal/thisisme, it could not be found in any version, there may be a typo in the package name.

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.
 - It's a private package and you forgot to add a custom repository to find it

I've also tried releases suffixes e.g.

composer require drupal/thisisme:1.0.x-dev

My minimum stablity is set to dev in composer.json

I've created a contrib module in the recent past and that has worked fine with composer require-ing it.

As an aside - my confusion about version numbering in different places (is this related to my problem)?

As an aside, I am a bit confused by why the versioning is in three places and with the possibility of differing version numbers, i.e.:

in the thisisme.info.yml file we could have:

version: 1.0

(or maybe even, anything we like?!)

In git.drupal.org, the branch is 1.0.x
And on the project page a created release is 1.0.x-dev, not 1.0.x - named after the branch name.

Related research:

I've created a contrib theme project page https://www.drupal.org/project/thisisme and pushed code to git.drupal.org and created releases.

But I can't get the module using composer require, e.g.

composer require drupal/thisisme

Gives:

./composer.json has been updated
Running composer update drupal/thisisme
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires drupal/thisisme, it could not be found in any version, there may be a typo in the package name.

Potential causes:
 - A typo in the package name
 - The package is not available in a stable-enough version according to your minimum-stability setting
   see <https://getcomposer.org/doc/04-schema.md#minimum-stability> for more details.
 - It's a private package and you forgot to add a custom repository to find it

I've also tried releases suffixes e.g.

composer require drupal/thisisme:1.0.x-dev

My minimum stablity is set to dev in composer.json

I've created a contrib module in the recent past and that has worked fine with composer require-ing it.

As an aside - my confusion about version numbering in different places (is this related to my problem)?

As an aside, I am a bit confused by why the versioning is in three places and with the possibility of differing version numbers, i.e.:

in the thisisme.info.yml file we could have:

version: 1.0

(or maybe even, anything we like?!)

In git.drupal.org, the branch is 1.0.x
And on the project page a created release is 1.0.x-dev, not 1.0.x - named after the branch name.

How does composer package manager "connect" to git.drupal.org such that composer require can fetch a drupal project, what does composer need to see?

Related research:

How to create a full project on drupal.org?

Source Link

asked Aug 8 at 0:04

therobyouknow

2.4k
3
32
60

Loading

Stack Exchange Network

Return to Question