feat: shared nightly release actions [ED-25507] - #53
Open
Ntnelbaba wants to merge 3 commits into
Open
Conversation
Co-authored-by: Cursor <cursoragent@cursor.com>
Co-authored-by: Cursor <cursoragent@cursor.com>
…507] Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds two composite actions backing the rolling nightly release for Elementor and Elementor Pro.
publish-nightly-release— copies the built zip to a stable nightly filename, force-moves the nightly tag to the merge commit, and writes release notes. The tag has to be moved here becausesoftprops/action-gh-releasenever repoints an existing tag. Consumed by both plugin repos; the only difference between them was the plugin slug, now an input.resolve-core-nightly— resolves the Core nightly release for a branch and optionally downloads the zip. Replaces per-repo logic in Pro that paged the releases API and parsed tag names.The tag rule (
main→nightly, any other branch →<version>-nightly) lives once inpublish-nightly-release/nightly-tag.shand is sourced by both actions, so producer and consumer cannot drift.Jira
https://elementor.atlassian.net/browse/ED-25507
Made with Cursor
✨ PR Description
1. Problem & Context
Standardizes nightly release tagging across repositories to prevent naming drift between the producer (
publish-nightly-release) and consumer (resolve-core-nightly). Addresses ED-25507.2. What Changed (Where)
nightly-tag.shpublish-nightly-release.sh/action.ymlresolve-core-nightly.sh/action.ymlpackage.jsonand download assets.README.md(both)3. How It Works
nightly-tag.shacts as the single source of truth: it returnsnightlyfor the main branch and<version>-nightlyfor others. The publish action uses this to force-push tags to a specific commit, while the resolve action uses it to fetch the correct nightly zip from the Core API.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