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

patch hosted runner #185

Merged
merged 1 commit into from
Jan 14, 2025
Merged

patch hosted runner #185

merged 1 commit into from
Jan 14, 2025

Conversation

sundarshankar89
Copy link
Contributor

Temp fix to move to hosted runner for publishing artifact.

Copy link

✅ 40/40 passed, 2 skipped, 1m17s total

Running from acceptance #253

@gueniai gueniai merged commit 0442a68 into main Jan 14, 2025
10 checks passed
@gueniai gueniai deleted the patch/hosted_runner branch January 14, 2025 14:30
gueniai added a commit that referenced this pull request Jan 14, 2025
* patch hosted runner ([#185](#185)). In this release, we have implemented a temporary fix to address issues with publishing artifacts in the release workflow. This fix involves changing the runner used for the job from `ubuntu-latest` to a protected runner group labeled "linux-ubuntu-latest". This ensures that the job runs on a designated hosted runner with the specified configuration, enhancing the reliability and security of the release process. The `permissions` section of the job remains unchanged, allowing authentication to PyPI and signing of release artifacts with sigstore-python. It is worth noting that this is a stopgap measure, and further changes to the release workflow may be made in the future.
@gueniai gueniai mentioned this pull request Jan 14, 2025
gueniai added a commit that referenced this pull request Jan 14, 2025
* patch hosted runner
([#185](#185)). In
this release, we have implemented a temporary fix to address issues with
publishing artifacts in the release workflow. This fix involves changing
the runner used for the job from `ubuntu-latest` to a protected runner
group labeled "linux-ubuntu-latest". This ensures that the job runs on a
designated hosted runner with the specified configuration, enhancing the
reliability and security of the release process. The `permissions`
section of the job remains unchanged, allowing authentication to PyPI
and signing of release artifacts with sigstore-python. It is worth
noting that this is a stopgap measure, and further changes to the
release workflow may be made in the future.
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