summaryrefslogtreecommitdiff
path: root/.github
Commit message (Collapse)AuthorAgeFilesLines
* Exclude bots from release notes.Julian Berman2023-03-251-0/+5
|
* Drop support for 3.7.Julian Berman2023-02-211-12/+0
| | | | | | | Referencing happens to not support it at the minute. It's close to EOL, so rather than adding it, I suspect it's droppable.
* tox.ini quoting seems to have changed too.Julian Berman2022-12-111-0/+3
|
* Run pip-audit only once, not for each OS.Julian Berman2022-12-111-6/+12
|
* Handle tox 4 (passenv doesn't take spaces now).Julian Berman2022-12-111-1/+1
|
* Replace codecov with coverage (7)'s native markdown support.Julian Berman2022-12-052-25/+9
|
* pypy3.8 -> 3.9Julian Berman2022-12-051-6/+6
|
* Run pip-licenses on the format-nongpl extra.Julian Berman2022-12-051-1/+5
|
* Replace safety with pip-audit.Julian Berman2022-12-051-2/+2
|
* Jammy changed the libenchant package name.Julian Berman2022-12-021-1/+1
|
* Skip the rest of the docs builds on Windows in CI.Julian Berman2022-11-221-0/+12
| | | | lxml doesn't have a 3.11 wheel currently.
* Run more things with 3.11 in CI.Julian Berman2022-11-221-19/+19
|
* Try enabling readthedocs/actions/preview for PR previews.Julian Berman2022-08-191-0/+16
|
* Follow pypa/gh-action-pypi-publish#83.Julian Berman2022-08-191-1/+1
|
* Specify a python-version for the pre-commit job.Julian Berman2022-08-171-1/+3
|
* Bump versions in the GH Actions workflow.Julian Berman2022-08-171-3/+3
|
* Re-enable more windows envs in CI.Julian Berman2022-08-061-48/+3
| | | | | | Enable UTF-8 mode to prevent cp1252 errors during test runs. See https://docs.python.org/3/using/windows.html#utf-8-mode
* Use the right Python version in the coverage workflow.Julian Berman2022-08-061-1/+1
|
* html -> dirhtml, and format_nongpl -> formatnongpl in toxJulian Berman2022-07-291-16/+16
|
* Combine the CI and packaging workflows.Julian Berman2022-05-302-43/+36
| | | | And only run the latter after the former.
* Re-enable Python 3.11 testing in CI.Julian Berman2022-05-282-17/+12
|
* Update various GHA versions.Julian Berman2022-05-284-13/+13
|
* Disable 3.11 CI until pypa/setuptools#3274 is fixed.Julian Berman2022-05-051-12/+13
|
* Skip annoying compiling Windows builds on 3.11 as well.Julian Berman2022-04-151-0/+12
|
* Move the skips for Windows to the right version (3.10)Julian Berman2022-01-121-12/+12
|
* Run 3.11 in CI.Julian Berman2022-01-121-0/+12
|
* pypy3.7 -> 3.8Julian Berman2022-01-121-12/+12
|
* Run more things with 3.10 in CI.Julian Berman2022-01-121-10/+10
|
* Setup mypy in `tox -e typing` and get it to passStephen Rosen2022-01-051-0/+2
| | | | | | | | | | | | | | | | | | | | | | This is the smallest possible change to get mypy passing on the jsonschema codebase. The goal of this configuration is to enforce type annotations anywhere that they appear. That is, if a method is added to the codebase, def foo(x: int) -> str: return str(x) then usages of `foo` will by type checked. If no annotations are added, `mypy` will not type check functions. For the most part, this keeps the impact low. The one exceptional case is the use of `pyrsistent.pmap` as an argument to `attr.ib(converter=...)`. Unfortunately, it causes `mypy` to incorrectly deduce the type of the init parameter created by attrs. We need to "explain the type of init" to mypy by creating a callable with a concrete type to act as the converter. The callable in question simply wraps `pmap` with a cast and presents the desired type information to mypy.
* Remove the Patreon link.Julian Berman2021-10-191-1/+0
|
* Sigh, back to full clones.Julian Berman2021-10-081-0/+2
|
* Try autocreating release notes.Julian Berman2021-10-081-8/+14
| | | | | | | | See https://docs.github.com/en/repositories/releasing-projects-on-github/automatically-generated-release-notes and https://github.blog/2021-10-04-beta-github-releases-improving-release-experience/
* Skip tests on 3.10 + Windows which fail for annoying compilation reasons.Julian Berman2021-10-081-0/+12
|
* Add support for Python 3.10.Julian Berman2021-10-082-1/+13
|
* Combine the CI and precommit workflows.Julian Berman2021-10-082-13/+7
|
* Re-allow the fuzz to fail.Julian Berman2021-10-031-0/+1
| | | | | | | It seems to have stopped running, even though I don't believe anything related to it has changed, but it'll require some diagnosis that I don't have time for at the minute to figure out what precisely.
* Minor tweak to the OSSFuzz workflow.Julian Berman2021-08-252-4/+2
|
* Minor restructure of which html sphinx builder we build in the tox.ini.v4.0.0a4Julian Berman2021-08-241-1/+1
|
* Drop support for Python 3.6.deprecationsJulian Berman2021-08-201-12/+0
| | | | | | | | | It's in security fix only mode (till EOY) and doesn't support module-level __getattr__ yet, which presents enough of a minor nuisance to drop it. Users should stick to older jsonschema versions (which should be properly marked.)
* Use python 3.9 for coverageHarald Nezbeda2021-07-121-2/+2
|
* Add language, remove dry-run: false which is the default.Julian Berman2021-03-021-3/+8
| | | | Run only against main for now, save some time on PRs.
* Move the fuzz workflow to fuzz.yml.Julian Berman2021-03-021-0/+0
|
* Merge branch 'main' into DavidKorczynski/mainJulian Berman2021-03-021-91/+24
|\ | | | | | | | | | | | | | | | | | | | | * main: Reskip the PyPy-on-Windows tests. Try the Twisted prerelease, which hopefully obviates installing IOCP. No, don't use venv. Fix test to windows path matching Test via PyPy3.7 Unskip most of the skipped windows builds. Update pre-commit.
| * Reskip the PyPy-on-Windows tests.windowsJulian Berman2021-02-221-0/+24
| | | | | | | | | | | | | | They seem to produce a fun variety of errors that I can't diagnose at the minute See e.g. https://github.com/Julian/jsonschema/runs/1956639377?check_suite_focus=true
| * No, don't use venv.Julian Berman2021-02-221-3/+0
| |
| * Test via PyPy3.7Julian Berman2021-02-201-6/+6
| |
| * Unskip most of the skipped windows builds.Julian Berman2021-02-201-88/+0
| |
* | switch to checking steps output.davkor2021-01-211-1/+1
| |
* | Try adding an success statement in CIdavkor2021-01-211-0/+1
| |
* | Move continue-on-error to build step.davkor2021-01-211-1/+1
| |