Version 1.7
All checks were successful
Build for Releases / ensure-release-exists (push) Successful in 1s
Build for Releases / push-build-x86_64 (push) Successful in 5s
Run Unit Tests / build-and-run-unit-tests (push) Successful in 2m10s
Build for Releases / push-build-aarch64 (push) Successful in 1m16s
Build for Releases / push-build-x86_64_debian (push) Successful in 35s
Build for Releases / push-build-aarch64_debian (push) Successful in 5m30s
All checks were successful
Build for Releases / ensure-release-exists (push) Successful in 1s
Build for Releases / push-build-x86_64 (push) Successful in 5s
Run Unit Tests / build-and-run-unit-tests (push) Successful in 2m10s
Build for Releases / push-build-aarch64 (push) Successful in 1m16s
Build for Releases / push-build-x86_64_debian (push) Successful in 35s
Build for Releases / push-build-aarch64_debian (push) Successful in 5m30s
This commit is contained in:
parent
b5b12171e1
commit
fca624550f
1 changed files with 5 additions and 0 deletions
|
@ -2,6 +2,11 @@
|
|||
|
||||
## Upcoming Changes
|
||||
|
||||
## Version 1.7
|
||||
|
||||
Fix usage of indexing in `IF`.
|
||||
Note this is used like `{{{!IF SomeVar[2]==true}}}`.
|
||||
|
||||
## Version 1.6
|
||||
|
||||
Fix usage of `IF` with a `FOREACH` variable when the `IF` is nested in the
|
||||
|
|
Loading…
Reference in a new issue