Add v0.5.0 release notes

[ejscribner]

No description provided.

[gemini-code-assist]

Hello @ejscribner, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

Summary of Changes

Hello team, gemini-code-assist here to provide a summary of this pull request by @ejscribner.

The primary goal of this PR, as indicated by the title, is to add the release notes for version 0.5.0. This involves updating the documentation to reflect the new features and fixes included in this release. Additionally, the pull request includes updates to the yarn.lock file, which is a standard outcome of dependency management operations performed during development.

Highlights

• Release Notes Added: New release notes for version 0.5.0 have been added to the documentation.
• New Features Documented: The release notes highlight key features implemented in v0.5.0, including Collection Document Change, Query Change Listener (Live Query), and Replicator Status/Document Change for iOS.
• Bug Fix Documented: A fix related to the creation of duplicate database instances is also noted in the release notes.
• Dependency Lock File Update: The yarn.lock file has been updated, reflecting potential changes or reordering in project dependencies.

Changelog

• docs/ProductNotes/release-notes.md
  • Added a new section for version 0.5.0 release notes.
  • Documented 'Implemented Collection Document Change'.
  • Documented 'Implemented Query Change Listener (Live Query)'.
  • Documented 'Implemented Replicator Status Change and Replicator Document Change (iOS)'.
  • Documented 'Fixed issue related to creation of two database instances'.
• yarn.lock
  • Updated dependency lock file, reflecting changes in package versions or resolutions.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point in your pull request via creating an issue comment (i.e. comment on the pull request page) using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in issue comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist is currently in preview and may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments to provide feedback.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

---

Notes for release,
Features new bring us peace,
Lock file updates.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request primarily adds release notes for version 0.5.0, which is a valuable update for users. The notes themselves are clear and concise.

The changes to yarn.lock appear to be standard updates resulting from dependency management, such as reordering entries and simplifying version specifiers. These are generally fine, assuming CI processes pass without issues.

One important consideration for overall documentation quality, though outside the specific lines changed in this PR, is to review the "Known Issues" section in docs/ProductNotes/release-notes.md. The new 0.5.0 release notes indicate fixes or implementations for features (like Live Query and Replicator Status) that might have been previously listed as known issues. Updating this section to accurately reflect the current state of the software would be beneficial for users.

Summary of Findings

• Documentation Accuracy: Known Issues Section: The 'Known Issues' section in docs/ProductNotes/release-notes.md may be outdated. Release 0.5.0 includes implementations for 'Query Change Listener (Live Query)' and 'Replicator Status Change'. If these address previously documented known issues, the 'Known Issues' section should be updated for accuracy. This feedback pertains to content outside the diff and is noted here for consideration (medium impact on documentation clarity).
• Markdown Formatting: Release Version Headers: In docs/ProductNotes/release-notes.md (line 7), the new release version **0.5.0** is formatted using bold text. For improved semantic structure and potentially better navigation in very long release notes, consider using a Markdown heading (e.g., ## 0.5.0). This is a minor stylistic suggestion (low severity) and was not commented on inline due to review settings.

Merge Readiness

The changes in this pull request, specifically the addition of release notes for v0.5.0, are well-implemented and clear. The yarn.lock changes seem to be routine.

Before merging, I'd recommend a quick review of the 'Known Issues' section in the release-notes.md file to ensure it's up-to-date with the changes introduced in v0.5.0, as mentioned in the general feedback.

Otherwise, the PR appears to be in good shape. As a language model, I am not authorized to approve pull requests; please ensure further review and approval as per your team's policies.