@@ -1,5 +1,25 @@

# Changelog

## [v1.0.6](https://github.com/ably/laravel-broadcaster/tree/v1.0.6)

[Full Changelog](https://github.com/ably/laravel-broadcaster/compare/v1.0.5...v1.0.6)

**Fixed bugs:**

- Using -\>toOthers\(\) results in a "Ably error: Malformed message; invalid connectionKey" Same as issue 38 [\#48](https://github.com/ably/laravel-broadcaster/issues/48)

- Issue with client ID when using SPA like inertia [\#45](https://github.com/ably/laravel-broadcaster/issues/45)

**Closed issues:**

- Fix base64 decode [\#51](https://github.com/ably/laravel-broadcaster/issues/51)

- Monitor channel connection/disconnect [\#47](https://github.com/ably/laravel-broadcaster/issues/47)

- Using -\>toOthers\(\) results in a "Ably error: Malformed message; invalid connectionKey" [\#38](https://github.com/ably/laravel-broadcaster/issues/38)

**Merged pull requests:**

- \[ECO-4977\] Fix/broadcast to others [\#50](https://github.com/ably/laravel-broadcaster/pull/50) ([sacOO7](https://github.com/sacOO7))

- Update README [\#49](https://github.com/ably/laravel-broadcaster/pull/49) ([sacOO7](https://github.com/sacOO7))

## [v1.0.5](https://github.com/ably/laravel-broadcaster/tree/v1.0.5)

[Full Changelog](https://github.com/ably/laravel-broadcaster/compare/v1.0.4...v1.0.5)

@@ -243,16 +243,16 @@ Please see [CHANGELOG](CHANGELOG.md) for more information what has changed recen

## Release Process

This library uses [semantic versioning](http://semver.org/). For each release, the following needs to be done:

1. Create a new branch for the release, named like `release/1.2.4` (where `1.2.4` is what you're releasing, being the new version).

1. Create a new branch for the release, named like `release/1.0.6` (where `1.0.6` is what you're releasing, being the new version).

2. Update the lib version in `src/AblyBroadcaster.php`.

3. Run [`github_changelog_generator`](https://github.com/github-changelog-generator/github-changelog-generator) to automate the update of the [CHANGELOG.md](CHANGELOG.md). This may require some manual intervention, both in terms of how the command is run and how the change log file is modified. Your mileage may vary:

- The command you will need to run will look something like this: `github_changelog_generator -u ably -p laravel-broadcaster --since-tag v1.2.4 --output delta.md --token $GITHUB_TOKEN_WITH_REPO_ACCESS`. Generate token [here](https://github.com/settings/tokens/new?description=GitHub%20Changelog%20Generator%20token).

- The command you will need to run will look something like this: `github_changelog_generator -u ably -p laravel-broadcaster --since-tag v1.0.6 --output delta.md --token $GITHUB_TOKEN_WITH_REPO_ACCESS`. Generate token [here](https://github.com/settings/tokens/new?description=GitHub%20Changelog%20Generator%20token).

- Using the command above, `--output delta.md` writes changes made after `--since-tag` to a new file.

- The contents of that new file (`delta.md`) then need to be manually inserted at the top of the `CHANGELOG.md`, changing the "Unreleased" heading and linking with the current version numbers.

- Also ensure that the "Full Changelog" link points to the new version tag instead of the `HEAD`.

4. Commit generated [CHANGELOG.md](./CHANGELOG.md) file.

5. Make a PR against `main`.

6. Once the PR is approved, merge it into `main`.

7. Add a tag and push it to origin - e.g.: `git tag v1.2.4 && git push origin v1.2.4`.

7. Add a tag and push it to origin - e.g.: `git tag v1.0.6 && git push origin v1.0.6`.

8. Visit https://github.com/ably/laravel-broadcaster/tags and add release notes for the release including links to the changelog entry.

9. Visit https://packagist.org/packages/ably/laravel-broadcaster, log in to Packagist, and click the "Update" button.

@@ -14,7 +14,7 @@

class AblyBroadcaster extends Broadcaster

{

const LIB_VERSION = '1.0.5';

const LIB_VERSION = '1.0.6';

/**

* The AblyRest SDK instance.