1.0.13: Maintenance Release

Updates some dependencies flagged by dependabot and fixes a minor documentation typo.

(sorry this upload is late - CI usually automatically does this but seems to have skipped it)

1.0.12: Maintenance Release + GitHub Actions

Maintenance release: no functional changes, just upgraded any dependencies as recommended by dependabot and ensured jobson can be built using GitHub Actions

1.0.11: Fixed deadlock when child process reads from stdin

- Fixed a deadlock that can occur when the child process tries to read
  from the standard input

- The deadlock occurs because jobson provides no standard input to child
  processes, but keeps the standard input open. This causes child processes
  to deadlock indefinitely when 'read'ing from stdin

- This fix makes jobson 'close' the standard input of any child process
  at launch time. If any child process attempts to read from the standard
  input they'll read 0 bytes then stop

- See https://github.com/adamkewley/jobson/issues/67 for more info

- Thanks to @Russel88 for finding this bug!

1.0.10: Added (undocumented) support for 'file[]' input type

- Added new expectedInput type, 'file[]'

- Enables devs to specify that (API and UI) clients should supply a
  sequence of 0 or more files. The UI currently renders this as a
  <input type="file" multiple />

- Added a new template expression function, 'toDir'

  - Only accepts a 'file[]'-like input

  - Copies each file in file[] into a single directory in the working
    directory and returns a path to that directory

  - Enables user's scripts to receive all files in file[] as a path that
    their application can search through

- Using a file[] input in a template expression (e.g. '${inputs.someFileArray}'
  automatically coerces the file array such that each file in the array
  is copied into a single directory.

  - This is effectively sugar for '${toDir(inputs.someFileArray)}'

  - This, along with 'toDir' is one of the few ways to use the file[]
    input type at the moment.

- This feature is currently undocumented due to time constraints and
  missing/buggy features (job copying + defaults do not work with file[],
  for example)

1.0.9: Added (undocumented) support for 'file' input type

- Added a new expectedInput type, 'file'

- Enables devs to specify that (API and UI) clients should supply a file
  input for the job. The UI renders this as an <input type="file" />

- Using a file input in a template expression (e.g. '${inputs.someFile}')
  automatically coerces the user-supplied file into a local filepath that
  your application can read.

  - This is effectively sugar for '${toFile(inputs.foo)}', but with some
    extra quality-of-life benefits.

  - The main QOL benefit is that Jobson will try to leave the user-supplied
    filename untouched, which is useful if your application relies on
    extension matching

- This feature is currently undocumented due to time constraints. The final
  API of the released version *should* (famous last words) be identical.

1.0.8: Minor maintenance update

- Fixed broken link in docs

- Added a documentation section for proxying Apache2 to a jobson server

- Fixed *some* compiler + runtime warnings related to running jobson
  with a newer JDK (reflective access, etc.) and other compiler
  warnings about deprecations

  - Some runtime warnings still exist. These will be fixed when jobson's
    dependencies (namely, Dropwizard) are updated.

- Fixed travis configuration

1.0.7: Updated Dependencies

- Almost all dependencies updated to their latest version
- API documentation updated to latest swagger, which supports a later OpenAPI
- README updated

1.0.6: openjdk-11 compat and fix ui string[] input behavior

- Fixed issues preventing jobson from building on openjdk-11
- Updated dependencies project-wide, where appropriate
- UI string[] input now only splits on newlines (previously: newlines and commas)

1.0.5: Minor quality of life improvements

- UI footer now sticks to the bottom of the page, even if the page
  contains little content
- The demo script generated by --demo is now a little more interactive,
  to demonstrate the websocket features of the UI
- The resubmit button has been fixed and will now correctly refresh the
  page afterwards
- The "download request (debug)" button is now less prominent
- The documentation now contains an architecture diagram
- The README now contains up-to-date links

1.0.4: UI quality-of-life improvements

- Added a 'resubmit' button to the job details page
  - Will immediately submit a new job with exactly the same inputs
    as the job being resubmitted.
  - Effectively, this is the same as copy -> submit, but it's one less
    click and browser render
  - The main benefit of this feature is for UI inputs that cannot be
    copied easily (e.g. SQL inputs) or massive job requests that take
    the browser a long time to render
- Added an 'elapsed' time field into the job details page
  - Counts the total time elapsed between when the job was submitted
    and when it reached a terminal state (finished, cancelled, error)
- All timestamps in the job details page now dynamically update
- (devs): refactored UI code