ensure nightly builds always produce new packages

[jameslamb]

Contributes to rapidsai/build-planning#218

• uses the new patterns for versioning nightly packages (see builds: add support for computing a date-based version component at build time rapidsai/shared-workflows#603), to ensure they're always uploaded on new builds.

For wheels:

# before
26.10.0a55 

# after
26.10.0a55.post260803200854

And for conda:

# before
26.10.0a55[build=cuda12_260803_9da146ef]

# after
26.10.0a55[build=cuda12_260803200854_9da146ef]

Notes for Reviewers

How I tested this

See rapidsai/cugraph-gnn#508

[copy-pr-bot]

Auto-sync is disabled for draft pull requests in this repository. Workflows must be run manually.

Contributors can view more details about this message here.

[jameslamb]

/ok to test

[jameslamb]

/ok to test

[github-actions]

CI Test Summary

✅ All 31 test job(s) passed.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Enterprise

Run ID: 7238e482-59ce-4c8f-b685-1305dfc75b8c

📥 Commits

Reviewing files that changed from the base of the PR and between a919638 and e5b1aa9.

📒 Files selected for processing (1)

• python/cuopt_server/cuopt_server/utils/job_queue.py

---

📝 Walkthrough

Walkthrough

The workflows now generate one build-datetime value and pass it to C++, Python, wheel, and Conda builds. Build scripts and Conda recipes use datetime-based identifiers. Client version checking accepts additional version segments.

Changes

Build timestamp propagation

Layer / File(s)	Summary
Workflow timestamp orchestration .github/workflows/build.yaml, .github/workflows/pr.yaml	Both workflows run build-details, pass its build-datetime output to build jobs, and update job dependencies.
Datetime-based build inputs ci/build_cpp.sh, ci/build_python.sh, ci/build_wheel.sh	Build scripts source rapids-datetime-string. Wheel versions include a .post datetime suffix.
Conda build string updates conda/recipes/*/recipe.yaml	Recipes use RAPIDS_DATETIME_STRING, datetime_string, and datetime-based package build strings.

Job queue version parsing

Layer / File(s)	Summary
Version component parsing python/cuopt_server/cuopt_server/utils/job_queue.py	check_client_version accepts version strings with more than three dot-separated components.

Estimated code review effort: 2 (Simple) | ~10 minutes

Suggested reviewers: tmckayus

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title clearly summarizes the main change: ensuring nightly builds produce new packages.
Description check	✅ Passed	The description directly explains the nightly versioning changes and how they ensure new wheel and conda packages are uploaded.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[jameslamb]

cuopt server tests were failing like this:

  File "/pyenv/versions/3.12.13/lib/python3.12/site-packages/cuopt_server/utils/job_queue.py", line 54, in check_client_version
    major, minor, _ = __version__.split(".")
    ^^^^^^^^^^^^^^^
ValueError: too many values to unpack (expected 3)

(build link)

This PR now adds a 4th component to nightly versions (e.g. 26.10.0a14.post260807023309).

Since this code only cares about the first 2 components (major and minor), just throwing away the others with * seems defensible.

I looked for other patterns like this in the codebase and didn't see any.

[jameslamb]

/merge