Setting the constraint composer require bk2k/bootstrap-package:"10.0.x@dev" doesn't select the related branch alias 10.0.x-dev.

Executing composer req bk2k/bootstrap-package:"10.0.x@dev" does install the related branch alias:
- Installing bk2k/bootstrap-package (dev-BP_10-0 0ca6a93): Cloning 0ca6a93685 from cache

I've stumble upon this issue several time and I don't know if it's something I'm doing wrong or a real issue.

When I try to test constraints for the package roots/wordpress, I'm shown a list of two possible package for that name roots/wordpress and roots/wordpress-core-installer.

If I click on roots/wordpress-core-installer the website correctly update with the results. But if I try to choose roots/wordpress nothing happens (or I should say the website refresh but still want me to "choose" between the two options).

I can't find a way around this behavior.

Tag a 1.0.0 release and add a link to the public Changehub page

dev, alpha, beta, RC, stable (default).

https://semver.madewithlove.com/

Right now dev-master links to https://github.com/vendor/repo/releases/tag/dev-master which results in 404. Change to https://github.com/vendor/repo/tree/master instead.

I like this service a lot, but currently it seems to only rely on Packagist proper, but I often need similar services from https://packages.drupal.org/8/packages.json : (equivalent version exists with /7) It would be nice if the site would default to Packagist, but also support a set of well-known directories like this one. Adding free entry for the directory URL woud probably for more security-vetting, but it seems just adding a list of a few alternate repos should not be a problem.

Hi there :)

I'm running into the following problem
https://semver.mwl.be SSL_connect returned=1 errno=0 state=SSLv3 read server certificate B: certificate verify failed

The certificate verification fails, because the Let's Encrypt certificate is expired.

Best, Jens

https://github.com/madewithlove/projects-banner
shanks!

<script type="text/javascript" src="https://rawgit.com/madewithlove/projects-banner/gh-pages/dist/madewithlove-projects-banner.min.js"></script>

http://semver.mwl.be/#?package=phpdocumentor%2Fphpdocumentor

With the current version running on the public server, the version & stability constraint selectors are ignored leading to invalid results.

e.g. https://semver.mwl.be/#?package=madewithlove%2Felasticsearcher&version=0.4.1&minimum-stability=dev

should only highlight 0.4.1 but it seems to ignore both parameters and only highlights all stable versions no matter what is selected.

BTW: When debugging the cause I realized that your server outputs debug details (i.e. for 404s) - in case that's not intended...

https://semver.madewithlove.com/ throws 500 error.

See http://semver.mwl.be/#?package=symfony%2Fsymfony&version=%3C2.7.0&minimum-stability=dev

2.7.0-beta1 should be considered lower than the 2.7.0 release and so be matched here. But your code does not match it

GET /packages/{vendor}/{package}

now returns

{
    "default_constraint": "~1.0",
    "versions": [...]
}

The default constraint can be filled in the second input field if it is empty.

In future versions of composer this will probably change to something with a caret (^)

How could I use semver with repositories different to packagist.org?

When focusing on the input fields it should clear both the package name and version number field.

The test method names are displayed weirdly (for example, see this). And my IDE displays it like so:

I wonder, is this intentional? If not, I'm happy to work on a PR that replaces them all with an underscore.

It would be neat if this could be used to test version constraints against the virtual php package representing the current PHP language runtime.

Testing phpunit/phpunit and ~4.2 includes 4.3, 4.4, 4.5, 4.6, 4.7, and 4.8 as valid versions

It shouldn't, I expect those values to only be returned when using the caret version ^4.2

• Tilde ~4.2 -> https://semver.mwl.be/#?package=phpunit%2Fphpunit&version=~4.2
• Caret ^4.2 -> https://semver.mwl.be/#?package=phpunit%2Fphpunit&version=^4.2

Hello there, thanks for this neat tool!

I found some weird behavior today: You're not able to fetch the versions for psalm/phar here: https://semver.mwl.be/#!?package=psalm%2Fphar&version=%5E3.12&minimum-stability=stable

The error actually is caused by this: https://semver.mwl.be/packages/psalm/phar

Would be neat if this also supported platform packages, like php, lib-curl, ext-gd, etc.

Not sure where one would get the available versions from though... 🤔

Currently, the package versions fetching is broken.

When clicking the Search button, the XHR get a 500 HTTP response.

Requesting the URL https://semver.mwl.be/packages/madewithlove/elasticsearcher gives the following result:

Screenshot

Exception

ErrorException thrown with message "Argument 2 passed to Packagist\Api\Result\Factory::createResult() must be of the type array, null given, called in /home/forge/default/vendor/knplabs/packagist-api/src/Packagist/Api/Result/Factory.php on line 81 and defined"

Stacktrace

