Skip to content

PHP 8.5 | UPGRADING: add missing finfo function - #23263

Merged
DanielEScherzer merged 1 commit into
php:PHP-8.5from
jrfnl:php-8.5/upgrading-add-missing-mention
Aug 15, 2026
Merged

PHP 8.5 | UPGRADING: add missing finfo function#23263
DanielEScherzer merged 1 commit into
php:PHP-8.5from
jrfnl:php-8.5/upgrading-add-missing-mention

Conversation

@jrfnl

@jrfnl jrfnl commented Aug 13, 2026

Copy link
Copy Markdown
Contributor

The entry about the new function parameter for finfo, is missing the OO method.
See: ba21ab4

The entry about the new function parameter for finfo, is missing the OO method.
See: php@ba21ab4
@LamentXU123

Copy link
Copy Markdown
Member

@iliaal Do we fix 8.5 UPGRADING file? This is correct.

@kamil-tekiela

Copy link
Copy Markdown
Member

What's the point in fixing this? PHP 8.5 has shipped and I don't think we're going to use this version of UPGRADING for anything.

@LamentXU123

Copy link
Copy Markdown
Member

That's exactly my point. Although this is technically correct I don't see the reason to fix this since 8.5 is shipped.

@iliaal

iliaal commented Aug 14, 2026

Copy link
Copy Markdown
Contributor

Ditto, this already shipped, no reason to do this

@jrfnl

jrfnl commented Aug 14, 2026

Copy link
Copy Markdown
Contributor Author

If that's the policy, then why are there some 8 other updates to the PHP 8.5 UPGRADING guide which have been committed since the release ?

https://github.com/php/php-src/commits/PHP-8.5/UPGRADING

@LamentXU123

LamentXU123 commented Aug 14, 2026

Copy link
Copy Markdown
Member

I think mostly I or David do this when merging up. This is meaningless so we will prevent this in the future (?)
Well, given this I think we can let the 8.5 RM to decide @edorian
Perhaps I close this too soon. My apologies.

@LamentXU123 LamentXU123 reopened this Aug 14, 2026
@jrfnl

jrfnl commented Aug 14, 2026

Copy link
Copy Markdown
Contributor Author

No worries @LamentXU123. If the update is not desired, that's fine. Just wanted to point out that in that case such policy should probably be applied consistently.

@kamil-tekiela

Copy link
Copy Markdown
Member

No worries @LamentXU123. If the update is not desired, that's fine. Just wanted to point out that in that case such policy should probably be applied consistently.

I don't know if there is a policy. It's more about common sense. If the file doesn't need to be changed, then let's not bother.

@DanielEScherzer
DanielEScherzer requested a review from a team August 15, 2026 09:32

@DanielEScherzer DanielEScherzer left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me, RM approval


@LamentXU123 I'm not sure about adding post-GA bug fixes into UPGRADING, since it is normally assumed to document just the parts that are there since the start of the releases, but this is about something that we included pre-GA and just not documented, so all the more reason it should be added

@DanielEScherzer
DanielEScherzer merged commit ab2bf46 into php:PHP-8.5 Aug 15, 2026
3 checks passed
DanielEScherzer added a commit that referenced this pull request Aug 15, 2026
* PHP-8.5:
  PHP 8.5 | UPGRADING: add missing finfo function (#23263)
@kamil-tekiela

Copy link
Copy Markdown
Member

Looks good to me, RM approval

@LamentXU123 I'm not sure about adding post-GA bug fixes into UPGRADING, since it is normally assumed to document just the parts that are there since the start of the releases, but this is about something that we included pre-GA and just not documented, so all the more reason it should be added

What is file used for after GA?

@jrfnl
jrfnl deleted the php-8.5/upgrading-add-missing-mention branch August 15, 2026 10:21
@jrfnl

jrfnl commented Aug 15, 2026

Copy link
Copy Markdown
Contributor Author

What is file used for after GA?

Many companies/projects only upgrade years after a new release.... And when the migration guide may not contain sufficient detail, UPGRADING is the place to look for an explanation of changed behaviour.

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

Successfully merging this pull request may close these issues.

5 participants