Skip to content

test: Update pixi.toml to change the AnyBody channel and version dependency #36

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Apr 7, 2025

Conversation

melund
Copy link
Member

@melund melund commented Apr 7, 2025

  • Updated the AnyBody channel from "anybody-beta" to "anybody".
  • Changed the version of anybodycon from "8.1.0beta4" to "8.1.0".

- Updated the AnyBody channel from "anybody-beta" to "anybody".
- Changed the version of anybodycon from "8.1.0beta4" to "8.1.0".
@melund melund requested a review from JacobAdamsen April 7, 2025 11:44
Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hello @melund, I'm Gemini Code Assist1! 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

This pull request updates the pixi.toml and pixi.lock files to reflect changes in the AnyBody channel and version dependency. Specifically, it switches the AnyBody channel from "anybody-beta" to "anybody" and updates the anybodycon version from "8.1.0beta4" to "8.1.0". The changes in pixi.lock reflect the updated dependencies and their corresponding versions for both Linux and Windows platforms.

Highlights

  • Channel Update: The AnyBody channel is updated from anybody-beta to anybody in both pixi.toml and pixi.lock.
  • Version Update: The anybodycon version is updated from 8.1.0beta4 to 8.1.0 in pixi.toml and the corresponding entry in pixi.lock is updated.
  • Dependency Updates: The pixi.lock file is updated with new versions and SHA256 hashes for various dependencies, including fonttools, glib, libcurl, libexpat, libffi, libglib, liblzma, pango, python_abi, pyzmq, setuptools, typing-extensions, vc, and vc14_runtime.

Changelog

  • pixi.lock
    • Updated the AnyBody channel from anybody-beta to anybody for the default and test environments.
    • Updated the version and SHA256 hash of anybodycon for the Windows platform in the test environment.
    • Updated versions and SHA256 hashes for various dependencies across Linux and Windows platforms, including fonttools, glib, libcurl, libexpat, libffi, libglib, liblzma, pango, python_abi, pyzmq, setuptools, typing-extensions, vc, and vc14_runtime.
  • pixi.toml
    • Updated the AnyBody channel from anybody-beta to anybody.
    • Changed the version of anybodycon from 8.1.0beta4 to 8.1.0.
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.


A beta's fleeting grace,
Replaced by stable pace,
Versions align,
Dependencies shine,
Code's journey finds its place.

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.

Copy link

@gemini-code-assist gemini-code-assist bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

The pull request updates the pixi.toml and pixi.lock files to switch from the 'anybody-beta' channel to the 'anybody' channel and updates the 'anybodycon' version from '8.1.0beta4' to '8.1.0'. This seems like a straightforward update to use the stable release versions. I have a few comments regarding the pixi.lock file.

Merge Readiness

The pull request updates the pixi.toml and pixi.lock files to switch from the 'anybody-beta' channel to the 'anybody' channel and updates the 'anybodycon' version from '8.1.0beta4' to '8.1.0'. I am unable to directly approve this pull request, and recommend that others review and approve this code before merging. Given the changes are dependency updates, I recommend merging this pull request after addressing the review comments.

Comment on lines +98 to +99
- conda: https://prefix.dev/conda-forge/linux-64/libexpat-2.7.0-h5888daf_0.conda
- conda: https://prefix.dev/conda-forge/linux-64/libffi-3.4.6-h2dba641_1.conda

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The change in libffi version from 3.4.6-h2dba641_0 to 3.4.6-h2dba641_1 might indicate a rebuild or a minor update. It would be helpful to understand the reason for this change, even if it's just a rebuild with the same source code. Can you confirm the reason for this change?

Comment on lines 108 to +109
- conda: https://prefix.dev/conda-forge/linux-64/liblapack-3.9.0-31_h7ac8fdf_openblas.conda
- conda: https://prefix.dev/conda-forge/linux-64/liblzma-5.6.4-hb9d3cd8_0.conda
- conda: https://prefix.dev/conda-forge/linux-64/liblzma-5.8.1-hb9d3cd8_0.conda

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The change in liblzma version from 5.6.4-hb9d3cd8_0 to 5.8.1-hb9d3cd8_0 is a more significant update. It would be helpful to understand the reason for this change and whether it introduces any compatibility issues. Can you confirm the reason for this change?

Comment on lines +325 to +326
- conda: https://prefix.dev/conda-forge/win-64/libexpat-2.7.0-he0c23c2_0.conda
- conda: https://prefix.dev/conda-forge/win-64/libffi-3.4.6-h537db12_1.conda

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The change in libffi version from 3.4.6-h537db12_0 to 3.4.6-h537db12_1 might indicate a rebuild or a minor update. It would be helpful to understand the reason for this change, even if it's just a rebuild with the same source code. Can you confirm the reason for this change?

Comment on lines 335 to +336
- conda: https://prefix.dev/conda-forge/win-64/liblapack-3.9.0-31_h1aa476e_mkl.conda
- conda: https://prefix.dev/conda-forge/win-64/liblzma-5.6.4-h2466b09_0.conda
- conda: https://prefix.dev/conda-forge/win-64/liblzma-5.8.1-h2466b09_0.conda

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

The change in liblzma version from 5.6.4-h2466b09_0 to 5.8.1-h2466b09_0 is a more significant update. It would be helpful to understand the reason for this change and whether it introduces any compatibility issues. Can you confirm the reason for this change?

@JacobAdamsen JacobAdamsen merged commit 0ab05e0 into master Apr 7, 2025
15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants