release: merge v2.5.0 back into develop#481
Merged
gabitoesmiapodo merged 1 commit intodevelopfrom Apr 21, 2026
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Back-merges the release/v2.5.0 version bump into develop to keep long-lived branches aligned on the same package version.
Changes:
- Bumps
package.jsonversion from2.0.4to2.5.0.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
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
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
No related issue. Back-merge the v2.5.0 release branch into develop to keep the version bump in sync.
Standard git-flow step: brings the
release: bump version to 2.5.0commit from release/v2.5.0 back into develop so both long-lived branches stay at 2.5.0.Changes
Acceptance criteria
Test plan
Automated tests
No new tests — this is a version bump only.
Manual verification
No manual steps required.
Breaking changes
None.
Checklist
Screenshots
None.