Wrong version identified into PHAR distrib 1.1.0 (stable)

[llaville]

It's a very minor error, but the PHAR distribution available on https://github.com/php/pie/releases/tag/1.1.0 still identify the previous RC version.

Actual

🥧 PHP Installer for Extensions (PIE) 1.1.0-rc.1

Expected

🥧 PHP Installer for Extensions (PIE) 1.1.0

From current context

wget https://github.com/php/pie/releases/download/1.1.0/pie.phar

--2025-08-09 07:39:42--  https://github.com/php/pie/releases/download/1.1.0/pie.phar
Resolving github.com (github.com)... 140.82.121.4
Connecting to github.com (github.com)|140.82.121.4|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://release-assets.githubusercontent.com/github-production-release-asset/765049687/ec614656-ad34-4dc7-b415-a607febcaae2?sp=r&sv=2018-11-09&sr=b&spr=https&se=2025-08-09T08%3A37%3A19Z&rscd=attachment%3B+filename%3Dpie.phar&rsct=application%2Foctet-stream&skoid=96c2d410-5711-43a1-aedd-ab1947aa7ab0&sktid=398a6654-997b-47e9-b12b-9515b896b4de&skt=2025-08-09T07%3A36%3A53Z&ske=2025-08-09T08%3A37%3A19Z&sks=b&skv=2018-11-09&sig=gMPnHTp3fhoB%2BuR8gehy9yErXyc%2Fm3SwD4oSEO5%2Fn9Q%3D&jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmVsZWFzZS1hc3NldHMuZ2l0aHVidXNlcmNvbnRlbnQuY29tIiwia2V5Ijoia2V5MSIsImV4cCI6MTc1NDcyNTQ4MiwibmJmIjoxNzU0NzI1MTgyLCJwYXRoIjoicmVsZWFzZWFzc2V0cHJvZHVjdGlvbi5ibG9iLmNvcmUud2luZG93cy5uZXQifQ._ukgHPRCsLCmMsjXMTFA4FsqsyVSeIiVJXXhYme2oz4&response-content-disposition=attachment%3B%20filename%3Dpie.phar&response-content-type=application%2Foctet-stream [following]
--2025-08-09 07:39:42--  https://release-assets.githubusercontent.com/github-production-release-asset/765049687/ec614656-ad34-4dc7-b415-a607febcaae2?sp=r&sv=2018-11-09&sr=b&spr=https&se=2025-08-09T08%3A37%3A19Z&rscd=attachment%3B+filename%3Dpie.phar&rsct=application%2Foctet-stream&skoid=96c2d410-5711-43a1-aedd-ab1947aa7ab0&sktid=398a6654-997b-47e9-b12b-9515b896b4de&skt=2025-08-09T07%3A36%3A53Z&ske=2025-08-09T08%3A37%3A19Z&sks=b&skv=2018-11-09&sig=gMPnHTp3fhoB%2BuR8gehy9yErXyc%2Fm3SwD4oSEO5%2Fn9Q%3D&jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmVsZWFzZS1hc3NldHMuZ2l0aHVidXNlcmNvbnRlbnQuY29tIiwia2V5Ijoia2V5MSIsImV4cCI6MTc1NDcyNTQ4MiwibmJmIjoxNzU0NzI1MTgyLCJwYXRoIjoicmVsZWFzZWFzc2V0cHJvZHVjdGlvbi5ibG9iLmNvcmUud2luZG93cy5uZXQifQ._ukgHPRCsLCmMsjXMTFA4FsqsyVSeIiVJXXhYme2oz4&response-content-disposition=attachment%3B%20filename%3Dpie.phar&response-content-type=application%2Foctet-stream
Resolving release-assets.githubusercontent.com (release-assets.githubusercontent.com)... 185.199.111.133, 185.199.109.133, 185.199.108.133, ...
Connecting to release-assets.githubusercontent.com (release-assets.githubusercontent.com)|185.199.111.133|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 5994782 (5.7M) [application/octet-stream]
Saving to: ‘pie.phar’

pie.phar                            100%[===================================================================>]   5.72M  3.52MB/s    in 1.6s

2025-08-09 07:39:44 (3.52 MB/s) - ‘pie.phar’ saved [5994782/5994782]

[asgrim]

FYI I believe this is because both 1.1.0-rc.1 tag and 1.1.0 point to the same commit, and it's picked the less stable tag when packaging it. Will check into how to improve for future 😁

[derickr]

This does mean that pie self-update will now always try to update itself, which it did for me, every hour, since 5 days ago :-)

[asgrim]

Notes: tag 1.1.0 and 1.1.0-rc.1 point to the same commit, but it seems when box compile ran for the 1.1.0 build, it picked the RC tag:

https://github.com/php/pie/actions/runs/16815594752/job/47631497558

The pipeline runs when you create a GH release (not tag); and interestingly, git describe --tags HEAD (which I understand is what Box uses), it also shows 1.1.0-rc.1 not the 1.1.0 tag; so this is probably the cause.

The actions/checkout step doesn't seem to indicate it's checkout the wrong thing (in fact, it specifically checked out refs/tags/1.1.0 which is what I would expect):

Checking out the ref
  /usr/bin/git checkout --progress --force refs/tags/1.1.0
  Note: switching to 'refs/tags/1.1.0'.
...
/usr/bin/git log -1 --format=%H
28b3e0d324f29034e6c80eed3f63773ca78038dc

However, I can't reproduce locally currently:

$ git checkout 1.1.0-rc.1 
HEAD is now at 28b3e0d Merge pull request #303 from asgrim/dep-updates
$ git describe --tags HEAD
1.1.0
$ 

Need to do some more digging.

[asgrim]

Can reproduce with the following clean checkout steps:

mkdir pie-git-test
cd pie-git-test
git init
git remote add origin git@github.com:php/pie.git
git -c protocol.version=2 fetch --prune --no-recurse-submodules origin +refs/heads/*:refs/remotes/origin/* +refs/tags/*:refs/tags/*
git -c protocol.version=2 fetch --no-tags --prune --no-recurse-submodules origin +28b3e0d324f29034e6c80eed3f63773ca78038dc:refs/tags/1.1.0
git checkout --progress --force refs/tags/1.1.0
git describe --tags HEAD

[asgrim]

Using git fetch --tags --force seems to overcome the issue going forward. Thanks for the report and feedback, people :)

[llaville]

@asgrim Nice work on many investigation to fix this issue