-
Notifications
You must be signed in to change notification settings - Fork 134
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
feat: Update dependencies to latest versions - less complex #1011
Conversation
WalkthroughThe changes in the pull request focus on updating the Other dependencies, including Additionally, the Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media? 🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I think this is the cause: conda/conda-build#5371 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Actionable comments posted: 1
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
📒 Files selected for processing (1)
- test/test_utils.py (2 hunks)
🧰 Additional context used
🪛 Ruff
test/test_utils.py
17-17:
conda_build.api
imported but unusedRemove unused import:
conda_build.api
(F401)
🔇 Additional comments (1)
test/test_utils.py (1)
655-656
: Improved exception handlingThe change from
SystemExit
toexceptions.CondaBuildUserError
is a good improvement. This modification provides more specific error handling for conda build processes.This change offers the following benefits:
- It provides a more precise exception type, making it easier to distinguish between different error scenarios.
- It aligns with best practices by using a custom exception from the
conda_build
package, which is likely designed for this specific use case.- It improves the overall error handling and debugging capabilities of the test suite.
@@ -652,7 +652,7 @@ def test_rendering_sandboxing(): | |||
assert ("'GITHUB_TOKEN' is undefined" in str(excinfo.value.stdout)) | |||
else: | |||
# recipe for "one" should fail because GITHUB_TOKEN is not a jinja var. | |||
with pytest.raises(SystemExit) as excinfo: | |||
with pytest.raises(exceptions.CondaBuildUserError) as excinfo: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hmm, we might need to update line 644 as well, if that behavior also changed.
🙏 |
🤖 I have created a release \*beep\* \*boop\* --- ## [3.4.0](https://www.github.com/bioconda/bioconda-utils/compare/v3.3.2...v3.4.0) (2024-10-21) ### Features * Update dependencies to latest versions - less complex ([#1011](https://www.github.com/bioconda/bioconda-utils/issues/1011)) ([167f348](https://www.github.com/bioconda/bioconda-utils/commit/167f348724e77384859e54c23b5226f2e67a1975)) --- This PR was generated with [Release Please](https://github.com/googleapis/release-please). See [documentation](https://github.com/googleapis/release-please#release-please). Co-authored-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
No description provided.