Skip to content

Bump flutter_custom_tabs version to 2.6.0#308

Merged
droibit merged 1 commit into
developfrom
bump-version
Jul 26, 2026
Merged

Bump flutter_custom_tabs version to 2.6.0#308
droibit merged 1 commit into
developfrom
bump-version

Conversation

@droibit

@droibit droibit commented Jul 26, 2026

Copy link
Copy Markdown
Owner

No description provided.

@droibit droibit added this to the 2.6.0 milestone Jul 26, 2026
@droibit droibit self-assigned this Jul 26, 2026
Copilot AI review requested due to automatic review settings July 26, 2026 08:18

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Pull request overview

Bumps the app-facing flutter_custom_tabs package for the 2.6.0 release, aligning its dependency constraints with the current federated platform package versions in this repo.

Changes:

  • Updates flutter_custom_tabs package version to 2.6.0 and removes publish_to: 'none' to allow publishing.
  • Switches federated dependencies from local path: references to hosted version constraints, matching current package versions.
  • Finalizes the flutter_custom_tabs changelog entry for 2.6.0 and documents updated minimum required platform package versions.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.

File Description
flutter_custom_tabs/pubspec.yaml Bumps package version to 2.6.0, enables publishing, and replaces path dependencies with versioned federated dependencies.
flutter_custom_tabs/CHANGELOG.md Renames the top entry to 2.6.0 and notes updated minimum required platform package versions.

@droibit
droibit merged commit 79bbf78 into develop Jul 26, 2026
3 checks passed
@droibit
droibit deleted the bump-version branch July 26, 2026 08:25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants