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

chore: re-bump postgres-version since it's used by an existing AMI #823

Merged
merged 1 commit into from
Dec 7, 2023

Conversation

thebengeu
Copy link
Member

https://github.com/supabase/postgres/actions/runs/7117692724/job/19379008532: "Error: AMI Name: 'supabase-postgres-15.1.0.139' is used by an existing AMI". The existing AMI was released manually in https://github.com/supabase/postgres/actions/runs/7111334625.

@thebengeu thebengeu requested a review from a team as a code owner December 6, 2023 18:33
thebengeu added a commit that referenced this pull request Dec 7, 2023
thebengeu added a commit that referenced this pull request Dec 7, 2023
…AMI builds

To avoid situations such as #823. This also disallows simply appending .e.g ".1", which is against https://semver.org/ for pre-release versions, and it's good to have more descriptive identifiers.
darora pushed a commit that referenced this pull request Dec 7, 2023
…AMI builds

To avoid situations such as #823. This also disallows simply appending .e.g ".1", which is against https://semver.org/ for pre-release versions, and it's good to have more descriptive identifiers.
@thebengeu thebengeu requested a review from darora December 7, 2023 02:33
@darora darora merged commit bfed6c4 into develop Dec 7, 2023
8 checks passed
@darora darora deleted the beng/re-bump branch December 7, 2023 02:41
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.

2 participants