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

build: fixing provenance workflow by removing runs-on parameter which conflicts with uses #267

Merged
merged 1 commit into from
Feb 9, 2024

Conversation

rsoberano-ld
Copy link
Contributor

Requirements

  • I have added test coverage for new or changed functionality
  • I have followed the repository's pull request submission guidelines
  • I have validated my changes against all supported platform versions

Related issues

Provide links to any issues in this repository or elsewhere relating to this pull request.

Describe the solution you've provided

Provide a clear and concise description of what you expect to happen.

Describe alternatives you've considered

Provide a clear and concise description of any alternative solutions or features you've considered.

Additional context

Add any other context about the pull request here.

@rsoberano-ld rsoberano-ld requested a review from a team February 9, 2024 22:30
@rsoberano-ld
Copy link
Contributor Author

Tested with manual publish dry run in branch here: https://github.com/launchdarkly/python-server-sdk/actions/runs/7850310016

@rsoberano-ld rsoberano-ld changed the title build: fixing provnenace workflow by removing runs-on parameter which conflicts with uses build: fixing provenance workflow by removing runs-on parameter which conflicts with uses Feb 9, 2024
@rsoberano-ld rsoberano-ld merged commit 13d88e9 into main Feb 9, 2024
12 checks passed
@rsoberano-ld rsoberano-ld deleted the rsoberano/SEC-5003/python-sdk-provenance-fix branch February 9, 2024 23:02
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