[setoelkahfi]

Gets smbcloud-email ready for its first RubyGems release, using the same fixes #91 applied to smbcloud-auth and smbcloud-model.

What was wrong with the email gem:

• ext/email/Cargo.toml asked for smbcloud-email-sdk = "0.4", but the crate is at 0.7.6.
• magnus 0.7.1 does not build on Ruby 4.0.
• The gemspec packaged the .ruby-version symlink, so the source gem would not install.
• rb_sys ~> 0.9.91 let darwin bundles get an empty install name.
• The gem was not in release-sdk-gem.yml.

Changes:

• magnus 0.8, smbcloud-email-sdk 0.7, and the ruby() helper in lib.rs for the deprecated exception constructors. Clippy is clean.
• rb_sys >= 0.9.130, build.rs removed, .ruby-version and .rubocop.yml left out of the package.
• Cross-compile for x86_64-linux, aarch64-linux, arm64-darwin and x86_64-darwin, with the per-Ruby-minor loader in lib/email.rb.
• Removed the [patch.crates-io] path override from sdk/gems/email/Cargo.toml. It ships in the source gem and points outside it, so cargo failed during gem install. Without it the gem resolves smbcloud-email-sdk from crates.io like auth and model do.
• release-sdk-gem.yml builds and pushes email, and waits for smbcloud-email-sdk on crates.io. The version sync and drift scripts cover the email crate requirement.

Checked locally: rake build, then a source gem install into a temp dir on Ruby 3.4.2 and 4.0.7. require "email" loads, the client builds, and a bad key raises SmbCloud::Email::Error (401). The package has no symlinks. check-release-versions.mjs and actionlint pass.

Pushing now uses RubyGems trusted publishing instead of the RUBYGEMS_API_KEY secret: the push job has id-token: write and calls rubygems/[email protected]. Before dispatching a release, someone who owns the gems has to register trusted publishers on rubygems.org for smbcloudXYZ/smbcloud-cli, workflow release-sdk-gem.yml, no environment: one on each of smbcloud-auth and smbcloud-model, and a pending publisher for smbcloud-email.

To publish after merge, dispatch SDK Ruby Gem Release with tag=v0.7.6, ref=development. auth and model 0.7.6 get skipped as already pushed.

[sigit-code-review]

This change prepares the smbcloud-email gem for its first RubyGems release, aligning it with fixes previously applied to smbcloud-auth and smbcloud-model. It updates dependencies (magnus 0.8, smbcloud-email-sdk 0.7, rb_sys >= 0.9.130), removes problematic symlinks from the gem package, ensures correct cross-compilation for multiple platforms, and updates the loader logic in lib/email.rb to support per-Ruby-minor ABI bundles. The release workflow is updated to build and publish the email gem, and the version sync/drift scripts now cover the email gem's crate requirement. The Cargo.toml patch override is removed to allow proper resolution from crates.io. The Rust extension now uses the Ruby thread-safe exception constructors required by magnus 0.8. All changes are consistent with the description and prior review threads appear addressed.

---

Automated review by siGit Code Review · commit f612fd5 · see the review dashboard

[sigit-code-review]

This update extends the CI and release workflows to support the new smbcloud-email Ruby gem, aligning it with the fixes and patterns already applied to smbcloud-auth and smbcloud-model. The CI workflow now builds, cross-compiles, and smoke-tests all three gems (auth, model, email) for multiple platforms and Ruby versions, and validates the source gem file lists. The release workflow switches to RubyGems trusted publishing (OIDC) and documents the need for trusted publisher setup for each gem, including the new email gem. The changes are mostly additive, modularizing the gem jobs and ensuring robust checks for packaging and installation. No previous findings are reintroduced or made worse by these changes.

---

Automated review by siGit Code Review · commit 10c7579 · changes since f612fd5 · see the review dashboard