Added timescale toolkit and updated timescaledb

[Ignas]

Summary by CodeRabbit

• Chores
  • Updated TimescaleDB from version 2.21.3 to 2.22.1
  • Added TimescaleDB Toolkit version 1.21.0 to the build environment

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Walkthrough

The build configuration is updated to version Timescale from 2.21.3 to 2.22.1 and introduce Timescale Toolkit version 1.21.0 management. A new workflow step retrieves the toolkit version and passes it as a Docker build argument. The Dockerfile adds a build argument and installs the corresponding toolkit package. Build platforms are reduced to linux/amd64 only.

Changes

Cohort / File(s)	Summary
Workflow version and platform updates .github/workflows/build.yaml	Updated Timescale version from 2.21.3 to 2.22.1; added new step to fetch and output Timescale Toolkit version 1.21.0; passed toolkit version to Docker build arguments; reduced build platforms from linux/amd64,linux/arm64/v8 to linux/amd64 only
Dockerfile toolkit installation Dockerfile	Added TIMESCALE_TOOLKIT_VERSION build argument; installed timescaledb-toolkit-postgresql-$POSTGRES_VERSION=1:$TIMESCALE_TOOLKIT_VERSION~debian$VERSION_ID package with preceding apt-get update

Sequence Diagram(s)

sequenceDiagram
    participant Workflow as Build Workflow
    participant Docker as Docker Build
    
    Workflow->>Workflow: Get Timescale version (2.22.1)
    Note over Workflow: New step added
    Workflow->>Workflow: Get Timescale Toolkit version (1.21.0)
    Workflow->>Workflow: Generate Docker metadata
    Workflow->>Docker: Build image with:<br/>TIMESCALE_VERSION=2.22.1<br/>TIMESCALE_TOOLKIT_VERSION=1.21.0<br/>Platform: linux/amd64
    Docker->>Docker: Install timescaledb packages
    Docker->>Docker: Install timescaledb-toolkit<br/>(using version from ARG)
    Docker-->>Workflow: Image built successfully

Loading

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~8 minutes

• Straightforward version bumps and configuration updates
• New build argument introduces a standard pattern already used for Timescale version
• Single package installation addition follows existing conventions
• Platform reduction is a direct configuration change

Poem

🐰 Versions rise and toolkits flow,
Timescale's toolkit takes the stage,
From 2.21 to 2.22 we go,
Building images, page by page,
Docker's args now compile with glee! 📦✨

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 accurately summarizes the two main changes: adding Timescale Toolkit support and updating TimescaleDB version, matching the core modifications in both the workflow and Dockerfile.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch timescale-toolkit-and-version-bump

---

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 454ca4a and 95bdf22.

📒 Files selected for processing (2)

• .github/workflows/build.yaml (3 hunks)
• Dockerfile (2 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). (1)

• GitHub Check: Build Image (pg16)

🔇 Additional comments (6)

Dockerfile (2)

10-10: ARG declaration is well-scoped.

The TIMESCALE_TOOLKIT_VERSION argument is correctly positioned with other build arguments and will be used during toolkit installation.

---

28-30: Package name and epoch versioning are correct.

Web search verification confirms that Timescale's official Debian repository distributes timescaledb-toolkit packages with the epoch prefix 1: in the version specification. Examples from Timescale's packagecloud repository show the standard format: timescaledb-toolkit-postgresql-<VERSION>=1:<TOOLKIT_VERSION>~debian<VERSION_ID>. The epoch is a Debian versioning convention used by Timescale to ensure proper version ordering for package management.

.github/workflows/build.yaml (4)

53-60: Toolkit version extraction step is well-structured.

The new step follows the identical pattern as the existing Timescale version extraction (lines 45–52), correctly parsing the semantic version into major, minor, and full version outputs. The step ID timescale_toolkit is correctly referenced downstream in line 99.

---

92-92: ⚠️ Breaking change: Build platforms reduced to linux/amd64 only.

The build platforms have been reduced from the previous multi-platform configuration (likely including linux/arm64/v8) to linux/amd64 exclusively. This is a breaking change that will prevent image builds for ARM64 systems (e.g., Apple Silicon, AWS Graviton).

Verify that:

1. This platform reduction is intentional and has been communicated to users.
2. There are no outstanding ARM64 support requirements or pending use cases.
3. Arm64 support will not be re-introduced in the near term.

If ARM64 support should be maintained, restore the multi-platform configuration (e.g., platforms: linux/amd64,linux/arm64/v8).

---

95-99: Build-arg integration for toolkit version is correct.

The TIMESCALE_TOOLKIT_VERSION build argument is correctly added to the build-args list and references the output from the newly-added toolkit version extraction step. This aligns with the Dockerfile's consumption of the ARG TIMESCALE_TOOLKIT_VERSION at line 10.

---

7-7: Renovate datasource and Timescale Toolkit repository verified as correct.

The renovate datasource timescale/timescaledb-toolkit correctly references the upstream repository at https://github.com/timescale/timescaledb-toolkit. The datasource format and depName syntax are properly configured, matching the pattern used for TIMESCALE_VERSION. Note that version 1.21.0 is pinned in this PR, while the latest available release is 1.22.0 (published Oct 24, 2025).

Tip

📝 Customizable high-level summaries are now available in beta!

You can now customize how CodeRabbit generates the high-level summary in your pull requests — including its content, structure, tone, and formatting.

• Provide your own instructions using the high_level_summary_instructions setting.
• Format the summary however you like (bullet lists, tables, multi-section layouts, contributor stats, etc.).
• Use high_level_summary_in_walkthrough to move the summary from the description to the walkthrough section.

Example instruction:

"Divide the high-level summary into five sections:

1. 📝 Description — Summarize the main change in 50–60 words, explaining what was done.
2. 📓 References — List relevant issues, discussions, documentation, or related PRs.
3. 📦 Dependencies & Requirements — Mention any new/updated dependencies, environment variable changes, or configuration updates.
4. 📊 Contributor Summary — Include a Markdown table showing contributions:
   | Contributor | Lines Added | Lines Removed | Files Changed |
5. ✔️ Additional Notes — Add any extra reviewer context.
   Keep each section concise (under 200 words) and use bullet or numbered lists for clarity."

Note: This feature is currently in beta for Pro-tier users, and pricing will be announced later.

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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