Skip to content

fix: allow release-plz to use crates.io registry #5

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.

Sign up for GitHub

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

Merged
f0rr0 merged 1 commit into from
Apr 26, 2026
Merged

fix: allow release-plz to use crates.io registry #5

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 0 additions & 1 deletion Cargo.toml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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/**",
Expand Down
3 changes: 3 additions & 0 deletions docs/RELEASE.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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

Expand Down