Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Release check-list #370

Open
Nour-Mws opened this issue Sep 18, 2023 · 0 comments
Open

Release check-list #370

Nour-Mws opened this issue Sep 18, 2023 · 0 comments

Comments

@Nour-Mws
Copy link
Collaborator

Nour-Mws commented Sep 18, 2023

To do only once:

  • create a PyPI account if you don't already have one
  • create an API token on PyPI
  • add it with poetry config pypi-token.pypi <token>

To do for each release:

  • bump version in pyproject.toml (and the pre-commit example at the bottom of README.md) and create a PR
  • check that the CI is not failing on main after merging the PR
  • create a tag with git tag -a <tag name> on the last commit of main. Example: git tag -a v0.1.0 (note the v in the name).
  • push github tag: git push origin <tag-name> or git push --tags
  • create the release on the Github repository (use the tag name you created and use the auto-generated release notes as a draft).
  • poetry build
  • poetry publish (you need to be a maintainer of the PyPI project)
  • Publish release announcement on:
    • #ext-falwtydeps on Slack
    • #collab-dev on Slack
    • #fawltydeps on the Tweag Discord
    • Consider if the release is worth announcing more widely:
      • Tweag socials?
      • #collab-marketing on Slack?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant