Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Individual Illuminate packages are not updated since 5.5.17 #22462

Closed
aedart opened this issue Dec 18, 2017 · 5 comments
Closed

Individual Illuminate packages are not updated since 5.5.17 #22462

aedart opened this issue Dec 18, 2017 · 5 comments

Comments

@aedart
Copy link
Contributor

aedart commented Dec 18, 2017

  • Laravel Version: 5.5.17+
  • PHP Version:
  • Database Driver & Version:

Description:

Acc. to packagist, several illuminate packages are still at version 5.5.17, but the framework itself is now at 5.5.25. Has something happened in you release process, since the individual illuminate packages are no longer updated?

@browner12
Copy link
Contributor

if I remember correctly, this is not an automated process. I'm guessing the importance of the changes dictates a little how often they are updated.

@aedart
Copy link
Contributor Author

aedart commented Dec 18, 2017

@browner12, okay... but that wouldn't make any sense. Previously, before version 5.5.17, I received updates regularly, per illuminate package.

I find that this is a very important thing, especially for those of us that develop packages and require just a few illuminate package, instead of the entire framework. Said differently, if Laravel releases important bug-fixes, those appear not to be "pushed" to the individual packages.

@Miguel-Serejo
Copy link

I'm fairly certain individual packages only get their versions bumped when there are actual changes made to them.

If there's a patch that only affects one package, why should all other packages get a version bump?

More importantly, how does this negatively impact your package and why would things be better if, for example, the config package got version bumped after an unrelated fix to the session package if you're only requiring config and not session?

@aedart
Copy link
Contributor Author

aedart commented Dec 18, 2017

@36864, that sounds very reasonable. If that is the case, then this isn't an issue - however, when reviewed the available versions, I just noticed the version gab and got scared.

UPDATE: Well... I just checked illuminate/database - it does not match the version(s) available in the framework, also from 5.5.17. I read in the release notes for 5.5.25, which was released 2017-12-11. New features / changes to the package. These are only available via the entire framework.

No way that this is NOT a mistake! "Something"... does not update the individual packages...

@GrahamCampbell
Copy link
Member

Thanks. The packages will be updated soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants