chore(main): release defender 0.4.4#18
Conversation
18c1d3b to
41c2406
Compare
There was a problem hiding this comment.
LGTM — automated Release Please version bump from 0.4.3 to 0.4.4.
Extended reasoning...
Overview
This is an automated Release Please PR that bumps the version from 0.4.3 to 0.4.4 across four files: .release-please-manifest.json, CHANGELOG.md, package-lock.json, and package.json. The only changes are version string replacements and a new changelog entry documenting the bug fix from PR #16.
Security risks
None. The changes are purely version bumps and changelog text — no code, configuration, or dependency changes.
Level of scrutiny
Minimal scrutiny needed. This is a fully mechanical, bot-generated release PR following the standard Release Please pattern. The version numbers are consistent across all four files and the changelog entry correctly references the merged commit.
Other factors
No bugs were found. No prior reviews or outstanding comments exist on this PR. The PR is labeled autorelease: pending which is the standard Release Please workflow label.
|
🤖 Created releases: 🌻 |
🤖 I have created a release beep boop
0.4.4 (2026-03-11)
Bug Fixes
This PR was generated with Release Please. See documentation.
Summary by cubic
Publish
@stackone/defenderv0.4.4 with a bug fix that makesToolSanitizationRulea public export and adds atier2Fieldsoption for finer control over sanitization. This satisfies ENG-12332 and unblocks consumers who need to import the rule and configure second‑tier fields.Written for commit 41c2406. Summary will update on new commits.