Skip to content

Conversation

dadangnh
Copy link
Contributor

@dadangnh dadangnh commented Sep 16, 2025

This pull request updates the n8n Helm chart to use the latest application version. The most important change is a version bump to ensure users deploy the most recent release of n8n.

Version updates:

  • Updated the version field in Chart.yaml from 1.0.14 to 1.0.15 and the appVersion field from 1.109.1 to 1.112.0 to reflect the new release.
  • Updated the change annotation to indicate the new n8n app version (1.112.0).

Summary by CodeRabbit

  • Chores
    • Upgraded Helm chart to 1.0.15 to deliver n8n 1.112.0.
    • Enables deployments to use the latest n8n release with upstream enhancements and fixes.
    • No changes to chart configuration or defaults; upgrade path remains unchanged.
    • Users can adopt the update via a standard Helm upgrade to access the newest improvements.

Copy link
Contributor

coderabbitai bot commented Sep 16, 2025

Walkthrough

Helm chart metadata updated in charts/n8n/Chart.yaml: chart version bumped from 1.0.14 to 1.0.15, appVersion from 1.109.1 to 1.112.0, and artifacthub.io/changes annotation text adjusted accordingly.

Changes

Cohort / File(s) Summary
Helm chart metadata bump
charts/n8n/Chart.yaml
Updated version to 1.0.15, appVersion to 1.112.0, and annotations.artifacthub.io/changes description to reflect the new app version.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

Suggested reviewers

  • Vad1mo
  • RoseSecurity

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 succinctly and accurately describes the primary change—bumping the n8n Helm chart and application versions to 1.0.15 and 1.112.0—and directly matches the PR objectives and the Chart.yaml updates in the raw summary, making it clear and useful for history scanning.
Docstring Coverage ✅ Passed No functions found in the changes. Docstring coverage check skipped.
✨ Finishing touches
🧪 Generate unit tests
  • Create PR with unit tests
  • Post copyable unit tests in a comment

Tip

👮 Agentic pre-merge checks are now available in preview!

Pro plan users can now enable pre-merge checks in their settings to enforce checklists before merging PRs.

  • Built-in checks – Quickly apply ready-made checks to enforce title conventions, require pull request descriptions that follow templates, validate linked issues for compliance, and more.
  • Custom agentic checks – Define your own rules using CodeRabbit’s advanced agentic capabilities to enforce organization-specific policies and workflows. For example, you can instruct CodeRabbit’s agent to verify that API documentation is updated whenever API schema files are modified in a PR. Note: Upto 5 custom checks are currently allowed during the preview period. Pricing for this feature will be announced in a few weeks.

Please see the documentation for more information.

Example:

reviews:
  pre_merge_checks:
    custom_checks:
      - name: "Undocumented Breaking Changes"
        mode: "warning"
        instructions: |
          Pass/fail criteria: All breaking changes to public APIs, CLI flags, environment variables, configuration keys, database schemas, or HTTP/GraphQL endpoints must be documented in the "Breaking Change" section of the PR description and in CHANGELOG.md. Exclude purely internal or private changes (e.g., code not exported from package entry points or explicitly marked as internal).

Please share your feedback with us on this Discord post.


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
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 (1)
charts/n8n/Chart.yaml (1)

36-39: Enhance Artifact Hub change entry with a release link (and align text if you choose stable).

Add a link to the release notes so users can inspect changes quickly. If you switch to 1.111.0 (stable), adjust the description accordingly.

Example with stable 1.111.0:

   artifacthub.io/changes: |
     - kind: changed
-      description: "Update n8n app version to 1.112.0"
+      description: "Update n8n app version to 1.111.0"
+      links:
+        - name: "n8n 1.111.0 release notes"
+          url: "https://github.com/n8n-io/n8n/releases/tag/n8n%401.111.0"

If you keep 1.112.0, link it instead and ensure artifacthub.io/prerelease is set to true. (github.com)

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between d06fe8b and a7e0e46.

📒 Files selected for processing (1)
  • charts/n8n/Chart.yaml (2 hunks)
🧰 Additional context used
🧠 Learnings (2)
📓 Common learnings
Learnt from: tsch157
PR: 8gears/n8n-helm-chart#239
File: charts/n8n/Chart.yaml:3-4
Timestamp: 2025-09-02T08:05:39.372Z
Learning: n8n 1.110.0 is a pre-release version and should not be used in production deployments. Always verify if a version is stable before recommending upgrades in the n8n Helm chart.
📚 Learning: 2025-09-02T08:05:39.372Z
Learnt from: tsch157
PR: 8gears/n8n-helm-chart#239
File: charts/n8n/Chart.yaml:3-4
Timestamp: 2025-09-02T08:05:39.372Z
Learning: n8n 1.110.0 is a pre-release version and should not be used in production deployments. Always verify if a version is stable before recommending upgrades in the n8n Helm chart.

Applied to files:

  • charts/n8n/Chart.yaml
⏰ 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: lint-test
🔇 Additional comments (2)
charts/n8n/Chart.yaml (2)

3-3: Chart version bump is appropriate.

Patch bump from 1.0.14 → 1.0.15 for an appVersion update aligns with SemVer for charts.


3-4: Fix appVersion/prerelease mismatch in charts/n8n/Chart.yaml

charts/n8n/Chart.yaml currently sets appVersion: 1.112.0 while annotation artifacthub.io/prerelease: "false". Deployment templates default image tags to .Chart.AppVersion (charts/n8n/templates/deployment*.yaml), so the chart will deploy the appVersion tag. If 1.112.0 is a pre-release, either pin to the latest stable or mark the chart as prerelease.

Option A — Stay on stable:

-appVersion: 1.112.0
+appVersion: 1.111.0

Option B — Track pre-release (also flip Artifact Hub flag):

-  artifacthub.io/prerelease: "false"
+  artifacthub.io/prerelease: "true"

Confirm upstream (GitHub releases) whether 1.112.0 is a pre-release before merging.

Copy link
Contributor

@RoseSecurity RoseSecurity left a comment

Choose a reason for hiding this comment

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

Thanks for this contribution

@Vad1mo Vad1mo merged commit 502c2ff into 8gears:main Sep 17, 2025
4 checks passed
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.

3 participants