############################ IMPORTANT  NOTES #############################
# If the new major version is the same as the previous one, you don't need
# to do anything besides updating the VER field in this file. However, if a
# major upgrade is available, you must do the following things:
#
# 1. Create a copy of postgresql-17 and name it `postgresql-$MAJOR', e.g.
#    `postgresql-18', and cd into that new directory.
# 2. Change the version number in spec to 18.X where X is the latest minor
#    version.
# 3. Go to release-monitoring.org and search for `PostgreSQL *' (note the
#    space.) You will find a project that corresponds to this major release
#    branch, for example `PostgreSQL 18.x'. Click on the project, go to the
#    address bar and copy the project ID in the link.
# 4. Replace the Anitya ID in the CHKUPDATE with the ID you just copied.
# 5. Modify the PKGNAME and PKGDES in autobuild/defines accordingly.
# 6. Run `abbs-update-checksum postgresql-18' to update the CHKSUMS.
# 7. Go back to postgresql package directory.
# 8. Run `aosc-findupdate'.
# 9. Edit autobuild/defines, change PKGDEP accordingly. DO NOT TOUCH ANY
#    OTHER FIELDS UNLESS NECESSARY!
# 10. Run a test build with your Ciel workspace.

VER=18.3
REL=1
DUMMYSRC=1
SUBDIR="."
# Do NOT edit this field as this points to the latest release.
CHKUPDATE="anitya::id=5601"
