Skip to content

fix(release): disable crates.io publishing#182

Merged
zeitlinger merged 1 commit intomainfrom
fix/no-crates-publish
Apr 16, 2026
Merged

fix(release): disable crates.io publishing#182
zeitlinger merged 1 commit intomainfrom
fix/no-crates-publish

Conversation

@zeitlinger
Copy link
Copy Markdown
Member

Summary

  • release-plz tries to publish to crates.io by default
  • Fails with "no token found" on every push to main (run)
  • Flint distributes via GitHub releases only — add publish = false

Flint distributes via GitHub releases, not crates.io.
Without this, release-plz tries to publish and fails with
"no token found, please run `cargo login`" on every push to main.
Signed-off-by: Gregor Zeitlinger <gregor.zeitlinger@grafana.com>
@zeitlinger zeitlinger marked this pull request as ready for review April 16, 2026 16:57
@zeitlinger zeitlinger requested a review from a team as a code owner April 16, 2026 16:57
Copilot AI review requested due to automatic review settings April 16, 2026 16:57
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Disables crates.io publishing in the release-plz configuration so pushes to main don’t fail due to missing crates.io credentials, aligning releases with this repo’s GitHub-release-only distribution approach.

Changes:

  • Add publish = false to release-plz.toml workspace configuration to prevent crates.io publish attempts.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

@zeitlinger zeitlinger merged commit 5af56d4 into main Apr 16, 2026
18 checks passed
@zeitlinger zeitlinger deleted the fix/no-crates-publish branch April 16, 2026 17:20
@github-actions github-actions Bot mentioned this pull request Apr 16, 2026
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.

3 participants