robdesilets's avatar

Upgrading from 13.6.1

Hi All,

I did my daily "composer update" today and something caught my eye:

Upgrading laravel/framework (v13.16.1 => 13.x-dev 2107d3d): Extracting archive

Usually it will go from a version to a [higher] version not some weird dev branch.

To my knowledge I have not changed anything in my environment that would cause me to grab a developer branch and was wondering what's up.

Is anyone else seeing this?

(I am going to refrain from deploying this)

Thanks!

-Rob

1 like
5 replies
JussiMannisto's avatar

What is minimum-stability set to in your composer.json file?

1 like
robdesilets's avatar

Interesting:

"minimum-stability": "dev", "prefer-stable": true,

That's probably the issue, it's been like this for years from back to Laravel 6.

I have just never seen a dev branch come down before (maybe I never noticed).

Thanks, I will change to "stable".

1 like
robdesilets's avatar

Hmm.. when I make that change it won't update as some other packages (like mailgun) require "dev".

1 like
robdesilets's avatar

I did this and it seems to work:

"laravel/framework": "^13.2.0@stable",

1 like
JussiMannisto's avatar

Hmm.. when I make that change it won't update as some other packages (like mailgun) require "dev".

That's not right. If we're talking about the mailer package, it definitely has stable releases.

What may have happened: since your composer file allowed dev versions, while installing the mailer you may have added a version constraint that doesn't yet exist as a stable release.

If you're worried about unstable versions, setting the constraint on a single package doesn't make the problem go away. Your project and all its dependencies can still install unstable versions. Even if laravel/framework itself is stable, dependency installed by it are not.

I'd switch to stable and fix the conflicting version constraints one by one.

1 like

Please or to participate in this conversation.