Would a patchlevel release be possible or is planned already ?

[sbuerk]

Is there any plan for a next (patchlevel) release ? Could not ind any release schedule.

Specially regarding the PHP8.4 required changes of merged #572 ?

[lolli42]

ping.

[lolli42]

Ping.
PHP is at 8.4.0 rc2, would be great to have a compat release of this library.

[ruudk]

@bshaffer You are probably very busy, but could you please tag a new release so that projects that rely on this have a few less errors to worry about when preparing for PHP 8.4 😅 🙏

[ruudk]

@ajupazhamayil would you be able to help out with this?

[standa]

If this helps to anyone: we are running on the commit pin (which seems to work for the time being).

	"require": {
		"firebase/php-jwt": "dev-main#76808fa",
}

Just note composer validate complains a bit 😞

# General warnings
- The package "firebase/php-jwt" is pointing to a commit-ref, this is bad practice and can cause unforeseen issues.

[sbuerk]

Since PHP 8.4.1 has been released some days ago, could we expect a patchlevel release of this library containing already merged fixes after these couple of months?

It does not show much trust if a framework needs to say:

You can use our framework safely with PHP8.4, but as we rely on XY you need to use a composer patch for already merged but not released PHP8.4 fixes.

to announce official PHP8.4 support.

[hafezdivandari]

It seems that the repo is using the release-please bot for releases, and this bot doesn't take chore commits into account!

[sbuerk]

It seems that the repo is using the release-please bot for releases, and this bot doesn't take chore commits into account!

Damn. Should have made one of the pr commits a fix. What a pity that is not mentioned within the README.md.

[ruudk]

So would it help if we do a new PR with a proper commit to get it tagged? There's probably something tiny code style thing we can tweak / fix.

[ruudk]

@hafezdivandari @sbuerk I think it would be solved with #583, agreed?

[sbuerk]

@hafezdivandari @sbuerk I think it would be solved with #583, agreed?

not sure if deps would lead to a release (don't know release-please) ... not that we have the same issue with the pr because it was only chore.

[hafezdivandari]

They usually squash and merge, so the fix prefix on the #583 PR title makes it a releasable unit 👍

[ruudk]

This can be closed

#585