Skip to content

chore(main): release 1.4.0 - #93

Open
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--postguard-business
Open

chore(main): release 1.4.0#93
github-actions[bot] wants to merge 1 commit into
mainfrom
release-please--branches--main--components--postguard-business

Conversation

@github-actions

@github-actions github-actions Bot commented May 25, 2026

Copy link
Copy Markdown
Contributor

🤖 I have created a release beep boop

1.4.0 (2026-07-23)

Features

  • add /readyz readiness probe with database check (#113) (36b8dad)
  • add structured logging with request correlation (#115) (4290278)
  • configure explicit Postgres connection pool and timeouts (#114) (7d638cb)
  • validate environment variables at startup with a typed config (#121) (e7bc114)

Bug Fixes

  • a11y: add id=main-content to marketing layout main (#94) (096beaa), closes #76
  • auth: harden post-login redirect validation (#125) (259c5ff)
  • csp: allow Yivi frontend traffic and bundle icons locally (#133) (fcb7405)
  • docker: pass DATABASE_URL as a BuildKit secret in the build stage (#128) (4130229)
  • enforce Content-Security-Policy instead of report-only mode (#126) (0231588), closes #124
  • irma: harden IRMA proxy request handling (#130) (c36994f)
  • log DNS resolver errors and differentiate by code (#90) (d7023c4), closes #88
  • reject unknown fieldName in approveChangeRequest (#91) (3d9e41a), closes #87
  • unify duplicate-key error detection into single helper (#92) (f1bfad2), closes #89

This PR was generated with Release Please. See documentation.

@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--postguard-business branch 2 times, most recently from a8bef9f to 7fba8c2 Compare May 25, 2026 12:33

@dobby-coder dobby-coder Bot left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code review

release-please 1.3.1 → 1.3.2. CHANGELOG entry + version bumped in package.json and both locations in package-lock.json (lockfileVersion 3). The two fix: commits since v1.3.1 (#90, #92) are the changelog entries; the 4 chore: commits between releases are correctly excluded. Patch bump is correct semver for two fixes.

Rule compliance

64 rule/note checks (61 org rules + 3 repo-specific notes) ran in parallel against the diff. No genuine violations — the rules that flagged this PR did so on misapplied scope (release-please CHANGELOG edits are not typo-sweep edits; consolidation-PR closing-keyword rule doesn't apply to release-please bodies; the FIX-stage skip rule doesn't apply to the REVIEW stage). No line-level findings.

@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--postguard-business branch from 7fba8c2 to c93efd5 Compare July 1, 2026 11:09
@github-actions github-actions Bot changed the title chore(main): release 1.3.2 chore(main): release 1.4.0 Jul 1, 2026
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--postguard-business branch from c93efd5 to e67d96a Compare July 1, 2026 14:12
@github-actions
github-actions Bot requested a review from rubenhensen as a code owner July 1, 2026 14:12
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--postguard-business branch 7 times, most recently from 50816c8 to 50748f9 Compare July 6, 2026 13:30
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--postguard-business branch 2 times, most recently from fd22f5c to 6e76f65 Compare July 15, 2026 07:23
@rubenhensen

Copy link
Copy Markdown
Contributor

/dobby fix ci

@dobby-coder

dobby-coder Bot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Hey @rubenhensen, on it — I'll dig into why CI is failing on PR #93 and push a fix directly to this PR.

@dobby-coder

dobby-coder Bot commented Jul 23, 2026

Copy link
Copy Markdown
Contributor

Fixed! I reviewed and approved #132, which excludes the release-please CHANGELOG.md from the prettier check, and took it out of draft. Once that merges, this release PR will get rebuilt on top of main and the Lint job should go green.

rubenhensen pushed a commit that referenced this pull request Jul 23, 2026
release-please generates CHANGELOG.md with asterisk bullets and blank lines
around lists, a Markdown style prettier rewrites. Since #69 enforced
`prettier --check .` in the Lint job without excluding the file, every
release PR fails lint on the regenerated CHANGELOG (e.g. #93 for 1.4.0).

CHANGELOG.md is owned by release-please, so exclude it from prettier.

Co-authored-by: dobby-yivi-agent[bot] <275734547+dobby-yivi-agent[bot]@users.noreply.github.com>
Co-authored-by: Claude Opus 4.8 <noreply@anthropic.com>
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--postguard-business branch from 6e76f65 to a3cca24 Compare July 23, 2026 12:12
@github-actions
github-actions Bot force-pushed the release-please--branches--main--components--postguard-business branch from a3cca24 to d9b0dbc Compare July 23, 2026 13:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment