Skip to content

feat(library-solidity): add Soldeer publishing to library-solidity CI#2123

Open
poppyseedDev wants to merge 3 commits intomainfrom
poppyseed/publish-soldeer
Open

feat(library-solidity): add Soldeer publishing to library-solidity CI#2123
poppyseedDev wants to merge 3 commits intomainfrom
poppyseed/publish-soldeer

Conversation

@poppyseedDev
Copy link
Contributor

@poppyseedDev poppyseedDev commented Mar 17, 2026

Summary

  • Add publish-soldeer job to library-solidity-publish workflow, publishing @fhevm-solidity to soldeer.xyz on release (parallel with npm publish)
  • Add .soldeerignore in library-solidity/ to ship only Solidity sources (lib/, config/, README, SECURITY)

Prerequisites before going live

  • Create @fhevm-solidity project on soldeer.xyz (public, under zama-bot account)
  • Ensure SOLDEER_TOKEN secret is set on this repo

@poppyseedDev poppyseedDev requested review from a team as code owners March 17, 2026 14:21
@cla-bot cla-bot bot added the cla-signed label Mar 17, 2026
@poppyseedDev poppyseedDev changed the title feat(contracts): add Soldeer publishing to library-solidity CI feat(library-solidity): add Soldeer publishing to library-solidity CI Mar 17, 2026
Add publish-soldeer job to publish @fhevm-solidity to soldeer.xyz
on release, running in parallel with npm publish.
@poppyseedDev poppyseedDev force-pushed the poppyseed/publish-soldeer branch from 4d8e321 to e84da33 Compare March 17, 2026 14:30
@poppyseedDev
Copy link
Contributor Author

@Mergifyio queue

@mergify
Copy link

mergify bot commented Mar 17, 2026

Merge Queue Status

  • 🟠 Waiting for queue conditions
  • ⏳ Enter queue
  • ⏳ Run checks
  • ⏳ Merge
Required conditions to enter a queue
  • -closed [📌 queue requirement]
  • -conflict [📌 queue requirement]
  • -draft [📌 queue requirement]
  • any of [📌 queue -> configuration change requirements]:
    • -mergify-configuration-changed
    • check-success = Configuration changed
  • any of [🔀 queue conditions]:
    • all of [📌 queue conditions of queue main]:
      • #approved-reviews-by >= 1 [🛡 GitHub branch protection]
      • #changes-requested-reviews-by = 0 [🛡 GitHub branch protection]
      • #review-threads-unresolved = 0 [🛡 GitHub branch protection]
      • base = main
      • branch-protection-review-decision = APPROVED [🛡 GitHub branch protection]
      • label!=do-not-merge
      • any of [🛡 GitHub branch protection]:
        • check-success = common-pull-request/lint (bpr)
        • check-neutral = common-pull-request/lint (bpr)
        • check-skipped = common-pull-request/lint (bpr)
      • any of [🛡 GitHub branch protection]:
        • check-skipped = coprocessor-cargo-listener-tests/cargo-tests (bpr)
        • check-neutral = coprocessor-cargo-listener-tests/cargo-tests (bpr)
        • check-success = coprocessor-cargo-listener-tests/cargo-tests (bpr)
      • any of [🛡 GitHub branch protection]:
        • check-skipped = coprocessor-cargo-test/cargo-tests (bpr)
        • check-neutral = coprocessor-cargo-test/cargo-tests (bpr)
        • check-success = coprocessor-cargo-test/cargo-tests (bpr)
      • any of [🛡 GitHub branch protection]:
        • check-skipped = coprocessor-dependency-analysis/dependencies-check (bpr)
        • check-neutral = coprocessor-dependency-analysis/dependencies-check (bpr)
        • check-success = coprocessor-dependency-analysis/dependencies-check (bpr)
      • any of [🛡 GitHub branch protection]:
        • check-skipped = gateway-contracts-deployment-tests/sc-deploy (bpr)
        • check-neutral = gateway-contracts-deployment-tests/sc-deploy (bpr)
        • check-success = gateway-contracts-deployment-tests/sc-deploy (bpr)
      • any of [🛡 GitHub branch protection]:
        • check-skipped = kms-connector-tests/test-connector (bpr)
        • check-neutral = kms-connector-tests/test-connector (bpr)
        • check-success = kms-connector-tests/test-connector (bpr)

- name: Publish to Soldeer
env:
SOLDEER_API_TOKEN: ${{ secrets.SOLDEER_TOKEN }}
run: forge soldeer push @fhevm-solidity~${{ steps.version.outputs.version }} . --skip-warnings

Check notice

Code scanning / zizmor

code injection via template expansion Note

code injection via template expansion
Copy link
Contributor Author

Choose a reason for hiding this comment

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

fixed

Copy link
Collaborator

@immortal-tofu immortal-tofu left a comment

Choose a reason for hiding this comment

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

LGTM!

@mergify
Copy link

mergify bot commented Mar 17, 2026

🧪 CI Insights

Here's what we observed from your CI run for 530f411.

🟢 All jobs passed!

But CI Insights is watching 👀

@poppyseedDev
Copy link
Contributor Author

@Mergifyio queue

@mergify
Copy link

mergify bot commented Mar 17, 2026

queue

☑️ Command queue ignored because it is already running from a previous command.

@poppyseedDev poppyseedDev requested a review from enitrat March 17, 2026 15:22
@mergify
Copy link

mergify bot commented Mar 17, 2026

Merge Queue Status

This pull request spent 1 hour 35 minutes 28 seconds in the queue, including 34 minutes 17 seconds running CI.

Required conditions to merge

Reason

Pull request #2123 has been dequeued. The pull request could not be merged. This could be related to an activated branch protection or ruleset rule that prevents us from merging. (details: Repository rule violations found

All comments must be resolved.

)

Hint

You should look at the reason for the failure and decide if the pull request needs to be fixed or if you want to requeue it.
If you do update this pull request, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio queue comment.

@mergify mergify bot removed the merge-queued label Mar 17, 2026
mergify bot added a commit that referenced this pull request Mar 17, 2026
@mergify mergify bot added dequeued and removed queued labels Mar 17, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants