Fixes #162 by testing against GraalVM
This commit is contained in:
parent
1f5e79b294
commit
e8759ceabf
2 changed files with 22 additions and 3 deletions
22
.github/workflows/test.yml
vendored
22
.github/workflows/test.yml
vendored
|
|
@ -17,6 +17,26 @@ jobs:
|
||||||
- name: Setup Clojure
|
- name: Setup Clojure
|
||||||
uses: DeLaGuardo/setup-clojure@master
|
uses: DeLaGuardo/setup-clojure@master
|
||||||
with:
|
with:
|
||||||
tools-deps: '1.10.3.814'
|
tools-deps: '1.10.3.822'
|
||||||
|
- name: Run Tests
|
||||||
|
run: clojure -M:test:runner
|
||||||
|
|
||||||
|
build-graalvm:
|
||||||
|
runs-on: ubuntu-latest
|
||||||
|
strategy:
|
||||||
|
matrix:
|
||||||
|
graalvm: [ '19.3.0', '20.0.0', '20.1.0', '20.2.0', '20.3.0', '20.3.1', '20.3.1.2', '21.0.0', '21.0.0.2' ]
|
||||||
|
base: [ 'java8', 'java11' ]
|
||||||
|
steps:
|
||||||
|
- uses: actions/checkout@v2
|
||||||
|
- name: Setup GraalVM
|
||||||
|
uses: DeLaGuardo/setup-graalvm@4.0
|
||||||
|
with:
|
||||||
|
graalvm: ${{ matrix.graalvm }}
|
||||||
|
java: ${{ matrix.base }}
|
||||||
|
- name: Setup Clojure
|
||||||
|
uses: DeLaGuardo/setup-clojure@master
|
||||||
|
with:
|
||||||
|
tools-deps: '1.10.3.822'
|
||||||
- name: Run Tests
|
- name: Run Tests
|
||||||
run: clojure -M:test:runner
|
run: clojure -M:test:runner
|
||||||
|
|
|
||||||
|
|
@ -4,10 +4,9 @@ Only accretive/fixative changes will be made from now on.
|
||||||
|
|
||||||
* 1.1.next in progress
|
* 1.1.next in progress
|
||||||
* Add **Tips & Tricks** section about working with PostgreSQL "interval" types (via PR #163 from @snorremd).
|
* Add **Tips & Tricks** section about working with PostgreSQL "interval" types (via PR #163 from @snorremd).
|
||||||
|
* Address #162 by adding GraalVM to the test matrix (thank you @DeLaGuardo).
|
||||||
* Update several dependency versions.
|
* Update several dependency versions.
|
||||||
|
|
||||||
## Stable Builds
|
|
||||||
|
|
||||||
* 1.1.646 -- 2021-03-15
|
* 1.1.646 -- 2021-03-15
|
||||||
* Fix #161 by allowing `execute-batch!` to work with datasources and connections, and providing the SQL statement directly.
|
* Fix #161 by allowing `execute-batch!` to work with datasources and connections, and providing the SQL statement directly.
|
||||||
|
|
||||||
|
|
|
||||||
Loading…
Reference in a new issue