Downgrade Aether package version to 1.0.2

[yilmaztayfun]

Changed the AetherPackageVersion property from 1.0.7 to 1.0.2 in Directory.Build.props. This may be to address compatibility or stability issues with the newer version.

Summary by Sourcery

Bug Fixes:

• Downgrade AetherPackageVersion from 1.0.7 to 1.0.2 in Directory.Build.props to resolve compatibility and stability issues

Summary by CodeRabbit

• Chores
  • Updated Prism dependency version used by AetherPackageVersion to 1.0.2 for improved compatibility and stability.
  • No changes to features or public APIs; behavior remains unchanged for end-users.

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

This PR adjusts the project-wide Aether package version in the shared build props file to improve compatibility or stability by rolling back from 1.0.7 to 1.0.2.

File-Level Changes

Change	Details	Files
Downgrade Aether package version	AetherPackageVersion property updated from 1.0.7 to 1.0.2	templates/api/Directory.Build.props

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

Updated a single build configuration file to change the Prism AetherPackageVersion from 1.0.7 to 1.0.2 within templates/api/Directory.Build.props. No other package versions or public interfaces were modified.

Changes

Cohort / File(s)	Summary of Changes
Prism package version pin templates/api/Directory.Build.props	Changed AetherPackageVersion from 1.0.7 to 1.0.2; no other package versions altered.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

I nudge a digit, hop and grin,
From seven back to two I spin.
Aether hums in calmer tune,
Templates purr—no change too soon.
Carrot commit, small and bright,
Version pinned, all builds take flight! 🥕✨

Tip

🔌 Remote MCP (Model Context Protocol) integration is now available!

Pro plan users can now connect to remote MCP servers from the Integrations page. Connect with popular remote MCPs such as Notion and Linear to add more context to your reviews and chats.

---

📜 Recent review details

Configuration used: .coderabbit.yaml
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 3f32b5c and 31505aa.

📒 Files selected for processing (1)

• templates/api/Directory.Build.props (1 hunks)

✨ Finishing Touches

🧪 Generate unit tests

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch sonar

---

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

‼️ IMPORTANT
Auto-reply has been disabled for this repository in the CodeRabbit settings. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

CodeRabbit Commands (Invoked using PR/Issue comments)

Type @coderabbitai help to get the list of available commands.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

Status, Documentation and Community

• Visit our Status Page to check the current availability of CodeRabbit.
• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[gemini-code-assist]

Summary of Changes

Hello @yilmaztayfun, 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!

This pull request addresses potential compatibility or stability issues by downgrading the Aether package version. Specifically, it reverts the AetherPackageVersion property in the Directory.Build.props file from 1.0.7 back to 1.0.2. This ensures that the project utilizes a known stable version of the Aether package.

Highlights

• Aether Package Version Downgrade: The AetherPackageVersion in templates/api/Directory.Build.props has been reverted from 1.0.7 to 1.0.2. This change is likely intended to address potential compatibility or stability issues encountered with the newer version.

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 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. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

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.

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. ↩

[sourcery-ai]

Hey there - I've reviewed your changes and they look great!

---

Your trial expires on August 29, 2025. Please upgrade to continue using Sourcery ✨

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[gemini-code-assist]

Code Review

This pull request downgrades the Aether package from version 1.0.7 to 1.0.2. While the description suggests this is for compatibility or stability, downgrading a package significantly can introduce risks such as re-introducing old bugs, security vulnerabilities, or causing breaking changes with the existing code. My review comment requests more specific justification for this change to better understand its necessity and impact.

[gemini-code-assist]

Downgrading a package from version 1.0.7 to 1.0.2 is a significant change that can introduce risks. This could potentially re-introduce bugs or security vulnerabilities that were fixed in versions between 1.0.2 and 1.0.7. It might also cause breaking changes if the application code depends on features or APIs introduced after version 1.0.2.

To ensure the stability and security of the application, could you please provide more detailed context for this downgrade? Linking to a specific issue, bug report, or a more thorough explanation of the compatibility problems would be very helpful for reviewers to understand the trade-offs involved.