Skip to content

docs: bring every extension to one changelog and release standard - #10

Merged
CallSohail merged 1 commit into
mainfrom
claude/fervent-galileo-1u30cs
Sep 18, 2026
Merged

CallSohail merged 1 commit into
mainfrom
claude/fervent-galileo-1u30cs

Conversation

@CallSohail

Copy link
Copy Markdown
Owner

Summary

All five extensions now keep a changelog beside the implementation, in the format RELEASING.md already prescribed but that only some files followed. No Python file is modified.

Changelogs

Extension Before After
RAGFlow Advanced Connector none added, covering the 3.0.0 published here
Rich Email Composer flat bullet list Added / Changed / Security / Compatibility
Study Mode ad-hoc thematic sections regrouped, every entry preserved
Quick Actions undated bullets dated, Fixed / Added / Changed / Compatibility / Upgrade notes
Secure Dynamic Onboarding ## [x] with partial sections normalized, header renamed to the published plugin name

Headings are now ## [MAJOR.MINOR.PATCH] - YYYY-MM-DD, newest first. Versions that predate this repository (Secure Dynamic Onboarding 7.0.0-9.0.0, RAGFlow before 3.0.0) are left undated rather than given an invented date.

Documentation

  • RAGFlow README was the thinnest in the repo; it now documents the six Tool methods, a full Valve reference with defaults and ranges read off the source, the data flow, and known limitations
  • a Changelog section on each extension README
  • a changelog column or link on the Tool, Filter, Action and Event indexes, and CHANGELOG.md added to each category's directory convention
  • fixed: the Action index listed Quick Actions as 3.0.0; the shipped version is 3.0.1
  • a per-extension changelog table on the root README

Release process

  • CONTRIBUTING.md now requires a CHANGELOG.md per implementation and names the sections it should use
  • RELEASING.md replaces its stale two-entry tag list with a published-release table for all five extensions, annotated-tag commands, and the rule that a tag points at the commit where that version's source last changed

Verification

  • no .py file in the diff
  • every declared source version matches its changelog entry, the root README and RELEASING.md (checked by script across all five extensions)
  • every relative Markdown link in the repository resolves

Follow-up

Tags and GitHub Releases are not created by this PR. This session has no release-creation tool, so I can push the annotated tags once this merges; publishing the Releases themselves needs your hand or a token with that scope.

🤖 Generated with Claude Code

https://claude.ai/code/session_018zFCVNrerYZ6TZJwVh2U4k


Generated by Claude Code

All five extensions now keep a changelog beside the implementation, in the
format RELEASING.md already prescribed but that only some files followed.

Changelogs:
- add tools/ragflow/CHANGELOG.md, the last extension without one, covering
  the 3.0.0 published in this repository;
- rewrite the email-composer, study-mode, quick-actions and secure-onboarding
  changelogs onto Added/Changed/Fixed/Security/Compatibility/Upgrade notes
  under dated "## [version]" headings, preserving every existing entry;
- leave versions that predate this repository undated rather than invent one.

Documentation:
- expand the RAGFlow README with its six Tool methods, a full Valve reference
  with defaults and ranges taken from the source, the data flow and known
  limitations;
- add a Changelog section to each extension README;
- add a changelog column or link to the Tool, Filter, Action and Event
  indexes, and the CHANGELOG.md file to each category's directory convention;
- correct the Quick Actions version in the Action index (3.0.0 -> 3.0.1);
- add a per-extension changelog table to the root README.

Release process:
- require a CHANGELOG.md per implementation in CONTRIBUTING.md and document
  the section names it uses;
- replace the stale tag list in RELEASING.md with a published-release table,
  annotated-tag instructions, and the rule that a tag points at the commit
  where that version's source last changed.

No Python file is modified by this commit.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_018zFCVNrerYZ6TZJwVh2U4k
@CallSohail
CallSohail force-pushed the claude/fervent-galileo-1u30cs branch from ea057b9 to ad88021 Compare September 18, 2026 08:34
@CallSohail
CallSohail merged commit f884120 into main Sep 18, 2026
8 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants