cicd: publish 조건 수정

[yesinkim]

No description provided.

[cr-gpt]

Code Review:

1. Changes to Trigger Action:

   • Changed the trigger from push with a tag match to a release trigger that only runs on "created" releases. This change is reasonable if you want to publish to PyPI only when a new release is created, not on every push (which could potentially become noisy).

2. Risk and Improvement Suggestions:

   • Security Risk: Consider implementing safeguards to prevent accidental or unauthorized releases.
   • Workflow Understanding: Ensure this action does not cause unintended publishing or errors due to misconfigured or untested releases.
   • Versioning: Be explicit about version numbers being released to prevent unintentional overwritten existing versions on PyPI.
   • Testing: It's helpful to thoroughly test the workflow to ensure it handles different scenarios well.

3. Future Improvements:

   • Include Tests: Add tests to automate validation of the release process in your workflows.
   • Error Handling: Implement error handling mechanisms to catch and report any issues during the release process.
   • Notification System: Consider setting up notifications for successful or failed releases.
   • Documentation: Document the workflow thoroughly so others can understand and maintain it easily.

Overall Assessment:

The code patch seems to provide a solid basis for publishing Python distributions to PyPI upon the creation of a release. However, to enhance robustness, consider addressing the identified risks and implementing suggested improvements.