release: prepare v1.1.0

[jeswr]

Release steps:

1. Inspecting the CHANGELOG.md to determine if the release was major, minor or patch. Make sure you align with the rest of the team first.
2. Use npm version --no-git-tag-version <major|minor|patch> to update package.json.
3. Update the CHANGELOG.md has been updated to show version and release date.
4. Add any @since X.Y.Z annotations if there have been any added or deprecated APIs.
5. Commit the changes as release: prepare vX.Y.Z on a branch named release/X.Y.Z
6. Create a PR, once CI passes, merge as a squash merge.
7. Create and publish the release via GitHub, this will create the tag and trigger the npm publish.

[vercel]

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name	Status	Preview	Updated
solid-client-notifications-js	✅ Ready (Inspect)	Visit Preview	Jul 5, 2022 at 11:26AM (UTC)

[ThisIsMissEm]

I'd like to land #302 first

[jeswr]

@ThisIsMissEm - this now up to date with those changes. Can I grab your approval to merge if there was nothing else you wanted to land first?