Create Publish Package to TestPyPi

[Qoyyuum]

This will help test the python distribution to TestPyPi for each new push to stable and pull request to master, and easily test the end product afterwards.

Background

There's no easy way to test new master pull requested packages. With this new workflow, we can see the latest changes and pull request to master, uploaded to TestPyPi and test the new package (as long as the version number in pyproject.toml file is incremented properly).

Changes

Created a new file, pypi-publish.yml as a new pipeline.
A couple of lines in pyproject.toml file to have a working python -m build

Documentation

Repo owner needs to set a new Repository secret called, TEST_PYPI_API_TOKEN. Get the API Token from https://test.pypi.org/
For each new change and about to release a new version, update the pyproject.toml file with a new version and set it up as a new pull request. This will trigger the workflow and upload it to testpypi.

Test the package by pip install -i https://test.pypi.org/simple/ auto-gpt==<new version number>

Test Plan

Tested by running the workflow myself and uploaded to my test account's project. (Now removed)

PR Quality Checklist

• My pull request is atomic and focuses on a single change.
• I have thoroughly tested my changes with multiple different prompts.
• I have considered potential risks and mitigations for my changes.
• I have documented my changes clearly and comprehensively.
• I have not snuck in any "extra" small tweaks changes

[p-i-]

This is a mass message from the AutoGPT core team.
Our apologies for the ongoing delay in processing PRs.
This is because we are re-architecting the AutoGPT core!

For more details (and for infor on joining our Discord), please refer to:
https://github.com/Significant-Gravitas/Auto-GPT/wiki/Architecting

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Comments	Updated (UTC)
docs	✅ Ready (Inspect)	Visit Preview	💬 Add feedback	Jun 11, 2023 6:08am

[Qoyyuum]

Hi @BillSchumacher since the production pypi is already up that I can see, would it make sense for this PR to help automate the release or no?

[codecov]

Codecov Report

Patch and project coverage have no change.

Comparison is base (0594ba3) 69.20% compared to head (797b056) 69.20%.

Additional details and impacted files

@@           Coverage Diff           @@
##           master    #2506   +/-   ##
=======================================
  Coverage   69.20%   69.20%           
=======================================
  Files          72       72           
  Lines        3579     3579           
  Branches      569      569           
=======================================
  Hits         2477     2477           
  Misses        920      920           
  Partials      182      182           

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[Pwuts]

@Qoyyuum that package doesn't seem to be maintained actively, and using Auto-GPT as a package from pypi isn't documented anywhere. Do you think we should add this as a supported way to use Auto-GPT, or rather take down the package?

[vercel]

Deployment failed with the following error:

Resource is limited - try again in 2 hours (more than 100, code: "api-deployments-free-per-day").

[Auto-GPT-Bot]

You changed AutoGPT's behaviour. The cassettes have been updated and will be merged to the submodule when this Pull Request gets merged.

[Qoyyuum]

Hi @Pwuts yeah its a little out of date but that's where I was hoping this PR could help test the package in TestPypi repo before releasing to Prod Pypi. Also, hoping to use the same package as where @BillSchumacher uploaded. But baby steps is to try this out to testpypi first.

And then I could raise a separate PR to also publish to Prod Pypi, including documentation, so that everyone can just have the latest and greatest release feature (as opposed to git pulling from stable branch) via a simple pip install agpt --upgrade.

What do you think?

[github-actions]

This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request.

[ntindle]

@Qoyyuum have you taken a look at #4604 ?

[Pwuts]

@lc0rp @collijk fyi