release: v1.3.0 - #56
Merged
Merged
Conversation
Bump the gem version to 1.3.0 and add the CHANGELOG entry. 1.3.0 is a minor release adding two backward-compatible features since 1.2.0: - Date-based Elasticsearch index names via strftime tokens in the tag (#27). - Composite primary key support in mysql_replicator (#7). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Release v1.3.0 (minor). Bumps
s.versionto1.3.0and adds the CHANGELOG entry.Consolidates the two backward-compatible features merged since v1.2.0.
What's in 1.3.0
Added
%Y%m%d) inthe tag's index-name segment are expanded using the record's event time,
enabling Logstash-style dated indices like
myindex-20180831. (How to change Index name in elasticsearch like logstash with date #27, feat: date-based Elasticsearch index names via strftime (#27) #54)mysql_replicator—primary_keyaccepts acomma-separated list of columns, used for change detection and as the
Elasticsearch document
_id. Single-column keys are unchanged. (Deals with tables with composite primary key #7, feat: composite primary key support in mysql_replicator (#7) #55)Versioning rationale
Both changes are new, backward-compatible features → MINOR bump (1.2.0 → 1.3.0).
(The plugin-managed index template feature is intentionally not in this
release; it will land separately because it raises the minimum Elasticsearch
version.)
Post-merge release steps (maintainer)
git checkout master && git pull git tag v1.3.0 git push origin v1.3.0 gem build fluent-plugin-mysql-replicator.gemspec gem push fluent-plugin-mysql-replicator-1.3.0.gem🤖 Generated with Claude Code