We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Current code from the main branch uses PostgreSQL JDBC driver 42.2.4
zally/server/zally-server/build.gradle.kts
Line 38 in e9e603a
Unfortunately, this version contains several known security vulnerabilities.
The latest relaased version of the driver seems to fix them: https://jdbc.postgresql.org/documentation/changelog.html#version_42.3.2
I have also found the following PostgreSQL Docker image tag discrepancy:
zally/docker-compose.yaml
Line 48 in e9e603a
zally/docker-compose-bark.yaml
Line 26 in e9e603a
Is it on purpose?
I have verified locally that Zally works after upgrading the JDBC driver and syncing Docker tags of the PostgreSQL Docker images used.
Can these changes be applied to the main branch and appear in the next release?
The text was updated successfully, but these errors were encountered:
Merge pull request #1361 from zalando/gh-1354-update-pg-and-cleanup-p…
ca763b0
…roject Update Postgres version and cleanup project
Successfully merging a pull request may close this issue.
Current code from the main branch uses PostgreSQL JDBC driver 42.2.4
zally/server/zally-server/build.gradle.kts
Line 38 in e9e603a
Unfortunately, this version contains several known security vulnerabilities.
The latest relaased version of the driver seems to fix them:
https://jdbc.postgresql.org/documentation/changelog.html#version_42.3.2
I have also found the following PostgreSQL Docker image tag discrepancy:
zally/docker-compose.yaml
Line 48 in e9e603a
vs
zally/docker-compose-bark.yaml
Line 26 in e9e603a
Is it on purpose?
I have verified locally that Zally works after upgrading the JDBC driver and syncing Docker tags of the PostgreSQL Docker images used.
Can these changes be applied to the main branch and appear in the next release?
The text was updated successfully, but these errors were encountered: