Open duttonw opened 1 week ago
Yes, sure. I'm using conventional commit messages and compile them into CHANGELOG.md using git-changelog. That's why my standard release workflow looks like:
setup.cfg
or whatever place keeps the versiongit changelog -c conventional -o CHANGELOG.md -B <NEW.VERSION.NUMBER>
chore: update changelog/bump version
message.python -m build
twine upload dist/*
. I'm using ~/.pypirc
config so credentials are not specified in CLIdist
folderHi @smotornyuk ,
Thanks for the bootstrap on deployment.
You can have a look at a crude auto deployment using github provide oidc auth.
https://github.com/ckan/ckanext-xloader/blob/master/.github/workflows/publish.yml#L96
pypi config you can see here: https://github.com/ckan/ckanext-xloader/issues/214#issuecomment-2415189905 and GitHub environment setup (so you can restrict who can deploy) https://github.com/ckan/ckanext-xloader/issues/214#issuecomment-2415384199
I'm still working on major improvements and it does require a 'Service Account bot' for proper 'bump' commit deployments via github actions.
Hi @smotornyuk
I'm one of my maintainers of data.qld.gov.au publications.qld.gov.au ckan instances. Which is deployed by https://github.com/qld-gov-au/ckan-qld-infrastructure/ .
I'm wondering if you can provide commands you run to deploy this plugin repo to pypi as you have been keeping it quite up to date in last last couple of years.
The reason i'm asking is that I'm looking for a general standardized approach that people use on packaging and deployed to pypi.
If you can you provide your steps (without creds etc) that you follow it would be great since with that I may be able to contribute a fully automated github action workflow for you based on it.
Also just a heads up, my area will be contributing features into your product to handle logout correctly for SSO users. You can get a sneak peak at https://github.com/DataShades/ckanext-oidc-pkce/compare/master...qld-gov-au:ckanext-oidc-pkce:develop
Regards,
@duttonw