Skip to content

ci: set up soldeer autopublish for rain-pyth#24

Merged
thedavidmeister merged 1 commit into
mainfrom
2026-06-04-autopublish-soldeer
Jun 4, 2026
Merged

ci: set up soldeer autopublish for rain-pyth#24
thedavidmeister merged 1 commit into
mainfrom
2026-06-04-autopublish-soldeer

Conversation

@thedavidmeister
Copy link
Copy Markdown
Contributor

Towards #22 — publish rain.pyth to the soldeer registry.

Now that rain.pyth is de-submoduled (#23 merged), it can be published. This wires it up:

  • Add [package] (name = "rain-pyth", version = "0.1.0" — first release; no prior tags/registry entry) to foundry.toml.
  • Add package-release.yaml calling rainix-autopublish (soldeer-package: rain-pyth), which publishes rain-pyth~<version> on push to main when the foundry.toml version diverges from the registry.

⚠️ First-publish gate: the rain-pyth project must be created on soldeer.xyz before the first push succeeds — the registry rejects pushes to a nonexistent project, and the workflow does not create it. After this PR merges, the package-release job will attempt rain-pyth~0.1.0 and fail until the project exists; once created, re-run (or next push) publishes and #22 can close.

Now that rain.pyth is de-submoduled (#23) it can be published to soldeer.
Add [package] (name=rain-pyth, version=0.1.0 first release) + a
rainix-autopublish wrapper (soldeer-package: rain-pyth). Towards #22.

NB: the rain-pyth project must be created on soldeer.xyz before the first
push succeeds (the registry rejects pushes to a nonexistent project).
@coderabbitai
Copy link
Copy Markdown
Contributor

coderabbitai Bot commented Jun 4, 2026

Warning

Review limit reached

@thedavidmeister, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 13 minutes and 40 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 2a083d99-ca5a-4cc5-bb09-939f870faa53

📥 Commits

Reviewing files that changed from the base of the PR and between 97b3b4c and 71b8c35.

📒 Files selected for processing (2)
  • .github/workflows/package-release.yaml
  • foundry.toml
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch 2026-06-04-autopublish-soldeer

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@thedavidmeister
Copy link
Copy Markdown
Contributor Author

Reviewed 71b8c35: APPROVE — set up soldeer autopublish for rain-pyth ([package] rain-pyth@0.1.0 + rainix-autopublish wrapper, soldeer-package: rain-pyth). Towards #22. First publish gated on the rain-pyth project existing on soldeer.xyz.

@thedavidmeister thedavidmeister merged commit 7f590e0 into main Jun 4, 2026
5 checks passed
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