v2.16.0

v2.9.2 should have been the last release for version 2, but considering the volatile timeline of v3, we have decided to continue supporting new enhancements for version 2.

As such, this release includes:

• fix: pass disable-dev-shm-usage arg to chrome #186

Docker Hub:

docker pull arachnysdocker/athenapdf:2.16.0
docker pull arachnysdocker/athenapdf-service:2.16.0

2.16.0 will not be pushed to 2 as it may introduce breaking changes. See the previous release for more information.

v2.15.0

v2.9.2 should have been the last release for version 2, but considering the volatile timeline of v3, we have decided to continue supporting new enhancements for version 2.

As such, this release includes:

• add --wait-for-status argument
• handle files without extension as HTML
• fix regression: did-get-response-details no longer functional in Electron 3

Docker Hub:

docker pull arachnysdocker/athenapdf:2.15.0
docker pull arachnysdocker/athenapdf-service:2.15.0

2.15.0 will not be pushed to 2 as it may introduce breaking changes. See the previous release for more information.

v2.14.0

v2.9.2 should have been the last release for version 2, but considering the volatile timeline of v3, we have decided to continue supporting new enhancements for version 2.

As such, this release includes:

• Modify /etc/hosts only if it is writeable to better support Kubernetes (56449b1)
• Upgrade Electron to v3.0.5 (Chrome 66)
• Fix to support converting files locally via the microservice with the latest Chrome

Docker Hub:

docker pull arachnysdocker/athenapdf:2.14.0
docker pull arachnysdocker/athenapdf-service:2.14.0

2.14.0 will not be pushed to 2 as it may introduce breaking changes. See the previous release for more information.

v2.13.0

v2.9.2 should have been the last release for version 2, but considering the volatile timeline of v3, we have decided to continue supporting new enhancements for version 2.

As such, this release includes:

• Graceful shutdown on SIGTERM
• Upgrade to go 1.10
• Dependencies are now versioned using go dep
• xvfb is now launched within weaver, and should it crash, it will take weaver with it
  • This is useful if you are using a container-orchestration system like Kubernetes as the container should be restarted automatically
  • Prior to this, athenapdf will not be functional if the display server crashes
  • Resolve #90
• Upgrade to Electron v2.0.4
• Timeout on CloudConvert based on the worker timeout
  • Prior to this, a conversion could continue running in background even after it times out in weaver

Docker Hub:

docker pull arachnysdocker/athenapdf:2.13.0
docker pull arachnysdocker/athenapdf-service:2.13.0

2.13.0 will not be pushed to 2 as it may introduce breaking changes. See the previous release for more information.

v2.12.0

This is an upgrade release. It will bring Athena up to Electron v2.0.1.

See https://github.com/electron/electron/releases for more information.

Docker Hub:

docker pull arachnysdocker/athenapdf:2.12.0
docker pull arachnysdocker/athenapdf-service:2.12.0

2.12.0 will not be pushed to 2 as it is a major Electron release (featuring an upgrade in the underlying Chromium engine) which may introduce breaking changes.

v2.10.0

This is an upgrade release. It will bring Athena up to Electron v1.7.5.

See https://github.com/electron/electron/releases for more information.

Docker Hub:

docker pull arachnysdocker/athenapdf:2
docker pull arachnysdocker/athenapdf:2.10.0

docker pull arachnysdocker/athenapdf-service:2
docker pull arachnysdocker/athenapdf-service:2.10.0

v2.9.2

This will be the last release for version 2.

Changes may still be pushed to version 2 if they are critical, security-related fixes. Regretfully, small bug fixes, and new features are unlikely to be welcomed or introduced. They will however, be taken into account for version 3.

We strongly recommend using our tagged releases. If you have not already done so, please take immediate action.

Example:

go get gopkg.in/arachnys/athenapdf.v2
docker pull arachnysdocker/athenapdf:2
docker pull arachnysdocker/athenapdf-service:2

If you do not do so, you are likely going to come across API breakages in the coming months.