Update repository references for rename to ably-pubsub-flutter

.claude/skills/release/SKILL.md

@@ -49,16 +49,16 @@ Then perform these steps in order:
    ```
    Filter the PRs to only those merged after that tag date. Format each as:
    ```
-   - Short, one sentence summary from PR title [#NUMBER](https://github.com/ably/ably-flutter/pull/NUMBER)
+   - Short, one sentence summary from PR title [#NUMBER](https://github.com/ably/ably-pubsub-flutter/pull/NUMBER)
    ```
    If the tag doesn't exist or there are no merged PRs, use a single `-` placeholder bullet instead.
 
 6. In `CHANGELOG.md`, insert the following block immediately after the `# Changelog` heading (and its trailing blank line), before the first existing `## [` version entry:
 
 ```
-## [NEW_VERSION](https://github.com/ably/ably-flutter/tree/vNEW_VERSION)
+## [NEW_VERSION](https://github.com/ably/ably-pubsub-flutter/tree/vNEW_VERSION)
 
-[Full Changelog](https://github.com/ably/ably-flutter/compare/vOLD_VERSION...vNEW_VERSION)
+[Full Changelog](https://github.com/ably/ably-pubsub-flutter/compare/vOLD_VERSION...vNEW_VERSION)
 
 BULLETS_FROM_STEP_5
 

.github/workflows/docs.yml

@@ -33,7 +33,7 @@ jobs:
         uses: aws-actions/configure-aws-credentials@67fbcbb121271f7775d2e7715933280b06314838 # v1.7.0
         with:
           aws-region: eu-west-2
-          role-to-assume: arn:aws:iam::${{ secrets.ABLY_AWS_ACCOUNT_ID_SDK }}:role/ably-sdk-builds-ably-flutter
+          role-to-assume: arn:aws:iam::${{ secrets.ABLY_AWS_ACCOUNT_ID_SDK }}:role/ably-sdk-builds-ably-pubsub-flutter
           role-session-name: "${{ github.run_id }}-${{ github.run_number }}"
 
       - name: Upload Documentation

.github/workflows/features.yml

@@ -17,6 +17,6 @@ jobs:
       id-token: write
     uses: ably/features/.github/workflows/sdk-features.yml@6b3fc7a8ede2ebdd7a6325314f3a96c6466f1453 # main
     with:
-      repository-name: ably-flutter
+      repository-name: ably-pubsub-flutter
     secrets:
       ABLY_AWS_ACCOUNT_ID_SDK: ${{ secrets.ABLY_AWS_ACCOUNT_ID_SDK }}

API_REF_INTRO_BLURB.md

@@ -1,6 +1,6 @@
 # Ably Flutter Client Library SDK API Reference
 
-The Flutter Client Library SDK supports a realtime and a REST interface. The Flutter API references are generated from the [Ably Flutter Client Library SDK source code](https://github.com/ably/ably-flutter/) using [dartdoc](https://dart.dev/tools/dart-doc) and structured by classes.
+The Flutter Client Library SDK supports a realtime and a REST interface. The Flutter API references are generated from the [Ably Flutter Client Library SDK source code](https://github.com/ably/ably-pubsub-flutter/) using [dartdoc](https://dart.dev/tools/dart-doc) and structured by classes.
 
 The realtime interface enables a client to maintain a persistent connection to Ably and publish, subscribe and be present on channels. The REST interface is stateless and typically implemented server-side. It is used to make requests such as retrieving statistics, token authentication and publishing to a channel.
 

CONTRIBUTING.md

@@ -21,9 +21,9 @@ There are two different ways the example application can be configured to use Ab
 
 Under the run/ debug configuration drop down menu, click `Edit Configurations...`. Duplicate the `Example App (Duplicate and modify)` configuration. Leave the "Store as project file" unchecked to avoid committing your Ably API key into a repository. Update this new run configuration's `additional run args` with your ably API key. Run or debug the your new run/ debug configuration.
 
-![Drop down menu for Run/Debug Configurations in Android Studio](https://github.com/ably/ably-flutter/raw/main/images/run-configuration-1.png)
+![Drop down menu for Run/Debug Configurations in Android Studio](https://github.com/ably/ably-pubsub-flutter/raw/main/images/run-configuration-1.png)
 
-![Run/Debug Configurations window in Android Studio](https://github.com/ably/ably-flutter/raw/main/images/run-configuration-2.png)
+![Run/Debug Configurations window in Android Studio](https://github.com/ably/ably-pubsub-flutter/raw/main/images/run-configuration-2.png)
 
 #### Visual Studio Code
 
@@ -171,7 +171,7 @@ Documentation stored in repository should follow the schema defined in [Ably Tem
 
 ### Including images in markdown files
 
-When referencing images in markdown files, using a local path such as `images/android.png`, for example `![An android device running on API level 30](images/android.png)` will result in the image missing on pub.dev README preview. Therefore, we currently reference images through the github.com URL path (`https://github.com/ably/ably-flutter/raw/`), for example to reference `images/android.png`, we would use `![An android device running on API level 30](https://github.com/ably/ably-flutter/raw/main/images/android.png)`. [A suggestion](https://github.com/dart-lang/pub-dev/issues/5068) has been made to automatically replace this relative image path to the github URL path.
+When referencing images in markdown files, using a local path such as `images/android.png`, for example `![An android device running on API level 30](images/android.png)` will result in the image missing on pub.dev README preview. Therefore, we currently reference images through the github.com URL path (`https://github.com/ably/ably-pubsub-flutter/raw/`), for example to reference `images/android.png`, we would use `![An android device running on API level 30](https://github.com/ably/ably-pubsub-flutter/raw/main/images/android.png)`. [A suggestion](https://github.com/dart-lang/pub-dev/issues/5068) has been made to automatically replace this relative image path to the github URL path.
 
 ## Release Process (Claude Code)
 
@@ -181,13 +181,13 @@ When referencing images in markdown files, using a local path such as `images/an
 4. Create a release PR (ensure you include an SDK Team Engineering Lead and the SDK Team Product Manager as reviewers) and gain approvals for it, then merge that to `main`
 5. Create a tag named like `v2.0.1` and push it to GitHub - e.g. `git tag v2.0.1 && git push origin v2.0.1`
 6. Create the release on GitHub including populating the release notes
-7. Go to the [Release Workflow](https://github.com/ably/ably-flutter/actions/workflows/release.yaml) and ask [ably/team-sdk](https://github.com/orgs/ably/teams/team-sdk) member to approve publishing to the pub.dev registry
+7. Go to the [Release Workflow](https://github.com/ably/ably-pubsub-flutter/actions/workflows/release.yaml) and ask [ably/team-sdk](https://github.com/orgs/ably/teams/team-sdk) member to approve publishing to the pub.dev registry
 8. Update the [Ably Changelog](https://changelog.ably.com/) (via [headwayapp](https://headwayapp.co/)) with these changes
 
 ## Release Process (Manual)
 
 Releases should always be made through a release pull request (PR), which needs to bump the version number and add to the [change log](CHANGELOG.md).
-For an example of a previous release PR, see [#89](https://github.com/ably/ably-flutter/pull/89).
+For an example of a previous release PR, see [#89](https://github.com/ably/ably-pubsub-flutter/pull/89).
 
 The release process must include the following steps:
 
@@ -211,8 +211,8 @@ The release process must include the following steps:
 9. Land the release PR to `main`
 10. Create a tag named like `v1.2.3`, using `git tag v1.2.3`
 11. Push the newly created tag to GitHub: `git push origin v1.2.3`
-12. Create a release on GitHub following the [previous releases]((https://github.com/ably/ably-flutter/releases)) as examples.
-13. Go to the [Release Workflow](https://github.com/ably/ably-flutter/actions/workflows/release.yaml) and ask [ably/team-sdk](https://github.com/orgs/ably/teams/team-sdk) member to approve publishing to the pub.dev registry
+12. Create a release on GitHub following the [previous releases]((https://github.com/ably/ably-pubsub-flutter/releases)) as examples.
+13. Go to the [Release Workflow](https://github.com/ably/ably-pubsub-flutter/actions/workflows/release.yaml) and ask [ably/team-sdk](https://github.com/orgs/ably/teams/team-sdk) member to approve publishing to the pub.dev registry
 14. Update the [Ably Changelog](https://changelog.ably.com/) (via [headwayapp](https://headwayapp.co/)) with these changes
 
 We tend to use [github_changelog_generator](https://github.com/skywinder/Github-Changelog-Generator) to collate the information required for a change log update.

README.md

@@ -1,6 +1,6 @@
 ![Ably Pub/Sub Flutter Header](images/flutter-github.png)
 [![Pub Version](https://img.shields.io/pub/v/ably_flutter)](https://pub.dev/packages/ably_flutter)
-[![License](https://badgen.net/github/license/ably/ably-flutter)](https://github.com/ably/ably-flutter/blob/main/LICENSE)
+[![License](https://badgen.net/github/license/ably/ably-pubsub-flutter)](https://github.com/ably/ably-pubsub-flutter/blob/main/LICENSE)
 
 ---
 
@@ -121,4 +121,4 @@ Read the [CONTRIBUTING.md](./CONTRIBUTING.md) guidelines to contribute to Ably.
 
 ## Support, feedback, and troubleshooting
 
-For help or technical support, visit the [Ably Support page](https://ably.com/support) or [GitHub Issues](https://github.com/ably/ably-flutter/issues) for community-reported bugs and discussions.
+For help or technical support, visit the [Ably Support page](https://ably.com/support) or [GitHub Issues](https://github.com/ably/ably-pubsub-flutter/issues) for community-reported bugs and discussions.

pubspec.yaml

@@ -1,7 +1,7 @@
 name: ably_flutter
 description: A wrapper around Ably's Cocoa and Java client library SDKs, providing iOS and Android support.
 version: 1.2.44
-repository: https://github.com/ably/ably-flutter
+repository: https://github.com/ably/ably-pubsub-flutter
 
 environment:
   sdk: ">=2.14.0 <4.0.0"