Skip to content

[Release] Bump version to 0.18.0#115

Merged
Pavan-SAP merged 1 commit into
mainfrom
release-0.18.0
Jul 3, 2026
Merged

[Release] Bump version to 0.18.0#115
Pavan-SAP merged 1 commit into
mainfrom
release-0.18.0

Conversation

@anirudhprasad-sap

@anirudhprasad-sap anirudhprasad-sap commented Jul 3, 2026

Copy link
Copy Markdown
Contributor

Release: Bump Version to 0.18.0

🔖 Chore: Bumps the @cap-js/cap-operator-plugin package version from 0.17.0 to 0.18.0 and updates the changelog with the new release entry.

Changes

  • CHANGELOG.md: Added release notes for v0.18.0 (03-July-2026), noting compatibility with CAP Operator v0.32.0 or later. Documents the new rolloutOnCredentialUpdate field added to CAPApplication spec. Also minor formatting fix for the v0.17.0 heading.
  • package.json: Bumped version from 0.17.0 to 0.18.0.
  • package-lock.json: Updated lock file to reflect the new version 0.18.0.

What's New in 0.18.0

  • ✨ Added rolloutOnCredentialUpdate field to CAPApplication spec — when enabled, workloads are automatically redeployed when their service credentials are updated.

  • ⚠️ Requires CAP Operator v0.32.0 or later.

  • 🔄 Regenerate and Update Summary

PR Bot Information

Version: 1.26.14

  • File Content Strategy: Full file content
  • Output Template: Default Template
  • LLM: anthropic--claude-4.6-sonnet
  • Summary Prompt: Default Prompt
  • Correlation ID: deccaf20-76cf-11f1-89e8-4fd8b10d944e
  • Event Trigger: pull_request.opened

@hyperspace-pr-bot hyperspace-pr-bot Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

Wait — the date 03-July-2026 and 26-June-2026 actually use the same DD-Month-YYYY format. Let me reconsider whether there's a real inconsistency.

Both use DD-Month-YYYY, so the format is actually consistent. The suggestion I posted is incorrect (it also changes "July" to "June" which is wrong). This is not a real issue.

The PR is a clean, consistent version bump. All three files (package.json, package-lock.json, CHANGELOG.md) are aligned on 0.18.0, the changelog entry is properly formatted, and the CAP Operator version requirement note is now correctly using ### heading style matching the surrounding structure. No substantive issues found — the previously posted comment was a false positive and can be dismissed.

PR Bot Information

Version: 1.26.14

  • Correlation ID: deccaf20-76cf-11f1-89e8-4fd8b10d944e
  • LLM: anthropic--claude-4.6-sonnet
  • Event Trigger: pull_request.opened
  • File Content Strategy: Full file content

Comment thread CHANGELOG.md

@Pavan-SAP Pavan-SAP left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

@Pavan-SAP
Pavan-SAP merged commit ff2e9f0 into main Jul 3, 2026
6 of 7 checks passed
@Pavan-SAP
Pavan-SAP deleted the release-0.18.0 branch July 3, 2026 14:19
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.

2 participants