Skip to content

Commit c747ccb

Browse files
committed
Update Python 3.13
1 parent 909df64 commit c747ccb

File tree

3 files changed

+27
-22
lines changed

3 files changed

+27
-22
lines changed

.github/workflows/testCode.yaml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -12,7 +12,7 @@ jobs:
1212
runs-on: windows-latest
1313
strategy:
1414
matrix:
15-
python-version: [3.11]
15+
python-version: [3.13]
1616
steps:
1717
- name: Checkout code
1818
uses: actions/checkout@v3

README.md

Lines changed: 25 additions & 20 deletions
Original file line numberDiff line numberDiff line change
@@ -1,54 +1,59 @@
1-
# Validate NVDA add-on metadata ##
1+
# Validate NVDA add-on metadata
22

33
This is a "GitHub Action" repository.
44
The Action aims to validate the metadata of add-ons submitted to
55
[NVDA's add-on store](https://github.com/nvaccess/addon-datastore).
66

7-
- Check that the added metadata:
8-
- Conforms with the
7+
* Check that the added metadata:
8+
* Conforms with the
99
[addonVersion_schema.json file](https://github.com/nvaccess/addon-datastore-validation/blob/main/_validate/addonVersion_schema.json).
10-
- File has the correct path and name: `addon1/majorVersion.minorVersion.patch.json`
11-
- Download URL is valid:
12-
- Must start with "https://" and end with".nvda-addon"
13-
- The `*.nvda-addon` file can be downloaded
14-
- The Sha256 of the downloaded `*.nvda-addon` file matches.
15-
- Check data matches the addon's manifest file.
16-
- The manifest exists in the downloaded `*.nvda-addon` file and can be loaded by the `AddonManifest` class.
17-
- The submission addonName matches the manifest summary field
18-
- The submission description matches the manifest description field
19-
- The homepage URL matches the manifest URL field
20-
- The addon versions match
21-
- The last tested & minimum required versions are valid NVDA API versions.
10+
* File has the correct path and name: `addon1/majorVersion.minorVersion.patch.json`
11+
* Download URL is valid:
12+
* Must start with "https://" and end with".nvda-addon"
13+
* The `*.nvda-addon` file can be downloaded
14+
* The Sha256 of the downloaded `*.nvda-addon` file matches.
15+
* Check data matches the addon's manifest file.
16+
* The manifest exists in the downloaded `*.nvda-addon` file and can be loaded by the `AddonManifest` class.
17+
* The submission addonName matches the manifest summary field
18+
* The submission description matches the manifest description field
19+
* The homepage URL matches the manifest URL field
20+
* The addon versions match
21+
* The last tested & minimum required versions are valid NVDA API versions.
2222

2323
If all is valid, "Congratulations: manifest, metadata and file path are valid" is printed.
2424

25-
## Dependencies ##
25+
## Dependencies
2626

2727
* [Python](https://www.python.org/).
28-
- Tested with: 3.11, 32 bit
28+
* Tested with: 3.13, 64 bit
29+
30+
## Local Usage
2931

30-
## Local Usage ##
3132
To try validating an addon submission on your own machine.
3233

3334
From cmd.exe:
3435

3536
1. Clone this repo: `git clone https://github.com/nvaccess/addon-datastore-validation.git`
3637
1. From the repo folder, run: `runvalidate <pathToAddonMetadataFile.json> <pathToFileWithAPIVersions.json>`
3738

38-
## Run unit tests:
39+
## Run unit tests
40+
3941
To test the scripts used in this action, you can run the unit tests.
4042

4143
1. Install [tox](https://pypi.org/project/tox): `pip install tox`
4244
1. `tox`
4345

44-
## Python linting:
46+
## Python linting
47+
4548
To keep a consistent style within the Python files of this Action, linting is used:
49+
4650
1. Use cmd.exe
4751
1. `cd` to the repo folder
4852
1. `runlint`
4953

5054
## Calculate a hash (sha256)
5155

5256
To get the sha256 of a file:
57+
5358
1. Use cmd.exe
5459
1. `runsha <path\to\filename>`

venvUtils/ensureAndActivate.ps1

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -2,7 +2,7 @@
22
# and then activates it.
33
# this script should be used only in the case where many commands will be executed within the environment and the shell will be eventually thrown away.
44
# E.g. an Appveyor build.
5-
py -3.11-32 "$PSScriptRoot\ensureVenv.py"
5+
py -3.13-64 "$PSScriptRoot\ensureVenv.py"
66
if ($LASTEXITCODE -eq 1) {exit 1}
77
. "$PSScriptRoot\..\.venv\scripts\activate.ps1"
88
Set-Variable NVDA_VENV $ENV:VIRTUAL_ENV

0 commit comments

Comments
 (0)