Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CI: Split production and test releases into different jobs + disable attestation for production releases #86

Merged
merged 2 commits into from
Nov 5, 2024

Conversation

SmithChart
Copy link
Member

No description provided.

.github/workflows/check-and-publish.yaml Outdated Show resolved Hide resolved
In workflow
https://github.com/linux-automation/usbsdmux/actions/runs/11659598753/job/32460446373
we have seen that a dirty environment can be problematic for a workflow.
Here a leftover file from the publish to test.pypi.org caused the preflight
checks for the proper release to fail.

With this change we will use different jobs for both steps - thus starting
with a clean environment every time.

Signed-off-by: Chris Fiege <[email protected]>
With v1.11.0 gh-action-pypi-publish has switched on attestations by
default:
https://github.com/pypa/gh-action-pypi-publish/releases/tag/v1.11.0

According to it's README they are still beta:
https://github.com/pypa/gh-action-pypi-publish/blob/fb13cb306901256ace3dab689990e13a5550ffaa/README.md?plain=1#L102

So we will disable attestations for releases to production for now.
This way we can still evaluate this supply chain feature in testing, but
keep our stable release workflow more stable.

Attestations can be enabled for production once they are stable.

Signed-off-by: Chris Fiege <[email protected]>
@SmithChart SmithChart merged commit 051f381 into linux-automation:master Nov 5, 2024
7 checks passed
@SmithChart SmithChart deleted the disable-attestations branch November 5, 2024 11:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants