chore(release): realign develop with main after the #670 promotion - #671
Merged
Conversation
chore(release): promote develop to main Closes the three gaps ADR-0119 declared — the auth guard that failed open on an unset NODE_ENV, the three services that defaulted it to development, and the bare helmet() that promised header values it did not deliver — plus the OPA binary the deployed runtime could not execute, the eleven audited and signed ADRs, and two guards that could report a pass over an empty scan.
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
📊 Bilingual Coverage ImpactPR Changes
Repository Coverage
✅ Good: All EN changes have ES counterparts. Generated by GitHub Actions |
This was referenced Sep 1, 2026
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
1 participant
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.
Pull Request Summary
Sync-back after the #670 promotion. Zero file changes —
git diff develop..mainis empty. The single commit is the merge node GitHub created onmainwhen #670 landed.Without this,
developsits one commit behindmainand every branch cut from it starts behind too. That is the driftdb596547("realign develop with main after the #637 promotion") already had to repair once, and this is the same step at the same point in the cycle — it is phase 2 of thepre-pushrelease macro, done as a PR becausedevelopis protected.Before you submit
db596547.Linked ADRs / Issues
db596547, the same realignment after chore(repo): pin Node at the root, and drop a Sponsor button that leads nowhere #637What the reviewer should know
Nothing in this PR changes a single line. If the checks take issue with it, the finding belongs to the branch state and not to this change — which is exactly the case the PR template describes as "ours, not yours".
🤖 Generated with Claude Code