What is update-change-log?

A command for updating a Python package's change log and version number from recent Git commits. A change log is a file that records releases and changes, while a version number identifies a package revision.

Use it when preparing a d365fo-client release: inspect version files, review commits, update CHANGELOG.md, and increment the version in pyproject.toml.

It turns recent development history into release notes and helps keep the package version aligned with its documented changes. It also accounts for the package's command-line and MCP entry points.

How mafzaal/d365fo-client configures GitHub Copilot

Reuse

Borrowing it

Nothing to install: this file belongs to mafzaal/d365fo-client. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.

Copy the file

curl -O https://raw.githubusercontent.com/mafzaal/d365fo-client/main/.github/prompts/update-change-log.prompt.md

Clone the repo

git clone --depth 1 https://github.com/mafzaal/d365fo-client

Made for: GitHub Copilot.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/commands/mafzaal/d365fo-client/update-change-log/github.svg)](https://agentmods.dev/commands/mafzaal/d365fo-client/update-change-log)

Your own site

<a href="https://agentmods.dev/commands/mafzaal/d365fo-client/update-change-log"><img src="https://agentmods.dev/badge/commands/mafzaal/d365fo-client/update-change-log/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/commands/mafzaal/d365fo-client/update-change-log"><img src="https://agentmods.dev/badge/commands/mafzaal/d365fo-client/update-change-log.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 24 Only the description is in the session, so the agent can decide to use it. The body loads when it is invoked.

When invoked 1,621 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe.

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00024	$0.01621
Opus 5.5	$0.00010	$0.00648
Sonnet 5.5	$0.00005	$0.00324
Haiku 4.5	$0.00002	$0.00162

Measured 1mo ago against content hash c8ab9865286b, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

update-change-log scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

.github/prompts/update-change-log.prompt.md · 151 lines

How it starts

The opening of the file, as written. The whole thing — 151 lines — stays where its author put it; the contents beside it link to each section on GitHub.

AI Assistant Instructions: Update d365fo-client Changelog and Version Numbers

Overview

These instructions guide an AI assistant to systematically update the d365fo-client project's CHANGELOG.md and increment version numbers in pyproject.toml based on git commit history. This is a comprehensive Python package for Microsoft Dynamics 365 Finance & Operations (D365 F&O) that provides OData client library, CLI application, and MCP server functionality.

Process Steps

1. Examine Current Version Files

Read pyproject.toml to identify current version number (look for version = "X.Y.Z" around line 3)
Read CHANGELOG.md to understand the last documented version and changes
Note: This project uses uv for package management and has two main entry points:
- CLI: d365fo-client command
- MCP Server: d365fo-mcp-server command

2. Analyze Git History

Use git log --oneline --since="YYYY-MM-DD" --pretty=format:"%h %s" --reverse to get commits since last changelog entry
Use git log --since="YYYY-MM-DD" --pretty=format:"%h %s%n%b" --reverse for detailed commit messages
Use git show --stat <commit-hashes> --pretty=format:"%h %s" to understand scope of changes

3. Determine Version Increment Strategy

Follow semantic versioning (semver.org):

MAJOR (X.0.0): Breaking changes, incompatible API changes
MINOR (0.X.0): New features, backward-compatible functionality additions
PATCH (0.0.X): Bug fixes, backward-compatible fixes

Common indicators for d365fo-client:

New MCP tools/resources → MINOR bump
New CLI commands/features → MINOR bump
New D365 F&O data entity operations → MINOR bump
Bug fixes only → PATCH bump
Breaking API changes → MAJOR bump
Dependency updates (via dependabot with deps: prefix) → PATCH bump
CI updates (via dependabot with ci: prefix) → PATCH bump
Documentation improvements → PATCH bump

4. Update CHANGELOG.md

Follow "Keep a Changelog" format (already used by this project):

## [X.Y.Z] - YYYY-MM-DD

### Added
- New features, tools, capabilities (MCP tools, CLI commands, D365 F&O operations)

### Changed
- Changes to existing functionality

### Improved
- Performance enhancements, optimizations, better implementations

### Fixed
- Bug fixes and corrections

### Removed
- Deprecated or removed functionality

### Dependencies
- Dependency updates (from dependabot or manual updates)

### Documentation
- Documentation improvements

Read the full file on GitHub · 151 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

1mo ago First seen · 151 lines · 24 tokens per session scan A c8ab9865286b

Subscribe to this mod's changes

update-change-log is a command published in the GitHub repository mafzaal/d365fo-client (40 stars, last pushed 3d ago), licensed MIT. It adds 24 tokens to every session and 1,621 once invoked, about $0.0001 per session on Opus 5.5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-11.

Commits Git and workflow Python Releases d365fo d365tools mcp-server

CHANGELOG

Command "CHANGELOG" from bytedance/UI-TARS-desktop, covering 0.4.0 2024-12-10 - add logging, 1.2.29, 1.2.28, 1.2.26 and 1.2.25.

bytedance/UI-TARS-desktop · 0 tokens

deploy

Run the complete ClawBridge release process. This is the ONLY way to deploy — follow every step.

NickRomanek/clawbridge · 0 tokens

release

A typical CI release creates the release, associates commits, finalizes it, and records a deploy. The sentry release create examples above show the full sequence.

getsentry/toolkit · 0 tokens

changelog-auto

Auto-generar entradas de CHANGELOG.md desde commits convencionales. Usa cuando el usuario dice "generar changelog", "update changelog", "changelog", "conventional commits", "auto changelog", "release notes", "generar release notes", "伽 changelog". Genera entradas desde conventional commits (feat, fix, docs, etc.) con…

doncheli/don-cheli-sdd · 80 tokens

commit-push-pr

Commit, push, and open a PR (includes changeset creation).

pablo-albaladejo/kaiord · 14 tokens

iterate

Iteration delivery — delivery check + archive + commit & tag + bump version.

daphnee-ovo/dev-flow · 14 tokens

d365fo-client: Command for GitHub Copilot