chore(main): [bot] release teuto-portal-k8s-worker:3.3.0

[teutonet-bot]

🤖 I have created a release beep boop

3.3.0 (2025-07-23)

Features

• teuto-portal-k8s-worker: use new pullPolicy template (#1384) (a4c2144)

Miscellaneous Chores

• teuto-portal-k8s-worker/dependencies: update common docker tag to v1.3.0 (#1363) (b6fa5e0)
• teuto-portal-k8s-worker/dependencies: update common docker tag to v1.4.0 (#1394) (260a99d)
• teuto-portal-k8s-worker/dependencies: update common docker tag to v1.5.0 (#1567) (3e0e84f)
• teuto-portal-k8s-worker/dependencies: update registry-gitlab.teuto.net/4teuto/dev/teuto-portal/teuto-portal-k8s-worker/teuto-portal-k8s-worker docker tag to v4.1.1 (#1568) (3ea6ef8)

---

This PR was generated with Release Please. See documentation.

Summary by CodeRabbit

• New Features

  • Introduced a new pullPolicy template for the teuto-portal-k8s-worker component.

• Chores

  • Updated docker tag dependencies to versions 1.3.0, 1.4.0, 1.5.0, and teuto-portal-k8s-worker docker tag to 4.1.1.
  • Bumped Helm chart version to 3.3.0.

[teutonet-bot]

🤖 I have diffed this beep boop

"/$namespace/$kind/$name.yaml" for normal resources
"/$namespace/HelmRelease/$name/$namespace/$kind/$name.yaml" for HelmReleases <- this is recursive
'null' means it's either cluster-scoped or it's in the default namespace for the HelmRelease

charts/teuto-portal-k8s-worker/ci/artifacthub-values.yaml

[charts/teuto-portal-k8s-worker/values.yaml]({"errors": ["Missing required field 'content'"]})

charts/teuto-portal-k8s-worker/ci/worker-values.yaml

[coderabbitai]

"""

Walkthrough

This change increments the version of the teuto-portal-k8s-worker Helm chart from 3.2.0 to 3.3.0 across relevant files, updates the changelog to reflect new features and dependency updates, and synchronizes the version in the release manifest.

Changes

Files	Change Summary
.github/release-please/manifest.json	Updated charts/teuto-portal-k8s-worker version from 3.2.0 to 3.3.0
charts/teuto-portal-k8s-worker/Chart.yaml, README.md	Updated chart version from 3.2.0 to 3.3.0; updated source URL and container image tag to 4.1.1 with SHA256 digest; bumped common dependency version to 1.5.0
charts/teuto-portal-k8s-worker/CHANGELOG.md	Added changelog entry for 3.3.0: new pullPolicy template feature, and updated docker tag dependencies

Estimated code review effort

1 (~2 minutes)

Suggested reviewers

• tasches
• marvinWolff
• cwrau

Poem

A hop, a skip, a version jump—
3.3.0 lands with a gentle thump!
Changelog grows, dependencies climb,
PullPolicy’s new, right on time.
The worker chart’s ready, so let’s deploy—
Another small leap, a bunny’s joy! 🐇✨
"""

---

📜 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 d5e284a and 37afc1c.

📒 Files selected for processing (2)

• charts/teuto-portal-k8s-worker/Chart.yaml (2 hunks)
• charts/teuto-portal-k8s-worker/README.md (3 hunks)

✅ Files skipped from review due to trivial changes (1)

• charts/teuto-portal-k8s-worker/README.md

🚧 Files skipped from review as they are similar to previous changes (1)

• charts/teuto-portal-k8s-worker/Chart.yaml

---

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

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Explain this complex logic.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai explain this code block.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and explain its main purpose.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

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)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR.
• @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[coderabbitai]

Actionable comments posted: 0

🧹 Nitpick comments (1)

charts/teuto-portal-k8s-worker/CHANGELOG.md (1)

13-14: Dependency Update Records
There are two entries updating the common docker tag—first to v1.3.0 and then to v1.4.0. Verify that both records are intentional and represent distinct updates. If they are part of a single update process, consider consolidating them for clarity.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a9d8ef2 and 8a6b2f3.

📒 Files selected for processing (4)

• .github/release-please/manifest.json (1 hunks)
• charts/teuto-portal-k8s-worker/CHANGELOG.md (1 hunks)
• charts/teuto-portal-k8s-worker/Chart.yaml (2 hunks)
• charts/teuto-portal-k8s-worker/README.md (2 hunks)

⏰ Context from checks skipped due to timeout of 90000ms (2)

• GitHub Check: generateDiffCommentBody
• GitHub Check: wait-for-checks

🔇 Additional comments (8)

.github/release-please/manifest.json (1)

1-2: Version Bump Verification
The manifest correctly updates the version for charts/teuto-portal-k8s-worker to "3.3.0" and the charts/common dependency to "1.4.0", which aligns with the PR objectives.

charts/teuto-portal-k8s-worker/CHANGELOG.md (2)

3-4: Changelog Version Header Updated
The section header for version 3.3.0 is updated with the correct comparison link and release date (2025-03-25), matching the intended release details.

---

6-8: New Feature Documentation
The changelog clearly documents the new pullPolicy template feature with a reference to issue [#1384] and the corresponding commit hash, ensuring transparency of the new functionality.

charts/teuto-portal-k8s-worker/README.md (3)

3-3: Version Badge Updated
The version badge now displays 3.3.0, which is consistent with the updated release.

---

17-18: Source Code Link Updated
The primary source code link is updated to point to the teuto-portal-k8s-worker-v3.3.0 branch. This ensures users are directed to the documentation corresponding to the latest release version.

---

24-24: Common Dependency Version Bumped
The requirement for the common dependency has been updated to 1.4.0, aligning with the changes in the release manifest and Chart.yaml.

charts/teuto-portal-k8s-worker/Chart.yaml (2)

5-5: Helm Chart Version Update
The chart’s version field is updated to 3.3.0, which is consistent with the overall release bump and accompanying documentation updates.

---

19-19: Source URL Updated
The source URL now correctly reflects the new branch (teuto-portal-k8s-worker-v3.3.0), ensuring that users can locate the precise version of the chart source code.

[teutonet-bot]

🤖 I have diffed this beep boop

"/$namespace/$kind/$name.yaml" for normal resources
"/$namespace/HelmRelease/$name/$namespace/$kind/$name.yaml" for HelmReleases <- this is recursive
'null' means it's either cluster-scoped or it's in the default namespace for the HelmRelease

charts/teuto-portal-k8s-worker/ci/artifacthub-values.yaml

[charts/teuto-portal-k8s-worker/values.yaml]({"errors": ["Missing required field 'content'"]})

charts/teuto-portal-k8s-worker/ci/worker-values.yaml

[teutonet-bot]

🤖 Created releases:

• teuto-portal-k8s-worker-v3.3.0

🌻