Repository navigation
fix(ci): build/prod updates with each PlaceOS release, and stops stalling on e2e timeouts - #343
Merged
Merged
Conversation
build/prod had not updated since July. The release/* branches ran e2e on every browser, which timed out at 25 minutes and skipped the deploy. The PlaceOS changelog listed backoffice changes that installs did not have. PlaceOS/PlaceOS now sends a placeos-release event after each release. RELEASE tags the backoffice commit that the version pins, tests it, and publishes it to build/prod. CI e2e runs Chromium only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
![github-advanced-security[bot]](https://avatars.githubusercontent.com/in/57789?s=60&v=4){kind=small}
…mmits CodeQL found that a RELEASE run could check out any commit and write to the develop cache through the Nx cache step. The Nx cache step is removed, and RELEASE stops when the pinned commit is not on develop. The workflows also set explicit token permissions. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.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.
PlaceOS installs load backoffice from
build/prod, butbuild/prodhas not changed since 2026-07-08. Therelease/2026-08-20andrelease/2026-10-08builds ran e2e on every browser, hit the 25-minute timeout, and skipped the deploy. The PlaceOS changelogs for 2.2610 and 2.2611 also list backoffice changes that installs do not have, because PlaceOS records thedevelopcommit that itsinterfaces/backofficesubmodule pins.Now each PlaceOS release ships the backoffice commit that it pins:
placeos-releaseevent after a release. That change is in a separate PR in PlaceOS/PlaceOS.RELEASEworkflow looks up the commit that the version pins, and tags itv<version>(for examplev2.2611.6). The version info shows the tag.build/prod.CHANGELOG.mdtodevelop. A rollback does not overwrite a newer changelog.You can also run
RELEASEby hand with a version, to retry or to roll back.Other changes:
BUILDnow builds onlydeveloptobuild/dev. The build steps are inbuild-app.yml, which both workflows use.update-changelog.yml. It never committed:git diff --quietdoes not see an untrackedCHANGELOG.md.release/**andrc/**triggers. Thercpath used astagingconfiguration thatproject.jsondoes not have.docs/releases.mdexplains the process.Tested locally: for
2.2611.6, the lookup finds484102f, which is the pinned commit. The lookup rejects bad and unknown versions. The tag shows asv2.2611.6insrc/env/version.ts, and git-cliff writes a## [2.2611.6]heading. actionlint reports no new issues.After merge: run
RELEASEwith2.2611.6to bringbuild/produp to date.Created with Claude Opus 5.5 in Claude Code.
🤖 Generated with Claude Code