Skip to content

feat(sdk): automate MinSdkVersion.VALUE maintenance via release pipeline (#36698) - #521

Closed
KevinDavilaDotCMS wants to merge 6 commits into
mainfrom
36698-automate-min-sdk-version-bump
Closed

feat(sdk): automate MinSdkVersion.VALUE maintenance via release pipeline (#36698)#521
KevinDavilaDotCMS wants to merge 6 commits into
mainfrom
36698-automate-min-sdk-version-bump

Conversation

@KevinDavilaDotCMS

Copy link
Copy Markdown
Member

Test implementation for dotCMS#36698 — see PR description commits. Testing in this fork before porting to the real repo.

KevinDavilaDotCMS and others added 6 commits July 23, 2026 14:05
…ons are accessible. This addresses a gap in the runner's workspace setup, improving the reliability of subsequent steps.
…fallback

Mirrors the fixes already verified and pushed on dotCMS/core PR dotCMS#36722:
continue-on-error on the SDK next-tag publish step (with the failure Slack
step checking step outcome directly, not job-level failure()), and a
fallback for the version string when the compute-version step itself fails.
…CMS/core main

This fork predates the dotCMS#36609/dotCMS#36678 merge and was missing MinSdkVersion.java,
SdkVersionWebInterceptor.java, sdk-compatibility.ts, and related files entirely.
Synced verbatim from upstream/main so the upcoming dotCMS#36698 work (automating
MinSdkVersion.VALUE maintenance) can be tested against an accurate baseline.
…ine (dotCMS#36698)

- New bump_min_sdk_version input on cicd_6-release.yml
- New verify-branch validation: fails the release if a merged PR carries
  an SDK-breaking-change label but the input was left false (checks for
  a stale unmerged bump PR too, non-fatally)
- New bump-min-sdk-version job, gated on release-prepare+build+deployment
  succeeding, that opens a PR against main (never a direct push) bumping
  MinSdkVersion.VALUE and notifies Slack for human review. Idempotent:
  no-ops if main already has the value, dedupes an already-open PR.
- New ai_claude-sdk-breaking-change.yml workflow mirroring
  ai_claude-rollback-safety.yml, labeling PRs AI: SDK Breaking Change /
  AI: Not SDK Breaking Change against a new reference doc
- New docs/core/SDK_BREAKING_CHANGE_CATEGORIES.md grounded in actual
  @dotcms/client code (GraphQL page API, REST nav/content responses,
  UVE postMessage protocol, the compatibility headers themselves)
- Updated MinSdkVersion.java Javadoc to describe the new automated flow
@KevinDavilaDotCMS
KevinDavilaDotCMS requested a review from a team as a code owner July 25, 2026 04:57
@KevinDavilaDotCMS

Copy link
Copy Markdown
Member Author

Superseded by a clean rebase onto origin/main (avoided resurrecting an unrelated stale conflict in internal.ts from old fork history).

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