SLCORE-1785 Create a common release automation workflow for IDE Experience

[Krosovok]

SLCORE-1785

Create a base workflow for IDE Experience squad

[sonarqubecloud]

SonarQube reviewer guide

Summary: Adds reusable GitHub workflow for automated IDE release process with Jira integration.

Review Focus: Verify job dependencies and permissions are correctly configured. Pay attention to the complex conditional logic in the summary step and ensure all required inputs are properly validated.

Start review at: .github/workflows/ide-automated-release.yml (lines 1-50). This section defines the workflow interface and inputs that drive the entire automation - any issues here will cascade through all subsequent jobs.

💬 Please send your feedback

Quality Gate passed

Issues
0 New issues
1 Accepted issue

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[damien-urruty-sonarsource]

A first round of comments

[damien-urruty-sonarsource]

@Krosovok Something I forgot to mention, this common action lives in a repo that is not ours, have you checked with the codeowners that this is fine? Personally I think it's OK. We could also create a separate repo if needed

[Krosovok]

@Krosovok Something I forgot to mention, this common action lives in a repo that is not ours, have you checked with the codeowners that this is fine? Personally I think it's OK. We could also create a separate repo if needed

I will double check.

[Krosovok]

@vnaskos-sonar can you please take a look too?

[yasen-pavlov-sonarsource]

🚀

[sonarqubecloud]

SonarQube reviewer guide

Important

We are currently testing different models for AI Summary.
Please give us your feedback by filling this form.

Model A:

Summary: Adds reusable GitHub Actions workflow for automated IDE product releases with Jira integration.

Review Focus:

• Job dependency chain and error handling across 6 sequential jobs
• Permissions scope for each job (especially write permissions to contents/PRs)
• Conditional logic in summarize_release job that always runs regardless of failures
• Test mode behavior (draft releases, sandbox Jira) controlled by is-test-run flag

Start review at: .github/workflows/ide-automated-release.yml lines 51-176 (job definitions). This contains the core orchestration logic that coordinates version management, Jira ticket creation, GitHub releases, and status transitions—understanding this flow is critical before examining individual step implementations.

Model B:

Summary: Add a reusable GitHub Actions workflow for automated IDE release management that orchestrates pre-release checks, version preparation, GitHub/Jira release creation, and ticket management.

Review Focus: Verify the job dependency chain is correct (each job properly awaits its dependencies), ensure all required permissions are minimal but sufficient, confirm the TODO comment regarding PM email from vault is tracked, and validate the hardcoded due date calculation (2 days) meets business requirements.

Start review at: .github/workflows/ide-automated-release.yml - the entire workflow file. This is the only file changed, so understanding the complete orchestration flow, job dependencies, input validation, and permission model is critical for release reliability.

See all code changes, issues, and quality metrics in one place.

Quality Gate passed

Issues
0 New issues
1 Accepted issue

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud