commit
efeef2831e
3 changed files with 6 additions and 3 deletions
|
|
@ -7,6 +7,8 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
|
|||
|
||||
## [Unreleased]
|
||||
|
||||
## [0.2.0] - 2025-07-15
|
||||
|
||||
### Added
|
||||
|
||||
- Custom methods support via `define_custom_method` (#75)
|
||||
|
|
|
|||
|
|
@ -588,7 +588,8 @@ This gem is published to [RubyGems.org](https://rubygems.org/gems/mcp)
|
|||
Releases are triggered by PRs to the `main` branch updating the version number in `lib/mcp/version.rb`.
|
||||
|
||||
1. **Update the version number** in `lib/mcp/version.rb`, following [semver](https://semver.org/)
|
||||
2. **Create A PR and get approval from a maintainer**
|
||||
3. **Merge your PR to the main branch** - This will automatically trigger the release workflow via GitHub Actions
|
||||
1. **Update CHANGELOG.md**, backfilling the changes since the last release if necessary, and adding a new section for the new version, clearing out the Unreleased section
|
||||
1. **Create a PR and get approval from a maintainer**
|
||||
1. **Merge your PR to the main branch** - This will automatically trigger the release workflow via GitHub Actions
|
||||
|
||||
When changes are merged to the `main` branch, the GitHub Actions workflow (`.github/workflows/release.yml`) is triggered and the gem is published to RubyGems.
|
||||
|
|
|
|||
|
|
@ -1,5 +1,5 @@
|
|||
# frozen_string_literal: true
|
||||
|
||||
module MCP
|
||||
VERSION = "0.1.0"
|
||||
VERSION = "0.2.0"
|
||||
end
|
||||
|
|
|
|||
Loading…
Reference in a new issue