Skip to content

Release 14.2.1 into trunk #707

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
iangmaia wants to merge 1 commit into from
Closed

Release 14.2.1 into trunk #707

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -14,12 +14,18 @@ _None_

### Bug Fixes

- Added optional `next_version` parameter to `android_update_release_notes` and `ios_update_release_notes` actions, allowing callers to provide the next version directly instead of relying on the built-in calculator that assumes minor version caps at 9. This fixes incorrect version bumps (e.g., 8.9 → 9.0 instead of 8.10) for apps using semantic versioning. [#706]
_None_

### Internal Changes

_None_

## 14.2.1

### Bug Fixes

- Added optional `next_version` parameter to `android_update_release_notes` and `ios_update_release_notes` actions, allowing callers to provide the next version directly instead of relying on the built-in calculator that assumes minor version caps at 9. This fixes incorrect version bumps (e.g., 8.9 → 9.0 instead of 8.10) for apps using semantic versioning. [#706]
Copy link
Copy Markdown
Contributor

@AliSoftware AliSoftware Mar 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

A bit pedantic of me, but while this is a bugfix (which is why it was considered being a patch semver bump)… in practice the fix for the bug consisted of adding a new parameter to the action and thus changing the API (even if in a backwards-compatible way), so IMHO that should be a minor version bump, not a patch for that reason.

Copy link
Copy Markdown
Contributor Author

@iangmaia iangmaia Mar 30, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Haha, I thought exactly about it right after I ran rake new_version and wondered the same 😄 oh well. Let's do it properly.


## 14.2.0

### New Features
Expand Down
2 changes: 1 addition & 1 deletion Gemfile.lock
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
PATH
remote: .
specs:
fastlane-plugin-wpmreleasetoolkit (14.2.0)
fastlane-plugin-wpmreleasetoolkit (14.2.1)
activesupport (>= 6.1.7.1, < 8)
buildkit (~> 1.5)
chroma (= 0.2.0)
Expand Down
2 changes: 1 addition & 1 deletion lib/fastlane/plugin/wpmreleasetoolkit/version.rb
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -3,6 +3,6 @@
module Fastlane
module Wpmreleasetoolkit
NAME = 'fastlane-plugin-wpmreleasetoolkit'
VERSION = '14.2.0'
VERSION = '14.2.1'
end
end