#24 ErrorException in /home/forge/default/vendor/knplabs/packagist-api/src/Packagist/Api/Result/Factory.php:103
#23 Semver\Services\Error\ServiceProvider:Semver\Services\Error\{closure} in /home/forge/default/vendor/knplabs/packagist-api/src/Packagist/Api/Result/Factory.php:103
#22 Packagist\Api\Result\Factory:createResult in /home/forge/default/vendor/knplabs/packagist-api/src/Packagist/Api/Result/Factory.php:81
#21 Packagist\Api\Result\Factory:createPackageResults in /home/forge/default/vendor/knplabs/packagist-api/src/Packagist/Api/Result/Factory.php:29
#20 Packagist\Api\Result\Factory:create in /home/forge/default/vendor/knplabs/packagist-api/src/Packagist/Api/Client.php:221
#19 Packagist\Api\Client:create in /home/forge/default/vendor/knplabs/packagist-api/src/Packagist/Api/Client.php:173
#18 Packagist\Api\Client:respond in /home/forge/default/vendor/knplabs/packagist-api/src/Packagist/Api/Client.php:98
#17 Packagist\Api\Client:get in /home/forge/default/app/Semver/Services/Repositories/PackageVersionsRepository.php:31
#16 Semver\Services\Repositories\PackageVersionsRepository:getVersions in /home/forge/default/app/Semver/Services/Repositories/PackageVersionsCacheRepository.php:46
#15 Semver\Services\Repositories\PackageVersionsCacheRepository:Semver\Services\Repositories\{closure} in /home/forge/default/vendor/illuminate/cache/Repository.php:292
#14 Illuminate\Cache\Repository:remember in /home/forge/default/app/Semver/Services/Repositories/PackageVersionsCacheRepository.php:47
#13 Semver\Services\Repositories\PackageVersionsCacheRepository:getVersions in /home/forge/default/app/Semver/Services/Packagist/Packagist.php:154
#12 Semver\Services\Packagist\Packagist:getRawVersions in /home/forge/default/app/Semver/Services/Packagist/Packagist.php:65
#11 Semver\Services\Packagist\Packagist:getVersions in /home/forge/default/app/Semver/Http/Controllers/PackageController.php:43
#10 Semver\Http\Controllers\PackageController:versions in [internal]:0
#9 ReflectionMethod:invokeArgs in /home/forge/default/vendor/league/container/src/ReflectionContainer.php:71
#8 League\Container\ReflectionContainer:call in /home/forge/default/vendor/league/container/src/Container.php:211
#7 League\Container\Container:call in /home/forge/default/vendor/league/route/src/Strategy/ParamStrategy.php:17
#6 League\Route\Strategy\ParamStrategy:dispatch in /home/forge/default/vendor/league/route/src/Route.php:92
#5 League\Route\Route:dispatch in /home/forge/default/vendor/league/route/src/Dispatcher.php:62
#4 call_user_func_array in /home/forge/default/vendor/league/route/src/Dispatcher.php:62
#3 League\Route\Dispatcher:handleFound in /home/forge/default/vendor/league/route/src/Dispatcher.php:43
#2 League\Route\Dispatcher:handle in /home/forge/default/vendor/league/route/src/RouteCollection.php:117
#1 League\Route\RouteCollection:dispatch in /home/forge/default/app/Semver/Application.php:57
#0 Semver\Application:run in /home/forge/default/public/index.php:11

Environment & details

GET Data

empty

POST Data

empty

Files

empty

Cookies

empty

Session

empty

Server/Request Data

Environment Variables

empty

Registered Handlers

0. Whoops\Handler\PrettyPageHandler

See composer/composer#7238.

by adding a boolean for example

I'm trying to use version with stability-flags, but it does not seem to be matching. For example: https://semver.mwl.be/#?package=monolog%2Fmonolog&version=1.0.*@dev&minimum-stability=stable.

Maybe the stability-flags override the Minimum Stability or auto-change dropdown (after read the docs below, i think its more Composer-like the override method).

Testing with composer, the match is different. Please check composer documentation bellow:
https://getcomposer.org/doc/articles/versions.md#stability
https://getcomposer.org/doc/04-schema.md#package-links

I would like to thank you for this tool, its really useful.

It could be a nice feature if the package name could work with autocomplete.

Certificate expired July 7, 2018

I can enter @dev in the version and then select dev as stability, and all versions including dev-main are selected.

The generated code is:

composer require madewithlove/htaccess-cli:"@dev@dev"

composer does not like that and says:

Could not parse version constraint @dev: Invalid version string "@dev"

Test URL: https://semver.madewithlove.com/?package=madewithlove%2Fhtaccess-cli&constraint=%40dev&stability=dev

So people can see what changed directly maybe? What do you think