Update starter deploy version in pom.xml

[hmoreras]

closes #35097

Summary

Updates the empty starter deploy version from empty_20260225 to empty_20260331 in parent/pom.xml.

This change is part of the Modernization Team effort to ensure fresh DotCMS installs include the updated starter data that ships with the correct Plugins portlet layout configuration. It is a follow-up to the work done in #35097, which fixed the root cause (missing plugins portlet in fresh-install layouts), and ensures the bundled empty starter reflects those fixes so new installs are no longer affected.

Related task: #35097

Proposed Changes

• Bump starter.deploy.version from empty_20260225 to empty_20260331 in parent/pom.xml

Checklist

• Tests — no code logic changed; starter artifact version bump only
• Translations — N/A
• Security Implications Contemplated — none; this is a version string update

Additional Info

The empty starter at version empty_20260331 includes the updated cms_layouts_portlets data that maps the Plugins portlet (plugins) correctly, so fresh installs will have the sidebar entry working out of the box without needing the upgrade task Task260320AddPluginsPortletToMenu.

[claude]

Claude finished @hmoreras's task in 40s —— View job

---

Rollback Safety Analysis

• Read rollback-unsafe categories reference
• Get full PR diff
• Analyze diff against all unsafe categories
• Apply appropriate label

---

Result: ✅ Safe to Rollback

The only change is in parent/pom.xml:

-<starter.deploy.version>empty_20260225</starter.deploy.version>
+<starter.deploy.version>empty_20260331</starter.deploy.version>

This updates a Maven property that controls which starter .zip version gets deployed. It does not touch any of the rollback-unsafe categories:

• No database migrations (no runonce tasks, no DDL)
• No Elasticsearch mapping changes
• No content JSON model version bump
• No API contract changes
• No OSGi interface changes
• No push publishing bundle format changes

Rolling back would simply revert to the previous starter version (empty_20260225), which is safe.

Label added: AI: Safe To Rollback

[github-actions]

❌ Issue Linking Required

This PR could not be linked to an issue. All PRs must be linked to an issue for tracking purposes.

How to fix this:

Option 1: Add keyword to PR body (Recommended - auto-removes this comment)
Edit this PR description and add one of these lines:

• This PR fixes #123 or Fixes: #123

• This PR closes #123 or Closes: #123

• This PR resolves #123 or Resolves: #123

• Other supported keywords: fix, fixed, close, closed, resolve, resolved
  Option 2: Link via GitHub UI (Note: won't clear the failed check)

1. Go to the PR → Development section (right sidebar)

2. Click "Link issue" and select an existing issue

3. Push a new commit or re-run the workflow to clear the failed check
   Option 3: Use branch naming
   Create a new branch with one of these patterns:

• 123-feature-description (number at start)

• issue-123-feature-description (issue-number at start)

• feature-issue-123 (issue-number anywhere)

Why is this required?

Issue linking ensures proper tracking, documentation, and helps maintain project history. It connects your code changes to the problem they solve.---

This comment was automatically generated by the issue linking workflow

[wezell]

If tests pass...