Skip to content

Conversation

aaronsteers
Copy link
Contributor

@aaronsteers aaronsteers commented Sep 19, 2025

Summary by CodeRabbit

  • Chores
    • Upgraded CI tooling to use Poetry 2.2.0 across automated fixes, PR commands, locking, linting, testing, and documentation workflows for improved stability and consistency.
  • Tests
    • Test pipelines now run with Poetry 2.2.0 to align dependency resolution across environments; no functional changes expected.
  • Documentation
    • Preview and publish pipelines now use Poetry 2.2.0 to streamline doc builds; content unaffected.

Important

Auto-merge enabled.

This PR is set to merge automatically when all requirements are met.

Copy link

👋 Greetings, Airbyte Team Member!

Here are some helpful tips and reminders for your convenience.

Testing This PyAirbyte Version

You can test this version of PyAirbyte using the following:

# Run PyAirbyte CLI from this branch:
uvx --from 'git+https://github.com/airbytehq/PyAirbyte.git@aj/bump-top-poetry-2.2.0' pyairbyte --help

# Install PyAirbyte from this branch for development:
pip install 'git+https://github.com/airbytehq/PyAirbyte.git@aj/bump-top-poetry-2.2.0'

Helpful Resources

PR Slash Commands

Airbyte Maintainers can execute the following slash commands on your PR:

  • /fix-pr - Fixes most formatting and linting issues
  • /poetry-lock - Updates poetry.lock file
  • /test-pr - Runs tests with the updated PyAirbyte

Community Support

Questions? Join the #pyairbyte channel in our Slack workspace.

📝 Edit this welcome message.

Copy link
Contributor

coderabbitai bot commented Sep 19, 2025

Warning

Rate limit exceeded

@aaronsteers has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 15 minutes and 49 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 67306e5 and fa23b59.

⛔ Files ignored due to path filters (1)
  • poetry.lock is excluded by !**/*.lock
📒 Files selected for processing (1)
  • .github/workflows/fix-pr-command.yml (3 hunks)
📝 Walkthrough

Walkthrough

All affected GitHub Actions workflows update the Gr1N/setup-poetry@v9 input poetry-version from "2.0.1" to "2.2.0". No other steps, conditions, or control flow were modified.

Changes

Cohort / File(s) Summary of Changes
Autofix workflow
.github/workflows/autofix.yml
Set Poetry version to "2.2.0" in Set up Poetry step.
PR command workflows
.github/workflows/fix-pr-command.yml, .github/workflows/test-pr-command.yml
Updated poetry-version from "2.0.1" to "2.2.0" in all Set up Poetry steps.
Poetry lock workflow
.github/workflows/poetry-lock-command.yml
Bumped poetry-version to "2.2.0" in two Set up Poetry steps.
Docs (pydoc) workflows
.github/workflows/pydoc_preview.yml, .github/workflows/pydoc_publish.yml
Changed Poetry setup to version "2.2.0"; no other edits.
Lint workflow
.github/workflows/python_lint.yml
Updated all Set up Poetry steps (ruff-lint-check, ruff-format-check, mypy-check) to "2.2.0".
Pytest workflows
.github/workflows/python_pytest.yml
Increased Poetry version to "2.2.0" across six Set up Poetry steps (pytest-fast x2, pytest-no-creds x2, pytest x1, dependency-analysis x1).

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Would you like to add a brief note in the PR description about verifying Poetry 2.2.x compatibility with your lockfile resolution to aid reviewers, wdyt?

Pre-merge checks and finishing touches

✅ Passed checks (3 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title Check ✅ Passed The title "chore: bump to poetry 2.2.0" succinctly and accurately summarizes the primary change — updating Poetry from 2.0.1 to 2.2.0 across the repository's GitHub Actions workflows — and follows a conventional "chore" prefix, making it clear and concise for teammates scanning history.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

Copy link

github-actions bot commented Sep 19, 2025

PyTest Results (Fast Tests Only, No Creds)

301 tests  ±0   301 ✅ +1   4m 32s ⏱️ -17s
  1 suites ±0     0 💤  - 1 
  1 files   ±0     0 ❌ ±0 

Results for commit fa23b59. ± Comparison against base commit 503b124.

♻️ This comment has been updated with latest results.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (11)
.github/workflows/fix-pr-command.yml (2)

100-104: Replace deprecated ::set-output with GITHUB_OUTPUT.

This step still uses the deprecated command; switch to file-based output to satisfy actionlint. Wdyt?

Apply:

-      run: |
-        git diff --quiet && echo "No changes to commit" || echo "::set-output name=changes::true"
+      run: |
+        if git diff --quiet; then
+          echo "No changes to commit"
+        else
+          echo "changes=true" >> "$GITHUB_OUTPUT"
+        fi

124-129: Same here: remove ::set-output in second diff check.

Mirror the fix for the second “unsafe” pass. Wdyt?

-      run: |
-        git diff --quiet && echo "No changes to commit" || echo "::set-output name=changes::true"
+      run: |
+        if git diff --quiet; then
+          echo "No changes to commit"
+        else
+          echo "changes=true" >> "$GITHUB_OUTPUT"
+        fi
.github/workflows/autofix.yml (1)

22-25: Poetry 2.2.0 bump LGTM; minor nit on commit message.

Step runs Ruff formatter but commit message says “Format code with black”. Consider updating the message for accuracy, wdyt?

-        git diff-index --quiet HEAD || git commit -m "Format code with black"
+        git diff-index --quiet HEAD || git commit -m "Format code with ruff format"
.github/workflows/python_lint.yml (3)

28-33: Duplicate Poetry setup — can we drop one to save time?

In ruff-lint-check, Poetry is set up twice (Lines 21–24 and 29–32). Removing one should speed CI slightly. Same pattern exists in mypy-check (Lines 69–72 and 77–80). Wdyt?


69-72: Poetry 2.2.0 bump LGTM; consider caching to speed installs.

Optional: add dependency caching (e.g., actions/cache keyed on poetry.lock + OS + py) to cut install time. Wdyt?


77-80: Second Poetry setup in mypy-check likely redundant.

Same dedupe suggestion as above. Wdyt?

.github/workflows/python_pytest.yml (2)

39-42: Two Poetry setup steps in pytest-fast — remove one?

You set Poetry twice (Lines 31–34 and 39–42). Dropping one should shorten CI. Wdyt?


104-107: Duplicate Poetry setup in pytest-no-creds.

Same dedupe opportunity as above. Wdyt?

.github/workflows/poetry-lock-command.yml (3)

100-103: Replace deprecated ::set-output with GITHUB_OUTPUT.

Modernize to avoid actionlint failures. Wdyt?

-      run: |
-        git diff --quiet && echo "No changes to commit" || echo "::set-output name=changes::true"
+      run: |
+        if git diff --quiet; then
+          echo "No changes to commit"
+        else
+          echo "changes=true" >> "$GITHUB_OUTPUT"
+        fi

129-136: Fix reference to undefined step id git-diff-2.

There’s no step with id git-diff-2 in this workflow, so this condition never resolves. Either add a second diff step or remove this clause. Wdyt?

-      if: steps.git-diff.outputs.changes != 'true' && steps.git-diff-2.outputs.changes != 'true'
+      if: steps.git-diff.outputs.changes != 'true'

106-113: Backticks in commit message trigger unintended command substitution.

git commit -m "Auto-commit \poetry lock` changes"executespoetry lock` inside the message. Use single quotes (or escape backticks) to avoid shell substitution. Wdyt?

-        git commit -m "Auto-commit `poetry lock` changes"
+        git commit -m 'Auto-commit `poetry lock` changes'
📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 8ef7237 and 67306e5.

⛔ Files ignored due to path filters (1)
  • poetry.lock is excluded by !**/*.lock
