From 67fc8114e4942f6fcd6becd5231de1d729a928e8 Mon Sep 17 00:00:00 2001
From: Sid Jain <sid_26@outlook.com>
Date: Sun, 26 Apr 2026 14:14:22 +0530
Subject: [PATCH] fix: allow release-plz to use crates.io registry

---
 Cargo.toml      | 1 -
 docs/RELEASE.md | 3 +++
 2 files changed, 3 insertions(+), 1 deletion(-)

diff --git a/Cargo.toml b/Cargo.toml
index 17a5973e..04da8db6 100644
--- a/Cargo.toml
+++ b/Cargo.toml
@@ -11,7 +11,6 @@ documentation = "https://docs.rs/pglite-oxide"
 keywords = ["postgres", "pglite", "wasm", "database", "embedded"]
 categories = ["database-implementations", "wasm", "development-tools::testing"]
 license = "MIT AND Apache-2.0 AND PostgreSQL"
-publish = ["crates-io"]
 exclude = [
   ".config/**",
   ".github/**",
diff --git a/docs/RELEASE.md b/docs/RELEASE.md
index 46e887f5..b125ca00 100644
--- a/docs/RELEASE.md
+++ b/docs/RELEASE.md
@@ -15,6 +15,9 @@ user-facing binary to distribute.
 - Repository Actions settings must allow GitHub Actions to create pull requests.
 - The `Release` workflow needs `contents: write`, `pull-requests: write`, and
   `id-token: write`; these are already declared in the workflow.
+- Do not set `package.publish = ["crates-io"]`; crates.io is Cargo's default
+  registry, and release-plz treats `package.publish` entries as named alternate
+  registries.
 
 ## Release intent