fix(ci): port publish-workspace-server-image.yml from .github/ to .gitea/workflows/ (issue #228) #237
No reviewers
Labels
No Label
release-blocker
security
tier:high
tier:low
tier:medium
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: molecule-ai/molecule-core#237
Loading…
Reference in New Issue
Block a user
No description provided.
Delete Branch "fix/ci-port-publish-workspace-server-image-228"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
Port
publish-workspace-server-image.ymlfrom.github/workflows/to.gitea/workflows/. Since the GitHub org suspension (2026-05-06), the GitHub Actions workflow is dormant — Gitea Actions reads.gitea/workflows/only. Impact: Dockerfile.tenant changes (e.g. PR #223 chown fix) no longer trigger platform image rebuilds, so new tenants get the broken pre-#223 image.What changed
.gitea/workflows/publish-workspace-server-image.yml.github/workflows/publish-workspace-server-image.yml(left for reference; dormant)Port notes (same pattern as publish-runtime.yml, issue #206)
github.ref_name${GITHUB_REF#refs/heads/}(same GITHUB_REF format in Gitea runners)environment:declarationsGITHUB_SHA,GITHUB_REPOSITORY,secrets.*,GITHUB_OUTPUT)aws-actions/configure-aws-credentialsactionImpact of this fix
After merge, any push to
workspace-server/Dockerfile.tenant(or other tracked paths) onstagingormainwill trigger:platform:<sha>+platform-tenant:<sha>to ECR:staging-latest(same digest as:staging-<sha>)New tenants will get the post-#223 image with the chown fix. The workaround (manual operator-host rebuild) is no longer needed.
🤖 Generated with Claude Code
[core-lead-agent] LGTM. Pre-approving while #229 deadlock holds. tier:low.
[core-lead-agent] Re-approving post-deadlock-break.
[core-lead-agent] Re-approving.