Skip to content
GitLab
Explore
Sign in
Primary navigation
Search or go to…
Project
helm-charts
Manage
Activity
Members
Code
Repository
Branches
Commits
Tags
Repository graph
Compare revisions
Deploy
Releases
Package Registry
Model registry
Operate
Terraform modules
Analyze
Model experiments
Help
Help
Support
GitLab documentation
Compare GitLab plans
Community forum
Contribute to GitLab
Provide feedback
Keyboard shortcuts
?
Snippets
Groups
Projects
Show more breadcrumbs
GitHub Mirror
groundhog2k
helm-charts
Commits
5876d4a5
Commit
5876d4a5
authored
3 weeks ago
by
Goeran Poehner
Browse files
Options
Downloads
Patches
Plain Diff
Updated postgres chart for Postgres 17.3
parent
668630b1
No related branches found
Branches containing commit
Tags
ghost-0.149.1
Tags containing commit
No related merge requests found
Changes
3
Hide whitespace changes
Inline
Side-by-side
Showing
3 changed files
charts/postgres/Chart.yaml
+2
-2
2 additions, 2 deletions
charts/postgres/Chart.yaml
charts/postgres/README.md
+1
-1
1 addition, 1 deletion
charts/postgres/README.md
charts/postgres/RELEASENOTES.md
+1
-0
1 addition, 0 deletions
charts/postgres/RELEASENOTES.md
with
4 additions
and
3 deletions
charts/postgres/Chart.yaml
+
2
−
2
View file @
5876d4a5
...
...
@@ -12,7 +12,7 @@ keywords:
-
database
-
postgres
version
:
"
1.
4.6
"
version
:
"
1.
5.2
"
appVersion
:
"
1
6.7
"
appVersion
:
"
1
7.3
"
icon
:
https://www.postgresql.org/media/img/about/press/elephant64.png
This diff is collapsed.
Click to expand it.
charts/postgres/README.md
+
1
−
1
View file @
5876d4a5
# PostgreSQL






## Changelog
...
...
This diff is collapsed.
Click to expand it.
charts/postgres/RELEASENOTES.md
+
1
−
0
View file @
5876d4a5
...
...
@@ -77,4 +77,5 @@
| 1.4.6 | 16.7 | Upgraded to Postgres 16.7 |
| 1.5.0 | 17.0 | Added Postgres 17.0 |
| 1.5.1 | 17.2 | Added Postgres 17.2 |
| 1.5.2 | 17.3 | Upgraded to Postgres 17.3 |
| | | |
This diff is collapsed.
Click to expand it.
Preview
0%
Loading
Try again
or
attach a new file
.
Cancel
You are about to add
0
people
to the discussion. Proceed with caution.
Finish editing this message first!
Save comment
Cancel
Please
register
or
sign in
to comment