Add version_level input to nightly builds workflow for flexible pre-release bumping

[Copilot]

The nightly build workflow hardcoded preminor when transitioning from a stable tag to a pre-release, making it impossible to trigger a premajor bump (e.g. v2.x.x → v3.0.0-0) via manual dispatch.

Changes

• workflow_dispatch input — adds a version_level choice (prepatch / preminor / premajor, default preminor) surfaced in the GitHub Actions UI when triggering manually
• RELEASE_TYPE logic — when the previous tag is stable, manual dispatches now use the selected version_level; scheduled runs retain the existing preminor fallback; the prerelease path (previous tag already pre-release) is untouched

inputs:
  version_level:
    description: "Version level for the pre-release bump when the previous release is stable (e.g. premajor → v3.0.0-0)"
    required: false
    default: "preminor"
    type: choice
    options:
      - prepatch
      - preminor
      - premajor

if ("${{ github.event_name }}" -eq "workflow_dispatch") {
    $RELEASE_TYPE = "${{ inputs.version_level }}"  # e.g. premajor → v3.0.0-0
} else {
    $RELEASE_TYPE = "preminor"                     # scheduled nightly unchanged
}

[Copilot]

Pull request overview

This PR updates the GitFlow nightly builds GitHub Actions workflow to allow manually dispatched nightly builds to choose the SemVer pre-release bump level (prepatch/preminor/premajor) when the previous tag is stable, while keeping scheduled nightly behavior unchanged.

Changes:

• Added a workflow_dispatch input version_level (choice: prepatch / preminor / premajor, default preminor).
• Updated the stable-tag path to use the selected version_level for manual dispatches, and keep preminor for scheduled runs.

[github-actions]

❌MegaLinter analysis: Error

Descriptor	Linter	Files	Fixed	Errors	Warnings	Elapsed time
✅ COPYPASTE	jscpd	yes		no	no	2.64s
⚠️ MARKDOWN	markdownlint	1	1	3	0	1.07s
✅ MARKDOWN	markdown-table-formatter	1	1	0	0	0.39s
✅ POWERSHELL	powershell	7		0	0	24.65s
✅ POWERSHELL	powershell_formatter	7		0	0	14.09s
⚠️ REPOSITORY	checkov	yes		4	no	28.61s
⚠️ REPOSITORY	devskim	yes		1	8	2.87s
✅ REPOSITORY	dustilock	yes		no	no	0.02s
✅ REPOSITORY	gitleaks	yes		no	no	1.29s
✅ REPOSITORY	git_diff	yes		no	no	0.02s
✅ REPOSITORY	grype	yes		no	no	54.85s
❌ REPOSITORY	kingfisher	yes		1	no	7.01s
❌ REPOSITORY	osv-scanner	yes		1	no	0.14s
✅ REPOSITORY	secretlint	yes		no	no	0.98s
✅ REPOSITORY	syft	yes		no	no	2.07s
✅ REPOSITORY	trivy	yes		no	no	10.05s
✅ REPOSITORY	trivy-sbom	yes		no	no	0.25s
✅ REPOSITORY	trufflehog	yes		no	no	5.13s
⚠️ SPELL	cspell	9		22	0	7.01s
✅ SPELL	lychee	1		0	0	2.19s

Detailed Issues

❌ REPOSITORY / kingfisher - 1 error

Linter output file not found

❌ REPOSITORY / osv-scanner - 1 error

Linter output file not found

⚠️ REPOSITORY / checkov - 4 errors

Linter output file not found

⚠️ SPELL / cspell - 22 errors

Linter output file not found

⚠️ REPOSITORY / devskim - 1 error

Linter output file not found

⚠️ MARKDOWN / markdownlint - 3 errors

Linter output file not found

Notices

📣 MegaLinter 9.5.0 is out! Discover the new features and security recommendations in the release announcement. (Skip this info by defining SECURITY_SUGGESTIONS: false)

See detailed reports in MegaLinter artifacts
Set VALIDATE_ALL_CODEBASE: true in mega-linter.yml to validate all sources, not only the diff

Show us your support by starring ⭐ the repository