Merge branch 'feature/release-v0.4.0' into development

Author: setoelkahfi

.agents/skills/ci-cd/SKILL.md

@@ -693,6 +693,15 @@ One practical warning: the Ruby gem release depends on crates.io propagation. If
 **SDK npm version out of sync with Rust crate version**
 `sdk/npm/smbcloud-auth/package.json` must have the same version as `crates/smbcloud-auth-sdk-wasm/Cargo.toml`. The `prepare-package.mjs` script compares them at build time and throws a hard error on mismatch. When bumping workspace crate versions for a release, always update the npm package version in the same commit. Forgetting this causes the `check-npm-sdk` CI job and the `release-sdk-npm` workflow to fail.
 
+**SDK Ruby gem versions out of sync with workspace crate versions**
+Three files must be bumped together for each gem in `sdk/gems/`:
+
+- `lib/<gem>/version.rb` — the gem version (`Auth::VERSION`, `Model::VERSION`)
+- `ext/<gem>/Cargo.toml` — the native extension crate version
+- `ext/<gem>/Cargo.toml` dependencies — the `smbcloud-*` version constraints (e.g. `"0.3"` → `"0.4"`)
+
+After bumping, regenerate lockfiles with `cargo generate-lockfile` and `bundle lock` inside each gem directory. The `release-sdk-gem` workflow checks `Auth::VERSION` against the tag and fails on mismatch.
+
 **Tagging a release on a feature branch instead of `development`**
 Always tag on `development` (the mainline branch). Tagging on a feature branch leaves `development` without the release commit, making git history confusing and future releases error-prone. Merge the feature branch into `development` first, then tag. If a tag was already placed on the wrong commit, move it with `git tag -f v<version>` and `git push origin v<version> --force`.
 

.agents/skills/smbcloud-cli-release/SKILL.md

@@ -36,6 +36,12 @@ The SDK npm package `@smbcloud/sdk-auth` must have its version in `sdk/npm/smbcl
 
 When bumping workspace crate versions for a release, always update `sdk/npm/smbcloud-auth/package.json` in the same commit.
 
+The same applies to the Ruby gems in `sdk/gems/`. For each gem (`auth`, `model`):
+
+- `lib/<gem>/version.rb` — the gem version constant
+- `ext/<gem>/Cargo.toml` — the native extension crate version AND the `smbcloud-*` dependency version constraints (e.g. `"0.3"` → `"0.4"`)
+- Regenerate `Cargo.lock` with `cargo generate-lockfile` and `Gemfile.lock` with `bundle lock` inside the gem directory
+
 ## Tagging discipline
 
 Always tag releases on the `development` branch (the mainline). Never tag on a feature branch.