Skip to content

Conversation

@jetbrains-junie
Copy link
Contributor

📌 Hey! This PR was made for you with Junie, the coding agent by JetBrains Early Access Preview

It's still learning, developing, and might make mistakes. Please make sure you review the changes before you accept them.
We'd love your feedback — join our Discord to share bugs, ideas: here.

📊 Junie Summary

Added a root-level GitHub Actions workflow to publish PyPI packages with safety checks. Workflow triggers on main branch pushes and requires manual file move and secret setup. Duplicate uploads are avoided.

 Added a root-level GitHub Actions workflow to publish PyPI packages with safety checks. Workflow triggers on main branch pushes and requires manual file move and secret setup. Duplicate uploads are avoided.
@Tryanks
Copy link
Owner

Tryanks commented Dec 3, 2025

@jetbrains-junie Please help me modify it to update PyPI automatically based on commit tags. This means that merely merging or pushing is not enough to trigger the current workflow; a tag must also be pushed. Only then will a new PyPI package be created based on the latest tag.

@jetbrains-junie
Copy link
Contributor Author

Hey, it’s Junie by JetBrains! I started processing your request 🚀

@jetbrains-junie
Copy link
Contributor Author

✅ The execution was successful

feat(ci): trigger PyPI publish only on tag pushes

The publishing workflow was updated to trigger only on Git tag pushes and moved to the standard GitHub Actions workflow directory. Safety checks ensure the workflow runs only on the canonical repository and tag refs. Instructions were provided for maintainers on token setup and release flow.

More information:

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

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Junie: Add a GitHub workflow to automatically publish new PyPI packages based on pushes and merges to the main branch.

2 participants