build prerelease jupyterhub

[minrk]

adding a prerelease version constraint to requirements.in makes prerelease versions accepted

what happens to tags when the version is a prerelease?

[manics]

I think this has identified a couple issues in the GH workflow:

• From the PR workflow https://github.com/jupyterhub/jupyterhub-container-images/actions/runs/14310412937/job/40103778920?pr=7 the new tag will be 5.3.0rc0-0 only. It won't be tagged 5.3.0rc0 since the workflow only handles major.minor.patch tags.
• I didn't test rc/beta tags in https://github.com/jupyterhub/action-get-quayio-tags/blob/c099e60c0fd1b637385491a94b7f5f83ee89850a/__tests__/quayio.test.js#L117-L153 we should add some tests cases

[manics]

Can you add prereleaseHasBuild: "true" to all the jupyterhub/action-major-minor-tag-calculator@v3 steps?
manics@2ff70f4

[minrk]

I added the flag and added the credentials for quay and dockerhub. If we merge this, will 5.3.0rc0 be published?

[manics]

Yes, it should

[minrk]

ok, are we ready to land it, then?

[manics]

Failed 😢
https://github.com/jupyterhub/jupyterhub-container-images/actions/runs/14378904626/job/40317797819

Run jupyterhub/[email protected]
  with:
    repository: jupyterhub/jupyterhub
    version: 5.3.0rc0
    allTags: false
    strict: true
  env:
    LATEST_BRANCH: main
    PUBLISH_BRANCH: main
    IMAGE: jupyterhub/jupyterhub
    SINGLEUSER: jupyterhub/singleuser
    PUBLISH_DOCKERIO: true
    CACHE_FROM: type=gha
    CACHE_TO: type=gha,mode=max
Error: Invalid version, must be MAJOR.MINOR.PATCH: 5.3.0rc0

I can't think of any obvious reason for the failure since the PR CI runs were fine

[manics]

https://github.com/jupyterhub/action-get-quayio-tags/blob/v0.1.0/src/quayio.js#L57-L65
strict is true here:

jupyterhub-container-images/.github/workflows/build.yml

Line 80 in bdcdd21

strict: "true"

but I'm still confused by why it was fine in the PR runs.