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

FEAT: Support to set the Project Version using uv command #7750

Closed
datnguye opened this issue Sep 28, 2024 · 1 comment
Closed

FEAT: Support to set the Project Version using uv command #7750

datnguye opened this issue Sep 28, 2024 · 1 comment
Labels
duplicate This issue or pull request already exists

Comments

@datnguye
Copy link

Currently I'm using poetry and would like move into uv world. One of the migration point is to be able to set the project version in pyproject.toml using uv command.

[project]
name = "package"
version = "0.0.0" # will be always like this in pyproject.toml & need updating on release

Similarly using poetry: poetry version 1.0.0 -- This feature will help to simplify the Pypi Publishing workflow.

In my case, here is the sample Github Workflow step:

    - name: Build and publish
      run: |
        poetry version $(git describe --tags --abbrev=0)
        poetry build
        poetry publish --username ${{ secrets.PYPI_USERNAME }} --password ${{ secrets.PYPI_PASSWORD }}

My expectation is that something I can do the same for uv:

    - name: Build and publish
      run: |
        uv version $(git describe --tags --abbrev=0)
        uv build
        uv publish --username ${{ secrets.PYPI_USERNAME }} --password ${{ secrets.PYPI_PASSWORD }}

OR:

    - name: Build and publish
      run: |
        uv build --version $(git describe --tags --abbrev=0)
        uv publish --username ${{ secrets.PYPI_USERNAME }} --password ${{ secrets.PYPI_PASSWORD }}
@zanieb
Copy link
Member

zanieb commented Sep 28, 2024

Thanks for the issue. This is a duplicate of #6298

@zanieb zanieb added the duplicate This issue or pull request already exists label Sep 28, 2024
@zanieb zanieb closed this as not planned Won't fix, can't repro, duplicate, stale Sep 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists
Projects
None yet
Development

No branches or pull requests

2 participants