-
Notifications
You must be signed in to change notification settings - Fork 0
Changelog
The Convert Ruby SDK publishes its release history through GitHub Releases. By design, the gem ships no CHANGELOG.md in the repository — the changelog lives entirely on GitHub Releases (the gemspec's changelog_uri points there).
→ github.com/convertcom/ruby-sdk/releases
Each release lists the version, the publish date, and notes grouped by change type (Features, Bug Fixes, Refactoring).
Releases are fully automated and run only from main — there is no manual version bump and no rake release task. The pipeline (semantic-release) reads the merged Conventional Commit subjects since the last release, computes the next semantic version, publishes the gem to RubyGems via OIDC Trusted Publishing, then tags vX.Y.Z and creates the GitHub Release with generated notes.
Which commit types drive a release:
| Commit type | Release | In notes |
|---|---|---|
fix: |
patch | Yes (Bug Fixes) |
feat: |
minor | Yes (Features) |
refactor: |
per preset | Yes (Refactoring) |
BREAKING CHANGE: footer / ! marker |
major | Yes |
chore:, docs:, ci:, test:, style:, perf:
|
none | No (hidden) |
All tags use the v prefix (v1.0.0, v1.2.3).
Pin a version in your Gemfile for reproducible builds:
gem "convert_sdk", "~> 1.0"Published versions are listed on the RubyGems listing and the GitHub Releases page.
- Installation — add and pin the gem
- Testing — the release-blocking verification gates
Copyrights © 2026 All Rights Reserved by Convert Insights, Inc.
Getting Started
Ruby SDK
- Quickstart
- Installation
- Initialization
- Configuration
- Return Types & Sentinels
- Code Examples
- Fork Safety & Runtime Recipes
- Tracking Control
Core Concepts
- Experiences & Variations
- Feature Flags
- Bucketing Algorithm
- Rule Evaluation
- Segments
- Data Management
- Event System
- API Communication
How-To Guides
- Running Experiences
- Running Features
- Tracking Conversions
- Visitor Context
- Persistent DataStore
- Troubleshooting
Contributing