Skip to content
New issue

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

RE-2169: chore: bump postgres client from 15 to 16 #11936

Merged
merged 7 commits into from
Apr 18, 2024

Conversation

erikburt
Copy link
Collaborator

@erikburt erikburt commented Feb 5, 2024

Updating postgres client from 15 -> 16.

Copied changes from dc6bd0c, however there exist more places which reference postgres now. For example:

  • && apt-get update && apt-get install -y postgresql-client-14 \
    • This wasn't included in this PR because it doesn't reference 15 like the rest. It seems like it was either accidentally missed or purposefully excluded during the last bump

@erikburt erikburt requested a review from a team February 5, 2024 20:05
@erikburt erikburt self-assigned this Feb 5, 2024
Copy link
Contributor

github-actions bot commented Feb 5, 2024

I see that you haven't updated any CHANGELOG files. Would it make sense to do so?

jmank88
jmank88 previously approved these changes Feb 6, 2024
@jmank88
Copy link
Contributor

jmank88 commented Feb 6, 2024

You can update plugins/chainlink.Dockerfile too - it was just overlooked. I probably created the PR before the others were bumped and missed it in a rebase.

jmank88
jmank88 previously approved these changes Feb 6, 2024
@cl-sonarqube-production
Copy link

cl-sonarqube-production bot commented Feb 6, 2024

Quality Gate passed Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

@snehaagni snehaagni changed the title chore: bump postgres client from 15 to 16 RE-2169: chore: bump postgres client from 15 to 16 Feb 7, 2024
jmank88
jmank88 previously approved these changes Apr 16, 2024
@erikburt erikburt requested a review from chudilka1 April 17, 2024 17:05
chudilka1
chudilka1 previously approved these changes Apr 18, 2024
@erikburt erikburt dismissed stale reviews from chudilka1 and jmank88 via e7ba665 April 18, 2024 17:57
Copy link
Contributor

I see you added a changeset file but it does not contain a tag. Please edit the text include at least one of the following tags:

  • #added For any new functionality added.
  • #breaking_change For any functionality that requires manual action for the node to boot.
  • #bugfix For bug fixes.
  • #changed For any change to the existing functionality.
  • #db_update For any feature that introduces updates to database schema.
  • #deprecation_notice For any upcoming deprecation functionality.
  • #internal For changesets that need to be excluded from the final changelog.
  • #nops For any feature that is NOP facing and needs to be in the official Release Notes for the release.
  • #removed For any functionality/config that is removed.
  • #updated For any functionality that is updated.
  • #wip For any change that is not ready yet and external communication about it should be held off till it is feature complete.

@erikburt erikburt enabled auto-merge April 18, 2024 18:09
@cl-sonarqube-production
Copy link

Quality Gate failed Quality Gate failed

Failed conditions
3 Security Hotspots

See analysis details on SonarQube

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants