You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
feat: add branch-based versioning for PR AMI builds (#1902)
* feat: add branch-based versioning for PR AMI builds
Manually create unique Postgres version names in branch often leads to
version conflicts with the base branch versions. These conflicts force
developers to deal with manual conflict resolution and unnecessary
rebuilds.
To address this, this change implement automatic branch-based versioning
for AMI builds triggered via workflow_dispatch on non-develop and
non-release branches. The branch name is sanitized and appended to the
Postgres version string.
Example: Branch 'multi-version-ext/pg-partman' produces postgres version
'multi-version-ext-pg-partman'
* feat: add notice message for published AMI version
Display the published postgres AMI version using GitHub Actions `::notice` annotation.
* feat: run actionlint on GitHub Actions workflows
Starting to lint GitHub Actions workflows with actionlint.
* fix: generate a unique AMI version
GitHub run_id is appended to the version suffix to ensure uniqueness.
It also enables to track the AMI back to the specific workflow run that
created it using url like: https://github.com/supabase/postgres/actions/runs/<run_id>
0 commit comments