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

Version v1.0.1 #203

Merged
merged 24 commits into from
Jul 29, 2024
Merged

Version v1.0.1 #203

merged 24 commits into from
Jul 29, 2024

Conversation

sibocw
Copy link
Contributor

@sibocw sibocw commented Jul 3, 2024

Description

This is the main PR for v1.0.1-pre.1 v1.0.1

Does this address any currently open issues?

(These are not issues but PRs, but) #204, #205, #206, #209

Issue #207

@sibocw sibocw changed the title Version 1.0.1-pre.1 Version 1.0.1~~-pre.1~~ Jul 27, 2024
@sibocw sibocw changed the title Version 1.0.1~~-pre.1~~ Version 1.0.1 Jul 27, 2024
@sibocw sibocw changed the title Version 1.0.1 Version ~~v1.0.1-pre.1~~ v1.0.1 Jul 27, 2024
@sibocw sibocw changed the title Version ~~v1.0.1-pre.1~~ v1.0.1 Version v1.0.1 Jul 27, 2024
@sibocw
Copy link
Contributor Author

sibocw commented Jul 27, 2024

Releasing this directly as 1.0.1; 1.0.1-pre.1 not needed.

Release checklist

  • Merge staging branch* into main
    • On the staging branch, UPDATE version in setup.py. It should follow the formats v1.2.3, v1.2.3-pre.4, or v1.2.3-post.4 depending on if it is a stable, pre-, or post-release. See Semantic Versioning.
    • On the staging branch, UPDATE doc/source/changelog.rst
    • IF README.md or website homepage needs to be updated, UPDATE them**
    • CREATE PR to merge staging branch into main
    • VERIFY that the CI workflows for the PR have all finished and are passing
    • VERIFY that someone else has reviewed the PR
    • MERGE PR
  • Make release on GitHub
    • CREATE a draft release
    • SET version number to the version number in setup.py
    • ADD content from changelog.rst to the release description, MODIFY as needed
    • Use the "Generate release notes" button to automatically CREATE a list of merged PRs since the last release
    • CHECK the "Set as a pre-release" and "Set as the latest release" checkboxes.
    • PUBLISH release
  • Push package to PyPI
    • CHECKOUT to the main branch: git checkout main
    • PULL the latest updates; VERIFY if the newly merged contents are pulled: git pull origin main
    • VERIFY that you are at the flygym root level
    • REMOVE existing artifacts: rm -rf build dist flygym.egg-info
    • VERIFY that you are on the correct virtual environment
    • CREATE the wheels: python setup.py sdist bdist_wheel
    • VERIFY that ~/.pypirc contains a [flygym] entry with password set to a PyPI API key.
    • PUSH the package: python -m twine upload --repository flygym --verbose dist/*
    • IF authentication fails, check API key on pypi.org, and possibly REGENERATE one. UPDATE ~/.pypirc accordingly. Then, REPEAT the step above (PUSH the package).
  • Push Docker image Docker Hub
    • (If not done already) AUTHENTICATE to Docker Hub: docker login
    • BUILD the image and tag it both as the latest version (default) and explicitly using the version number: docker build -t nelyepfl/flygym -t nelyepfl/flygym:vx.x.x . (replace version number)
    • PUSH to Docker Hub: docker push nelyepfl/flygym, then docker push nelyepfl/flygym:vx.x.x (replace version number)
  • Cleaning up
    • REMOVE merged and deprecated branches

@sibocw sibocw requested a review from tkclam July 27, 2024 19:45
@sibocw sibocw marked this pull request as ready for review July 27, 2024 19:54
tkclam
tkclam previously approved these changes Jul 29, 2024
@sibocw sibocw merged commit f0b14f1 into main Jul 29, 2024
15 checks passed
@sibocw sibocw deleted the dev-v1.0.1-pre.1 branch July 29, 2024 12:23
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

Successfully merging this pull request may close these issues.

2 participants