Skip to content

Automate publication of ckan package to PyPI #8520

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

Merged
merged 3 commits into from
Nov 14, 2024
Merged

Automate publication of ckan package to PyPI #8520

merged 3 commits into from
Nov 14, 2024

Conversation

amercader
Copy link
Member

Part of #8143

This adds a new GitHub workflow to publish to

  • PyPI when a tag is pushed
  • Test PyPI when a PR is merged

Using test.pypi.org allows us to check that the workflow is healthy.

Besides the workflow file this has required setting up:

  • GitHub Actions environmnenst (pypi and testpypi). This allows us to define additional rules and limit how actions are run
  • Trusted Publishers on PyPI: This allows the actions to authenticate without having to share API tokens around

Part of #8143

This adds a new GitHub workflow to publish to

* PyPI when a tag is pushed
* Test PyPI when a PR is merged

Using test.pypi.org allows us to check that the workflow is healthy.

Besides the workflow file this has required setting up:

* [A GitHub Actions environmnent][1]. This allows us to define
  additional rules and limit how actions are run
* [Trusted Publishers][2] on PyPI: This allows the actions to
  authenticate without having to share API tokens around

[1]:
https://docs.github.com/en/actions/managing-workflow-runs-and-deployments/managing-deployments/managing-environments-for-deployment
[2]: https://docs.pypi.org/trusted-publishers/
@kowh-ai kowh-ai merged commit 328bf9e into master Nov 14, 2024
12 checks passed
@kowh-ai kowh-ai deleted the automate-pypi branch November 14, 2024 16:26
@ckanbot
Copy link

ckanbot commented Nov 14, 2024

Backport failed for dev-v2.11, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin dev-v2.11
git worktree add -d .worktree/backport-8520-to-dev-v2.11 origin/dev-v2.11
cd .worktree/backport-8520-to-dev-v2.11
git switch --create backport-8520-to-dev-v2.11
git cherry-pick -x c9102e65ec76418a94014b056f29e782cda83d62 a52c33c77016e76594dc4d4de4e3e5ffe5ad641c 89c2b5b49135f5ec051daa9de969f0b5b41d833f

@ckanbot
Copy link

ckanbot commented Nov 14, 2024

Backport failed for dev-v2.10, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin dev-v2.10
git worktree add -d .worktree/backport-8520-to-dev-v2.10 origin/dev-v2.10
cd .worktree/backport-8520-to-dev-v2.10
git switch --create backport-8520-to-dev-v2.10
git cherry-pick -x c9102e65ec76418a94014b056f29e782cda83d62 a52c33c77016e76594dc4d4de4e3e5ffe5ad641c 89c2b5b49135f5ec051daa9de969f0b5b41d833f

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants