This release fixes issues for SREs watching stability and regressions.
✓ No known CVEs patched in this version
Topics
+10 more
ReleasePort's take
Light signalERPNext v16.18.2 fixes a bug where stock transactions incorrectly calculated batch quantities using the current time instead of the entered posting date, restoring accurate batch tracking.
Why it matters: Stock batch quantities now calculate correctly using entered posting dates. Test in dev before production deployment if your inventory operations depend on date-based transaction accuracy.
Summary
AI summaryFixed stock transactions to use entered posting date and time, preventing incorrect batch quantities.
Changes in this release
| Type | Severity | Summary | CVE |
|---|---|---|---|
| Bugfix | Medium |
Records stock transactions using entered posting date/time, not current time, fixing batch quantities Records stock transactions using entered posting date/time, not current time, fixing batch quantities Source: llm_adapter@2026-05-21 Confidence: high |
— |
Full changelog
Bug Fixes
- Records stock transactions using the entered Posting Date and Posting Time rather than the current time, preventing incorrect batch quantities. (https://github.com/frappe/erpnext/pull/54931)
Authors: @rohitwaghchaure
Reviewers: @rohitwaghchaure
For these release notes, we used an LLM (OpenAI o3) to review and summarise the code changes, along with the associated issue and PR descriptions. It may contain typical errors and inaccuracies. You can read the prompt here.
Changes with the following labels were excluded:
- skip-release-notes
Changes with the following types were excluded:
- ci
- chore
- style
- docs
- refactor
- build
- test
Weekly OSS security release digest.
The CVE patches and breaking changes that affected production tools this week. One email, every Sunday.
No spam, unsubscribe anytime.
Share this release
Beta — feedback welcome: [email protected]