Release v0.1.0

[noklam]

Description

Context

Possible Implementation

Possible Alternatives

[noklam]

@Galileo-Galilei I am not familiar with the release workflow, I saw there is a prepare-release workflow and seems like it bump version automatically. How does the release process work?

[Galileo-Galilei]

The release workflow works in 2-steps:

• the create-release-candidate worklow which bumps the changelog and the version and opens a PR to enable manuel fixes at this step (eg. if the release notes are not up to date)

• Once the PR is merged, the publish worklow creates a github release and deploy the main branch to PyPI

[Galileo-Galilei]

I'll do it tonight, for some unknown reason I cant trigger the workflow through the Android app.

[noklam]

@Galileo-Galilei I fixed a bug in the Github action but run into permission error. Maybe it has to be you running the workflow. https://github.com/Galileo-Galilei/kedro-pandera/actions/runs/6052281404/job/16425421416

[Galileo-Galilei]

I'll check this. I may have not enable / configured my PyPI and github tokens for this repo when I created it at first. I'll wait you to merge #32 before I trigger the release.

Do you think that it is appropriate to make an announcement on the kedro slack to attract users or is this considered as too aggressive self promotion and reserved to the team for "official" products?

[noklam]

I think it's fine to do it on #plugin-integration channels, but probably better to announce by you to avoid people thinking this is from the official Kedro team.

[Galileo-Galilei]

Done!

I close the issue but we may need to refactor the github action & advertise on the slack channel.