[davseve]

Summary

Lets the release-tag-creation action release Elementor Pro as well as Core, selected by one new input.

• New input plugin: core | pro (default core). It replaces plugin_file, version_constant, update_readme and update_elementor_tested_up_to. The mapping is in plugin-config.ts:

  plugin	Plugin file	Version constant	readme.txt	"Elementor tested up to"
  core	elementor.php	ELEMENTOR_VERSION	updated	not touched
  pro	elementor-pro.php	ELEMENTOR_PRO_VERSION	not touched	set from Core release/<channel>

• Pro "Elementor tested up to". The action fetches elementor.php from Core's matching release/<channel> branch, reads its Version: and writes it as X.Y.Z, with any beta suffix removed (elementor-tested-up-to.ts).

• Shared utils (version-files.ts). patchPhpVersion takes the constant to update, typed as VersionConstant (ELEMENTOR_VERSION or ELEMENTOR_PRO_VERSION). A new patchPhpHeaderField updates any * Field: value header line. Both now throw if the expected line is missing, instead of silently committing an unchanged file.

• The commit step and the job summary now read plugin_file and update_readme from the version-update step's outputs, not from inputs.

Compatibility

• Core: no change needed. Core's workflow doesn't pass the old inputs, and plugin defaults to core, which matches the old defaults (elementor.php, ELEMENTOR_VERSION, readme updated).
• Pro: must pass plugin: pro. If it's forgotten, the run fails reading elementor.php, which doesn't exist in the Pro repo, before anything is committed or tagged.

Testing

• vitest in actions/release-tag-creation and packages/editor-github-actions-utils passes.
• tsc and eslint are clean.
• Not yet run end to end in a workflow.

✨ PR Description

1. Problem & Context

Extends the release-tag-creation action to support Elementor Pro ED-25747. This enables automated version bumping for Pro and synchronizes the "Elementor tested up to" header with the latest Core release version.

2. What Changed (Where)

File	Change
elementor-tested-up-to.ts	New logic to fetch and sanitize Core versions via GitHub API.
plugin-config.ts	Configuration mapping for 'core' vs 'pro' plugins.
update-version-files.ts	Refactored run() to handle dynamic plugin config and header patching.
version-files.ts	Generic PHP header and constant patching utilities in @elementor/editor-github-actions-utils.
action.yml	Added plugin and github_token inputs; updated outputs and commit logic.
*.test.ts	Comprehensive test coverage for new utilities and the main execution loop.

3. How It Works

The action now accepts a plugin input ('core' or 'pro'). For 'pro', it fetches the current version of the specified Core channel (stable/beta) using the GitHub Contents API, strips pre-release tags via semver, and patches both the ELEMENTOR_PRO_VERSION constant and the "Elementor tested up to" header in elementor-pro.php.

4. Risks

API rate limits on Core version fetching; mitigated by the optional github_token input.

Generated by LinearB AI and added by gitStream.
_{AI-generated content may contain inaccuracies. Please verify before using.
💡 Tip: You can customize your AI Description using Guidelines Learn how}

[wiz-9a149474ff]

Wiz Scan Summary

Scanner	Findings
Vulnerabilities	-
Sensitive Data	-
Secrets	-
IaC Misconfigurations	-
SAST Findings	4
Software Management Findings	-
Total	4

View scan details in Wiz

To detect these findings earlier in the dev lifecycle, try the Wiz Code extension for VS Code, JetBrains, or Visual Studio.

[Ntnelbaba]

Review

Re-checked at df341e32 (not from zero).

Still open:

1. Medium — fetchCoreReleaseVersion raw.githubusercontent fetch has no cache-bust (inline).
2. Low — plugin_file / update_readme outputs are set before the PHP write succeeds (inline).
3. Low — no unit/integration test for run() in update-version-files.ts.

plugin default core, plugin-config mapping, and throw-on-missing header/define behavior look good.

Comment-only; not approving.

[Ntnelbaba]

And if the value is "koko"?