Add 30-day retention for pip package artifacts in CI

[Copilot]

The CI workflow builds pip packages on every push but artifacts weren't explicitly retained, making them unavailable for experimentation in other projects.

Changes

• Added retention-days: 30 to the artifact upload step in .github/workflows/publish.yaml

The python-package-distributions artifact (wheel + source tarball) is now available for download from any workflow run for 30 days.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Add pip package in CI as build artifact</issue_title>
<issue_description>As an AI engineer I want to quickly experiment with the built pip package from main in other projects.
Currently the package is built but the artifact is not persisted in the GH workflow.
Therefore, add it as a build artifact and retain for 30 days.</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Add pip package in CI as build artifact #124

---

✨ Let Copilot coding agent set things up for you — coding agent works faster and does higher quality work when set up for your repo.

[Haydnspass]

@copilot but dis i just overlook the artifact or is the retention period really needed?

[Copilot]

@copilot but dis i just overlook the artifact or is the retention period really needed?

The artifact was already there - actions/upload-artifact@v4 was being used on lines 26-30. However, without the retention-days parameter, GitHub uses a default of 90 days. The issue specifically requested 30-day retention, so the change was needed to meet that requirement.

[Haydnspass]

Closed as already there.