Skip to content

chore: sync main (v0.27.0) back to development#1390

Merged
tyhonchik merged 9 commits into
developmentfrom
main
Jun 10, 2026
Merged

chore: sync main (v0.27.0) back to development#1390
tyhonchik merged 9 commits into
developmentfrom
main

Conversation

@arabot-1

Copy link
Copy Markdown
Contributor

Auto-opened when release/0.27.0 merged into main. Carries the merged changes (incl. CHANGELOG.md / version) back into development.

tyhonchik and others added 9 commits June 8, 2026 15:16
main is the release PR base. Seed the workflows GitHub resolves from the base
branch on release/hotfix PRs, plus the merge gate:
- release-pr (Approve #1: deploy to staging), deploy-reusable (the gated deploy)
- release-finalize (tags vX.Y.Z + GitHub Release), release-backmerge (main->development)
- release-cancel, release-hotfix-cherrypick
- CODEOWNERS (* @aragon/app-team) = Approve #2
- RELEASE.md runbook

The development-side workflows (release-start, app-production, hotfix-start,
rollback, develop-deploy) and the unit-dep/integration-test trigger trims arrive
on main automatically with the first release merge (development -> main).
ci(release): seed main with PR-gated release flow (PR-base side)
# Conflicts:
#	.github/workflows/deploy-reusable.yml
#	.github/workflows/release-pr.yml
- include .github/workflows/scripts in notify jobs' sparse-checkout
  (fixes MODULE_NOT_FOUND when slack-notify runs slackNotify.js)
- reword the deploy-result Slack message to state the NEXT action
  (staging -> review & merge, prod -> done, failure -> re-run/fix)
  instead of appending the raw job result word
- link Linear issues in the release summary when LINEAR_API_TOKEN is
  set (optional GitHub Actions secret; Linear silently skipped and PR
  links kept when the token is absent)
refactor(logMetadata): update block number comparison and restrict test suite execution
@arabot-1 arabot-1 requested a review from a team as a code owner June 10, 2026 10:23
@tyhonchik tyhonchik merged commit 6f3f256 into development Jun 10, 2026
15 of 17 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants