Skip to content

chore(rust-plugins): update farm crates #142

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
CCherry07 merged 1 commit into from
Sep 22, 2025
Merged

chore(rust-plugins): update farm crates #142

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
4 changes: 2 additions & 2 deletions .github/workflows/release-changeset.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -118,7 +118,7 @@ jobs:
id: changesets-rust-main
uses: changesets/action@v1
with:
publish: pnpm exec changeset publish --tag beta
publish: pnpm exec changeset publish
title: "Release: Rust Plugins (Beta)"
commit: "chore: release rust plugins (beta)"
Comment on lines +121 to 123
Copy link

@coderabbitai coderabbitai bot Sep 22, 2025

Choose a reason for hiding this comment

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

⚠️ Potential issue

Main branch now publishes Rust to npm “latest” but still labeled Beta — likely unintended.

Removing “--tag beta” means main publishes to the latest dist‑tag, while titles/commits still say Beta and JS still uses beta on main. This can push prerelease bits to “latest”.

Recommended fix (keep main as beta to match JS):

-          publish: pnpm exec changeset publish
-          title: "Release: Rust Plugins (Beta)"
-          commit: "chore: release rust plugins (beta)"
+          publish: pnpm exec changeset publish --tag beta
+          title: "Release: Rust Plugins (Beta)"
+          commit: "chore: release rust plugins (beta)"

Alternative (make main stable): also update job title/commit and align JS job in a follow‑up.

📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
publish: pnpm exec changeset publish
title: "Release: Rust Plugins (Beta)"
commit: "chore: release rust plugins (beta)"
publish: pnpm exec changeset publish --tag beta
title: "Release: Rust Plugins (Beta)"
commit: "chore: release rust plugins (beta)"
🤖 Prompt for AI Agents 
.github/workflows/release-changeset.yml lines 121-123: the publish step
currently runs "pnpm exec changeset publish" which will push packages to the
"latest" dist-tag while the job title/commit message and the JS pipeline still
treat main as Beta; restore explicit prerelease behavior by adding the "--tag
beta" flag to the publish command (e.g., pnpm exec changeset publish --tag beta)
so main continues to publish under the beta dist-tag, and update the job
title/commit message if needed to remain consistent (or, if you intend to make
main stable, instead change the title/commit and align the JS job to remove
beta).

env:
Expand All @@ -139,4 +139,4 @@ jobs:

call-rust-build:
if: contains(github.event.head_commit.message, 'rust-plugins') || contains(github.event.head_commit.message, 'all')
uses: ./.github/workflows/build.yaml
uses: ./.github/workflows/build.yaml
Loading
Loading