Skip to content

github-workflows: astral-sh/setup-uv from v6 to v7#19219

Merged
seanbudd merged 1 commit into
nvaccess:masterfrom
dpy013:githubUpdate-workflows
Nov 17, 2025
Merged

github-workflows: astral-sh/setup-uv from v6 to v7#19219
seanbudd merged 1 commit into
nvaccess:masterfrom
dpy013:githubUpdate-workflows

Conversation

@dpy013

@dpy013 dpy013 commented Nov 16, 2025

Copy link
Copy Markdown
Contributor

Link to issue number:

none

Summary of the issue:

Update astral-sh/setup-uv from v6 to v7 to conveniently use the latest security fixes.
Below is the release page for v7.1.3.

Description of user facing changes:

Routine update of CI/CD with no impact on users.

Description of developer facing changes:

Batch replaced uses: astral-sh/setup-uv@v6 with v7 in .github/workflows/testAndPublish.yml.

Description of development approach:

Batch replaced uses: astral-sh/setup-uv@v6 with v7 in .github/workflows/testAndPublish.yml to use the latest stable version.

Testing strategy:

Tests have been conducted using the forked repository, and all CI/CD checks have passed. Below is the link to view the test details:
https://github.com/dpy013/nvda/actions/runs/19405173517

Known issues with pull request:

none

Code Review Checklist:

  • Documentation:
    • Change log entry
    • User Documentation
    • Developer / Technical Documentation
    • Context sensitive help for GUI changes
  • Testing:
    • Unit tests
    • System (end to end) tests
    • Manual testing
  • UX of all users considered:
    • Speech
    • Braille
    • Low Vision
    • Different web browsers
    • Localization in other languages / culture than English
  • API is compatible with existing add-ons.
  • Security precautions taken.

@dpy013 dpy013 requested a review from a team as a code owner November 16, 2025 12:53
@dpy013 dpy013 requested a review from seanbudd November 16, 2025 12:53
@amirmahdifard

Copy link
Copy Markdown

@SaschaCowley @seanbudd I have a question, sorry about asking it hear. It's a quick question. We no longer have built nvda in artifaqts of pull requests? it was very usefull. Imagin someone opened a pull request doing something, And I wanted to test it. Before when nvda was using appvayer, I could download the built nvda out of that pull request, but Now that i'm checking the artifaqts of checks github actions, I don't see the actual nvda being there, I just saw the documentation and a nvda launcher etc. If this is no longer a case, can you please readd it? I really needed that and it was useful

@seanbudd

Copy link
Copy Markdown
Member

Hi @amirmahdifard - the NVDA launcher is the artifact you'd use to test NVDA

@seanbudd seanbudd left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @dpy013

@seanbudd seanbudd merged commit d05da56 into nvaccess:master Nov 17, 2025
41 checks passed
@github-actions github-actions Bot added this to the 2026.1 milestone Nov 17, 2025
@dpy013 dpy013 deleted the githubUpdate-workflows branch November 17, 2025 00:59
seanbudd pushed a commit that referenced this pull request Nov 18, 2025
…tup-python@v6 (#19229)

Follow up
#19219

#19224
Summary of the issue:

Updated actions/setup-python@v5 to actions/setup-python@v6
Description of user facing changes:

none ci-cd Update
Description of developer facing changes:

Updated the version of actions/setup-python in testAndPublish.yml to 6.x
Description of development approach:

Updated the version of actions/setup-python in testAndPublish.yml to 6.x
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.

3 participants