[pull] main from activepieces:main#1199
Merged
Conversation
Fix `Check for breaking migrations` step failing with `Cannot find module '@activepieces/server-utils'` — add a `bun run --cwd packages/server/utils build` step so tsx can resolve the re-export introduced in #12532. Move the migration check to run before any publish side effects (release-drafter, git tag, docker promote) so a future script failure no longer leaves a half-published release. Replace the tag-exists guard with a digest comparison so reruns against an already-published version succeed when the release-candidate image is unchanged and still fail on an accidental overwrite with different content.
Releases for self-hosted are cut via release-self-hosted.yml (manually dispatched with an explicit tag), so the weekly automatic release-candidate promotion is no longer needed and its migration-check step has been flaky. Drop the file rather than keep maintaining it alongside a superseded flow.
v5 runs on Node.js 20 (deprecated) and silently swallows transient GitHub GraphQL 502s — the step logs ##[error] but exits 0, so the workflow shows green while no release is actually created (seen on 0.82.0-rc.1 and 0.82.0 runs). v7 runs on Node.js 24 and surfaces failures properly.
Bring back the weekly release promotion flow that was removed in 5e3a034, with release-drafter bumped to v7 to match the fix already applied in release-self-hosted.yml (v5 swallowed GraphQL 502s and silently exited 0). The weekly cadence and digest-match guard against release-candidate still apply.
Adds a deploy-canary job that runs on the scheduled Sunday promotion and pushes release-candidate to the canary app and worker kamal configs before promote-to-production takes over. Hotfix (workflow_dispatch/cloud-hotfix) still bypasses canary as documented on its input description.
Replace the inline kamal-based canary deploy in continuous-delivery-cloud.yml with a reusable workflow_call to continuous-delivery-canary.yml so the Sunday promotion reuses the same build + migration-check + deploy pipeline that runs daily. Update the release playbooks and release-cycle docs to reflect the refreshed-canary step before prod promotion.
…ivepieces into release/v0.82.0
release-rc.yml is redundant with release-self-hosted.yml, which already accepts an explicit tag input, handles -rc tags (skips 'latest' when the tag contains -rc), creates the git tag, and runs release-drafter. release-rc.yml only built images — no tag, no changelog — and the cloud RC image it produced is already covered by the staging → release-candidate pipeline. Also drops the now-unused rcVersion field from package.json, which was only read by this workflow.
Address PR #12757 review: - Drop the duplicate `Check for breaking migrations` step — GitHub Actions rejects workflows with repeated step ids, so the weekly release would fail validation before running (P0). - Capture the raw output of `docker buildx imagetools inspect` before hashing. Piping a failed inspect straight into sha256sum produced the SHA-256 of the empty string, which never matched the zero-length guard, so first-time releases would always trip the "refusing to overwrite" branch (P1).
… members who are not admins (#12789)
Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Co-authored-by: greptile-apps[bot] <165735046+greptile-apps[bot]@users.noreply.github.com>
…ect options (#12964) Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com> Co-authored-by: David Anyatonwu <51977119+onyedikachi-david@users.noreply.github.com> Co-authored-by: David Anyatonwu <davidanyatonwu@gmail.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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
8 participants
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.
See Commits and Changes for more details.
Created by
pull[bot] (v2.0.0-alpha.4)
Can you help keep this open source service alive? 💖 Please sponsor : )