Create new Release Process Workflow

[JcMinarro]

🎯 Goal

The release process has been simplified and centralized on a common repository to be reused across our different products.
Complete: AND-493

The publish-new-version workflow automates the complete release process for Android repositories by:

1. Automatically bumping version (major/minor/patch) in the configuration file
2. Building and publishing to Maven Central
3. Creating GitHub releases
4. Automatically syncing branches (release → main → develop)

Improvements for repositories:

• Eliminates manual version and release management
• Reduces human errors in the publication process
• Keeps main branches automatically in sync

🎉 GIF

[Copilot]

Pull Request Overview

This pull request simplifies and centralizes the Android release process by removing the old publish workflow and introducing a new workflow that automates version bumping, building, and publishing.

• Removed the deprecated publish workflow (.github/workflows/publish.yml).
• Added the new publish-new-version workflow (.github/workflows/publish-new-version.yml) that leverages a centralized release process from our common repository.

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.

File	Description
.github/workflows/publish.yml	Removed the legacy publish workflow
.github/workflows/publish-new-version.yml	Introduces a new workflow to automate the release process with configurable inputs and remote workflow reuse

Comments suppressed due to low confidence (1)

.github/workflows/publish-new-version.yml:21

• Verify that setting 'use-official-plugin' to false is intentional, as this choice may affect the expected behavior of the version bump operation.

      use-official-plugin: false

[Copilot]

[nitpick] Consider adding inline comments to clarify the purpose of each workflow input (e.g. 'bump') for improved maintainability and easier onboarding of new developers.