📒 Files selected for processing (8)
  • .github/workflows/autofix.yml (1 hunks)
  • .github/workflows/fix-pr-command.yml (1 hunks)
  • .github/workflows/poetry-lock-command.yml (1 hunks)
  • .github/workflows/pydoc_preview.yml (1 hunks)
  • .github/workflows/pydoc_publish.yml (1 hunks)
  • .github/workflows/python_lint.yml (3 hunks)
  • .github/workflows/python_pytest.yml (4 hunks)
  • .github/workflows/test-pr-command.yml (1 hunks)
⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (4)
  • GitHub Check: Pytest (All, Python 3.11, Ubuntu)
  • GitHub Check: Pytest (All, Python 3.10, Ubuntu)
  • GitHub Check: Pytest (No Creds)
  • GitHub Check: Pytest (Fast)
🔇 Additional comments (11)
.github/workflows/pydoc_publish.yml (1)

41-44: Poetry 2.2.0 bump looks good; please confirm lock compatibility.

No workflow logic change; just verify CI pulls Poetry 2.2.0 successfully and that no poetry lock format diffs are introduced compared to 2.0.1, especially for contributors using older local Poetry. Wdyt?

.github/workflows/fix-pr-command.yml (1)

84-87: Poetry 2.2.0 bump LGTM.

Thanks for keeping all workflows consistent. Wdyt?

.github/workflows/python_lint.yml (2)

21-24: Bump to Poetry 2.2.0 looks good.

No functional change; consistent with other workflows. Wdyt?


51-54: Poetry 2.2.0 bump LGTM here as well.

All good. Wdyt?

.github/workflows/pydoc_preview.yml (1)

24-27: Poetry 2.2.0 bump LGTM.

No other changes; docs generation should be unaffected. Wdyt?

.github/workflows/python_pytest.yml (4)

31-34: Poetry 2.2.0 bump LGTM (pytest-fast).

Looks consistent with the matrix. Wdyt?


96-99: Poetry 2.2.0 bump LGTM (pytest-no-creds).

All good. Wdyt?


178-181: Poetry 2.2.0 bump LGTM (pytest all).

No other logic changes. Wdyt?


251-254: Poetry 2.2.0 bump LGTM (dep analysis).

All good. Wdyt?

.github/workflows/poetry-lock-command.yml (1)

87-90: Poetry 2.2.0 bump LGTM.

Thanks for aligning lock workflow too. Wdyt?

.github/workflows/test-pr-command.yml (1)

116-119: Poetry 2.2.0 bump LGTM.

No other step changes; on-demand tests should behave the same. Wdyt?

@aaronsteers aaronsteers enabled auto-merge (squash) September 19, 2025 19:51
Copy link

PyTest Results (Full)

364 tests  ±0   348 ✅ ±0   21m 22s ⏱️ -19s
  1 suites ±0    16 💤 ±0 
  1 files   ±0     0 ❌ ±0 

Results for commit fa23b59. ± Comparison against base commit 503b124.

@aaronsteers aaronsteers merged commit 7560c51 into main Sep 19, 2025
23 checks passed
@aaronsteers aaronsteers deleted the aj/bump-top-poetry-2.2.0 branch September 19, 2025 20:15
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.

1 participant