Skip to content

Conversation

@octavia-bot-hoard
Copy link
Contributor

@octavia-bot-hoard octavia-bot-hoard bot commented Sep 16, 2025

Update source-clockify

This PR was autogenerated by running airbyte-ci connectors --name=source-clockify up_to_date --pull

We've set the auto-merge label on it, so it will be automatically merged if the CI pipelines pass.
If you don't want to merge it automatically, please remove the auto-merge label.
Please reach out to the Airbyte Connector Tooling team if you have any questions or concerns.

Operations

  • Upgrade the base image to the latest version in metadata.yaml: Successful

  • PATCH bump source-clockify version to 0.4.34: Successful

  • Build source-clockify docker image for platform(s) linux/amd64, linux/arm64: Successful

  • Get dependency updates: Successful

  • Create or update pull request on Airbyte repository: Successful

  • Add changelog entry: Successful

Dependency updates

We use syft to generate a SBOM for the latest connector version and the one from the PR.
It allows us to spot the dependencies that have been updated at all levels and for all types of dependencies (system, python, java etc.).
Here are the dependencies that have been updated compared to airbyte/source-clockify:latest.
Keep in mind that :latest does not always match the connector code on the main branch.
It is the latest released connector image when the head commit of this branch was created.

Type Name State Previous Version New Version
python airbyte-cdk updated 6.60.12 7.3.0
python anyio updated 4.10.0 4.11.0
python cattrs updated 24.1.2 25.2.0
python importlib_metadata updated 8.0.0 8.7.0
python joblib updated 1.5.1 1.5.2
python jsonschema updated 4.17.3 4.25.1
python pandas updated 2.2.2 2.2.3
python whenever updated 0.6.16 0.8.8
python zipp updated 3.19.2 3.23.0
python jsonschema-specifications added not present 2025.4.1
python referencing added not present 0.36.2
python rpds-py added not present 0.27.1
python filelock removed 3.18.0 not present
python pyrsistent removed 0.20.0 not present
@CLAassistant
Copy link

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
You have signed the CLA already but the status is still pending? Let us recheck it.

@github-actions
Copy link
Contributor

👋 Greetings, Airbyte Team Member!

Here are some helpful tips and reminders for your convenience.

Helpful Resources

PR Slash Commands

Airbyte Maintainers (that's you!) can execute the following slash commands on your PR:

  • /format-fix - Fixes most formatting issues.
  • /bump-version - Bumps connector versions.
    • You can specify a custom changelog by passing changelog. Example: /bump-version changelog="My cool update"
    • Leaving the changelog arg blank will auto-populate the changelog from the PR title.
  • /run-cat-tests - Runs legacy CAT tests (Connector Acceptance Tests)
  • /build-connector-images - Builds and publishes a pre-release docker image for the modified connector(s).
  • /poe connector source-example lock - Run the Poe lock task on the source-example connector, committing the results back to the branch.
  • /poe source example lock - Alias for /poe connector source-example lock.
  • /poe source example use-cdk-branch my/branch - Pin the source-example CDK reference to the branch name specified.
  • /poe source example use-cdk-latest - Update the source-example CDK dependency to the latest available version.

📝 Edit this welcome message.

@octavia-bot-hoard octavia-bot-hoard bot force-pushed the up-to-date/source-clockify branch from 4f6f814 to 16ed2fa Compare September 16, 2025 10:48
@octavia-bot-hoard octavia-bot-hoard bot enabled auto-merge (squash) September 16, 2025 10:48
@github-actions
Copy link
Contributor

github-actions bot commented Sep 16, 2025

source-clockify Connector Test Results

5 tests   2 ✅  7s ⏱️
1 suites  3 💤
1 files    0 ❌

Results for commit a799b18.

♻️ This comment has been updated with latest results.

@github-actions
Copy link
Contributor

github-actions bot commented Sep 16, 2025

Deploy preview for airbyte-docs ready!

✅ Preview
https://airbyte-docs-bamfov7bk-airbyte-growth.vercel.app

Built with commit a799b18.
This pull request is being automatically deployed with vercel-action

@octavia-bot-hoard octavia-bot-hoard bot force-pushed the up-to-date/source-clockify branch from 16ed2fa to 7fa24a2 Compare September 23, 2025 12:54
@octavia-bot-hoard octavia-bot-hoard bot changed the title 🐙 source-clockify: run up-to-date pipeline [2025-09-16] 🐙 source-clockify: run up-to-date pipeline [2025-09-23] Sep 23, 2025
@octavia-bot-hoard octavia-bot-hoard bot force-pushed the up-to-date/source-clockify branch from 7fa24a2 to b8ab540 Compare September 23, 2025 12:59
@octavia-bot-hoard octavia-bot-hoard bot force-pushed the up-to-date/source-clockify branch from b8ab540 to 3e801a1 Compare September 30, 2025 20:20
@octavia-bot-hoard octavia-bot-hoard bot changed the title 🐙 source-clockify: run up-to-date pipeline [2025-09-23] 🐙 source-clockify: run up-to-date pipeline [2025-09-30] Sep 30, 2025
…yaml; PATCH bump source-clockify version to 0.4.34; Build source-clockify docker image for platform(s) linux/amd64, linux/arm64; Get dependency updates; Create or update pull request on Airbyte repository; Add changelog entry
@octavia-bot-hoard octavia-bot-hoard bot force-pushed the up-to-date/source-clockify branch from 3e801a1 to a799b18 Compare September 30, 2025 20:23
@airbyteio airbyteio merged commit 69d224e into master Sep 30, 2025
29 of 31 checks passed
@airbyteio airbyteio deleted the up-to-date/source-clockify branch September 30, 2025 22:09
matteogp pushed a commit that referenced this pull request Oct 10, 2025
Co-authored-by: octavia-bot-hoard[bot] <230633153+octavia-bot-hoard[bot]@users.noreply.github.com>
Aymericcst pushed a commit to Aymericcst/airbyte that referenced this pull request Oct 13, 2025
) Co-authored-by: octavia-bot-hoard[bot] <230633153+octavia-bot-hoard[bot]@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment