Skip to content

Replace existing release assets on retry#290

Merged
simonsmallchua merged 2 commits into
mainfrom
work/confident-cannon
Apr 3, 2026
Merged

Replace existing release assets on retry#290
simonsmallchua merged 2 commits into
mainfrom
work/confident-cannon

Conversation

@simonsmallchua
Copy link
Copy Markdown
Contributor

@simonsmallchua simonsmallchua commented Apr 3, 2026

Summary

  • Add replace_existing_artifacts: true to goreleaser config
  • When a release retrigger finds existing assets (from a prior partial run), goreleaser deletes and re-uploads them instead of failing with 422

Companion to #289 — completes the idempotent retry story.

Test plan

  • Merge, retag cli-v0.1.0, confirm goreleaser uploads assets and npm publish succeeds

Summary by CodeRabbit

  • Chores
    • Updated release configuration to replace existing artefacts during the release process.

@supabase
Copy link
Copy Markdown

supabase Bot commented Apr 3, 2026

Updates to Preview Branch (work/confident-cannon) ↗︎

Deployments Status Updated
Database Fri, 03 Apr 2026 12:49:44 UTC
Services Fri, 03 Apr 2026 12:49:44 UTC
APIs Fri, 03 Apr 2026 12:49:44 UTC

Tasks are run on every commit but only new migration files are pushed.
Close and reopen this PR if you want to apply changes from existing seed or migration files.

Tasks Status Updated
Configurations Fri, 03 Apr 2026 12:49:53 UTC
Migrations Fri, 03 Apr 2026 12:50:28 UTC
Seeding Fri, 03 Apr 2026 12:50:35 UTC
Edge Functions Fri, 03 Apr 2026 12:50:36 UTC

View logs for this Workflow Run ↗︎.
Learn more about Supabase for Git ↗︎.

@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Apr 3, 2026

Caution

Review failed

The pull request is closed.

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 92c6bc78-7684-45f8-b091-c5f89d4ee9fd

📥 Commits

Reviewing files that changed from the base of the PR and between 8091137 and 860787e.

📒 Files selected for processing (1)
  • .goreleaser.yml

📝 Walkthrough

Walkthrough

A configuration option has been added to .goreleaser.yml to enable automatic replacement of existing artifacts during release processes. The change modifies goreleaser's default behaviour when artifacts already exist.

Changes

Cohort / File(s) Summary
Release Configuration
.goreleaser.yml
Added release.replace_existing_artifacts: true to enable overwriting of existing artifacts during release operations, changing the default handling behaviour.

Comment @coderabbitai help to get the list of available commands and usage tips.

@github-actions
Copy link
Copy Markdown
Contributor

github-actions Bot commented Apr 3, 2026

🏷️ Release Preview

When this PR is merged, it will automatically create:

  • Version: vcli..1 (patch release)
  • Tag: vcli..1
  • GitHub Release: Pre-release with changelog content

The changelog will be updated and committed automatically.


💡 Tip: Update the changelog heading to control release type:

  • ## [Unreleased] or ## [Unreleased:patch] → patch release (default)
  • ## [Unreleased:minor] → minor release
  • ## [Unreleased:major] → major release

@simonsmallchua simonsmallchua merged commit dfdf7d5 into main Apr 3, 2026
7 of 8 checks passed
@simonsmallchua simonsmallchua deleted the work/confident-cannon branch April 3, 2026 12:50
@codecov
Copy link
Copy Markdown

codecov Bot commented Apr 3, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ All tests successful. No failed tests found.

📢 Thoughts on this report? Let us know!

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.

1 participant