Add granular publish tags for "-bin" docker image

[glensc]

Implement TODO:

• pie/.github/workflows/release.yml

  Lines 90 to 96 in 5c3fa89

  	with:
  	# @TODO v1.0 Consider introducing more granular tags (major and major.minor)
  	# @see https://github.com/php/pie/pull/122#pullrequestreview-2477496308
  	# @see https://github.com/php/pie/pull/122#discussion_r1867331273
  	tags: |
  	${{ ((!contains(github.ref, 'alpha') && !contains(github.ref, 'beta') && !contains(github.ref, 'rc')) && 'type=raw,value=bin') || '' }}
  	type=semver,pattern={{version}},suffix=-bin

See:

• feat: CI job for building Docker binary-only images #122 (review)
• feat: CI job for building Docker binary-only images #122 (comment)
• Offer fine-grained (major/minor specific) Docker image tags #480

PR submitter checklist

• I have read CONTRIBUTING.md
• I discussed this feature with the maintainers in feat: CI job for building Docker binary-only images #122
• I have added appropriate tests
• I confirm that I have the right to submit this under the project's open source licence

Future TODO

After this is merged and verified working also update documentation (another PR):

• https://github.com/php/pie/blob/1.5.x/docs/usage.md#docker-installation

[asgrim]

@glensc please can you complete the PR submitter checklist; you can reference #122 in the second checklist item

[glensc]

@asgrim ✅

[jnoordsij]

This fixed #480, right?

However, I wonder if this implementation is entirely correct: for e.g. 1.5.0-alpha.1, this would now also update the 1-bin 'major' image if I understand things correctly.

Likely you'd want to distinguish stable and non-stable tags in some way, similar to how it's done for the floating bin tag.

[asgrim]

This fixed #480, right?

However, I wonder if this implementation is entirely correct: for e.g. 1.5.0-alpha.1, this would now also update the 1-bin 'major' image if I understand things correctly.

Likely you'd want to distinguish stable and non-stable tags in some way, similar to how it's done for the floating bin tag.

yep

[glensc]

This fixed #480, right?

However, I wonder if this implementation is entirely correct: for e.g. 1.5.0-alpha.1, this would now also update the 1-bin 'major' image if I understand things correctly.

Likely you'd want to distinguish stable and non-stable tags in some way, similar to how it's done for the floating bin tag.

I suppose similar guard can added there:

${{ ((!contains(github.ref, 'alpha') && !contains(github.ref, 'beta') && !contains(github.ref, 'rc')) && 'type=raw,value=bin') || '' }}

[glensc]

This also needs to be backported to 1.4.x branch?

[TimWolla]

Besides the obvious bug with pre-release versions, I wonder what problem this is attempting to solve. Is there ever a good reason to intentionally stay on an outdated branch of PIE?

[glensc]

Well, this is merged to 1.5, but there are no 1.5 releases.

I'm new to pie, so i'm not aware when will be 1.5.0 is released, and i would like to update my Dockerfile to 1.x branch, be it 1.4 or 1.5, not really relevant to me. i'm assuming the project follows basic semver.

[glensc]

This fixed #480, right?
However, I wonder if this implementation is entirely correct: for e.g. 1.5.0-alpha.1, this would now also update the 1-bin 'major' image if I understand things correctly.
Likely you'd want to distinguish stable and non-stable tags in some way, similar to how it's done for the floating bin tag.

I suppose similar guard can added there:

${{ ((!contains(github.ref, 'alpha') && !contains(github.ref, 'beta') && !contains(github.ref, 'rc')) && 'type=raw,value=bin') || '' }}

Fix:

• Fix: Skip semver tag patterns for pre-releases #620

It maybe not loking the nicest, it follows the same pattern, so should be easy to review