[Chore]: Preparation for 1.1.0 version release#110
[Chore]: Preparation for 1.1.0 version release#110theMasudRana wants to merge 10 commits intodevelopfrom
Conversation
- Updated version in package.json, readme.txt, and rt-carousel.php to 1.1.0 - Added new features: carousel progress bar block, vertical alignment support, and wp-env configuration - Fixed issues with navigation buttons, block toolbar visibility, and carousel initialization state - Refactored plugin name from "Carousel Kit" to "rtCarousel" - Removed development files from distribution package
…omatic content migration
There was a problem hiding this comment.
Pull request overview
Prepares the rtCarousel WordPress plugin repository for the 1.1.0 release by synchronizing version metadata across plugin/distribution files, updating release notes, and adjusting the Node-based changelog tooling.
Changes:
- Bump version references to
1.1.0across plugin header, WordPress readme, npm package metadata, lockfile, and POT header. - Update
readme.txtwith upgrade guidance (from “Carousel Kit”), changelog entries, and an upgrade notice for 1.1.0. - Add
1.1.0release notes toCHANGELOG.mdand update changelog generation tooling/dependencies.
Reviewed changes
Copilot reviewed 5 out of 6 changed files in this pull request and generated 1 comment.
Show a summary per file
| File | Description |
|---|---|
| rt-carousel.php | Updates plugin header version to 1.1.0. |
| readme.txt | Updates stable tag, adds upgrade FAQ + 1.1.0 changelog + upgrade notice. |
| package.json | Bumps npm version to 1.1.0 and adjusts changelog script/deps. |
| package-lock.json | Syncs lockfile version and captures dependency/tooling updates. |
| languages/rt-carousel.pot | Updates Project-Id-Version and POT creation metadata; adds new strings. |
| CHANGELOG.md | Adds generated 1.1.0 release section with features/fixes/refactors. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 5 out of 6 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
…tency across patterns
…unt for improved functionality
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 11 out of 12 changed files in this pull request and generated 2 comments.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| * rename plugin from "Carousel Kit" to "rtCarousel" with automatic block content migration ([#101](https://github.com/rtCamp/rt-carousel/pull/101)) ([9788ed7](https://github.com/rtCamp/rt-carousel/commit/9788ed7)) | ||
|
|
||
|
|
||
| ## [1.0.4](https://github.com/rtCamp/carousel-kit/compare/v1.0.3...v1.0.4) (2026-03-09) | ||
|
|
There was a problem hiding this comment.
CHANGELOG.md mixes repository URLs: the new 1.1.0 section links to rtCamp/rt-carousel, but older releases (e.g., 1.0.4) still link to rtCamp/carousel-kit for compare/commit URLs. This makes the changelog inconsistent and can break/redirect links for readers. Consider updating the older release links to the current repository (or add a clear note explaining that pre-rename history lives in a different repo).
| { | ||
| "name": "rt-carousel", | ||
| "version": "1.0.4", | ||
| "version": "1.1.0", | ||
| "description": "Carousel block using Embla and WordPress Interactivity API", | ||
| "author": "rtCamp", |
There was a problem hiding this comment.
The PR description says only the plugin version was updated, but this PR also updates the readme (FAQ/changelog/upgrade notice), adds a 1.1.0 changelog entry, updates the .pot file, adjusts migration logging, and updates npm deps/lockfile. Please update the PR description (Summary / What changed / Testing details) to reflect the actual scope so release review is accurate.
Summary
This PR will update the required files to release the
1.1.0versionType of change
Related issue(s)
Closes #
Relates to # (if applicable)
What changed
Breaking changes
Does this introduce a breaking change? If yes, describe the impact and migration path below.
Testing
Describe how this was tested.
Test details:
Screenshots / recordings
If applicable, add screenshots or short recordings.
Checklist