Skip to content

Commit

Permalink
Package publishing workflow (#51)
Browse files Browse the repository at this point in the history
  • Loading branch information
nopcoder authored Mar 15, 2023
1 parent 476569e commit fbd2080
Show file tree
Hide file tree
Showing 2 changed files with 31 additions and 0 deletions.
24 changes: 24 additions & 0 deletions .github/workflows/publish.yaml
Original file line number Diff line number Diff line change
@@ -0,0 +1,24 @@
name: publish

on:
release:
types: [published]
workflow_dispatch:

jobs:
publish:
runs-on: ubuntu-latest
steps:
- name: Checkout
uses: actions/checkout@v3

- name: Build
run: python3 -m pip install --upgrade build && python3 -m build

- name: Publish
uses: pypa/gh-action-pypi-publish@release/v1
with:
# for testing uncommit the test repository url
#repository-url: https://test.pypi.org/legacy/
password: ${{ secrets.PYPI_API_TOKEN }}
verbose: true
7 changes: 7 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -46,6 +46,13 @@ For more information see the [official lakeFS documentation](https://docs.lakefs
- Testing of production data before exposing it to users / consumers.
- Testing of intermediate results in your DAG to avoid cascading quality issues.


## Publishing

The repository include GitHub workflow that is trigger on publish event and will build and push the package to PyPI.
**Note** that the package version is specified in the `setup.py` - make sure to update before publishing.


## Community

Stay up to date and get lakeFS support via:
Expand Down

0 comments on commit fbd2080

Please sign in to comment.