v16.18.1

frappe/hrmsv16.18.1Sep 9, 2026by frappe-pr-bot

AI Summary

This release improves telemetry handling and updates usage tracking to use the HRMS-specific persona. It also enhances security by restricting record modifications to POST requests.

Key Highlights

Improves telemetry event handling to send data only when enabled.
Updates usage tracking to identify HRMS-specific users.
Restricts create/update/delete requests for sensitive records to POST only.

Full Release Notes

## Bug Fixes
* Improves telemetry event handling so usage data is sent only when telemetry is enabled. (https://github.com/frappe/hrms/pull/5107)
* Updates usage tracking to identify HRMS users with the HRMS-specific persona instead of the ERPNext persona. (https://github.com/frappe/hrms/pull/5216)

## Other Changes
* Restricts requests that create, update, or delete records across roster, attendance, leave, payroll, and recruitment to POST requests instead of allowing GET requests. (https://github.com/frappe/hrms/pull/5229)

**Authors**: @deepeshgarg007, @iamkhanraheel

<details>
<summary>AI content</summary>

 For these release notes, we used an LLM (OpenAI gpt-5.6-luna) 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](https://github.com/barredterra/pretty_release_notes). 

Changes with the following labels were excluded:
- skip-release-notes

Changes with the following types were excluded:
- refactor
 - chore
 - style
 - docs
 - test
 - build
 - ci

</details>