Repository navigation
Automate versioned website releases and deployment - #2
Conversation
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 4e4d207cda
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| concurrency: | ||
| group: website-production | ||
| cancel-in-progress: false |
There was a problem hiding this comment.
With the workflow-level concurrency configured this way, cancel-in-progress: false protects only the running workflow; GitHub still cancels and replaces an existing pending run when another run joins the group (GitHub documentation). If an older deployment is running, a version-bump push is pending, and a subsequent package.json change keeps that new version unchanged, the latter run replaces the bump run and then release-gate.py emits release=false because its immediate parent already contains that version. The bumped version is therefore never deployed automatically; retain the full queue or make the gate decide against the last published/deployed version rather than only github.event.before.
Useful? React with 👍 / 👎.
The website only had a build check and was not deployed at the main domain. Add an independent, version-triggered release workflow that builds static assets, uploads them through a dedicated SSH account, atomically activates the verified release, checks its public revision, and publishes a versioned GitHub archive.
The production environment is configured for master-only deployment. Website versions remain independent of the app/server; merge this PR and manually run Website release on master to publish the initial website release. Future package.json version increases trigger deployment automatically.
Validation: seven focused automation tests, static build, Actionlint, and Node syntax checks passed. The upload, activation, and identical-archive retry were also verified with the dedicated account against Hetzner, including the public revision through Cloudflare. No app/server test suite was run.