Merge pull request #152 from ably/release/1.2.1

Release/1.2.1

CHANGELOG.md

@@ -1,5 +1,29 @@
 # Changelog
 
+## [v1.2.1](https://github.com/ably/ably-flutter/tree/v1.2.1)
+
+[Full Changelog](https://github.com/ably/ably-flutter/compare/v1.2.0...v1.2.1)
+
+**Implemented enhancements:**
+
+- Migrate to null safety [\#82](https://github.com/ably/ably-flutter/issues/82)
+
+**Closed issues:**
+
+- Investigate libraries that can help leverage our push implementation [\#142](https://github.com/ably/ably-flutter/issues/142)
+- Could not find method coreLibraryDesugaring\(\) for arguments [\#130](https://github.com/ably/ably-flutter/issues/130)
+- Create code snippets for homepage \(flutter\) [\#124](https://github.com/ably/ably-flutter/issues/124)
+- Make this SDK ready for the first non-preview release  [\#102](https://github.com/ably/ably-flutter/issues/102)
+- Activate and getting Push Notifications [\#54](https://github.com/ably/ably-flutter/issues/54)
+
+**Merged pull requests:**
+
+- Bump ws from 5.2.2 to 5.2.3 in /example/test\_harness [\#145](https://github.com/ably/ably-flutter/pull/145) ([dependabot[bot]](https://github.com/apps/dependabot))
+- Skip 1 failing test, fix 1 failing test and schedule tests on main twice a day [\#144](https://github.com/ably/ably-flutter/pull/144) ([ben-xD](https://github.com/ben-xD))
+- Refactor large files into 1 file per class [\#138](https://github.com/ably/ably-flutter/pull/138) ([ben-xD](https://github.com/ben-xD))
+- Add instructions for M1 macs and fixing ruby fatal error for example apps [\#137](https://github.com/ably/ably-flutter/pull/137) ([ben-xD](https://github.com/ben-xD))
+- Migrate to null-safety [\#136](https://github.com/ably/ably-flutter/pull/136) ([tiholic](https://github.com/tiholic))
+
 ## [v1.2.0](https://github.com/ably/ably-flutter/tree/v1.2.0)
 
 [Full Changelog](https://github.com/ably/ably-flutter/compare/1.2.0-preview.2...v1.2.0)

CONTRIBUTING.md

@@ -199,13 +199,16 @@ The release process must include the following steps:
 1. Ensure that all work intended for this release has landed to `main`
 2. Create a release branch named like `release/1.2.3`
 3. Add a commit to bump the version number
-4. Add a commit to update the change log
+4. Add a commit to update the change log. 
+  - Autogenerate the changelog contents by running `github_changelog_generator -u ably -p ably-flutter --since-tag 1.2.0 --output delta.md` and manually copying the relevant contents from `delta.md` into `CHANGELOG.md`
+  - Make sure to replace `HEAD` in the autogenerated URL's with the version tag you will create (e.g. `v1.2.1`).
 5. Push the release branch to GitHub
 6. Open a PR for the release against the release branch you just pushed
 7. Gain approval(s) for the release PR from maintainer(s)
 8. Land the release PR to `main`
 9. Execute `flutter pub publish` from the root of this repository
-10. Create a tag named like `v1.2.3` and push it to GitHub
+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`
 
 To check that everything is looking sensible to the Flutter tools, without publishing, you can use:
 

example/pubspec.lock

@@ -7,7 +7,7 @@ packages:
       path: ".."
       relative: true
     source: path
-    version: "1.2.0"
+    version: "1.2.1"
   async:
     dependency: transitive
     description:

pubspec.yaml

@@ -1,6 +1,6 @@
 name: ably_flutter
 description: A wrapper around Ably's Cocoa and Java client library SDKs, providing iOS and Android support.
-version: 1.2.0
+version: 1.2.1
 repository: https://github.com/ably/ably-flutter
 
 environment: