Skip to content

chore(main): release 1.3.2#93

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

chore(main): release 1.3.2#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.3.2 (2026-05-25)

Bug Fixes

  • 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 from dfe38ce to a8bef9f Compare May 25, 2026 12:31
@github-actions github-actions Bot force-pushed the release-please--branches--main--components--postguard-business branch 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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

0 participants