docs(changelog): sync full changelog from tego-standard

[baizixv]

Automatically sync full changelog files from tego-standard repository to ensure consistency. This PR overwrites the changelog files in docs repository with the complete changelog from tego-standard repository.

Summary by CodeRabbit

• Documentation
  • Added changelog entry for version 1.6.6 featuring a database-clean bug fix
  • Updated version comparison links and release reference indexes

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

📝 Walkthrough

Walkthrough

Two changelog files updated to document version 1.6.6 release with a database-clean bug fix. English and Chinese changelogs both add the new release entry, update Unreleased comparison links to reference v1.6.6, and include the version in the release index.

Changes

Cohort / File(s)	Summary
Changelog Documentation docs/en/changelog/changelog.md, docs/zh/changelog/changelog.md	Added v1.6.6 release section documenting database-clean bug fix. Updated "Unreleased" comparison links from v1.6.5 to v1.6.6 HEAD. Added v1.6.6 release tag entry to version index.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• docs(changelog): sync full changelog from tego-standard #196: Both PRs modify the same changelog files and update the Unreleased/release sections with consistent structural patterns.
• docs(changelog): sync full changelog from tego-standard #187: Both PRs make analogous edits to the same changelog files, adding a new release block and updating the Unreleased comparison link.
• docs(changelog): sync full changelog from tego-standard #188: Both PRs modify the same changelog files, updating the Unreleased comparison anchor and adding new release entries.

Poem

🐰 A tiny hop through changelog pages,
Version 1.6.6 now graces the stages!
Bug fixes recorded, links all renewed,
In English and Chinese—perfectly brewed! ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: syncing changelog files from tego-standard to maintain consistency across repositories.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

📜 Recent review details

Configuration used: defaults

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between a1645f0 and 7894ccc.

📒 Files selected for processing (2)

• docs/en/changelog/changelog.md
• docs/zh/changelog/changelog.md

🧰 Additional context used

📓 Path-based instructions (3)

docs/zh/**/*.md

📄 CodeRabbit inference engine (.cursorrules)

docs/zh/**/*.md: When creating a new file in docs/zh/, you MUST create the corresponding file in docs/en/ in the same commit or pull request
When modifying content in docs/zh/, you MUST update the corresponding file in docs/en/ in the same commit or pull request

Files:

• docs/zh/changelog/changelog.md

docs/**/*.md

📄 CodeRabbit inference engine (.cursorrules)

docs/**/*.md: Use professional technical terminology in documentation translations
Maintain original formatting (headings, lists, code blocks, tables, links) when translating documentation
Preserve code examples as-is; do not translate code or variable names
Keep image references and links functional across both language versions
Maintain markdown syntax consistency across all documentation files
Use the defined key terminology mapping when translating between Chinese and English (e.g., 灵矶 → Lingji/Tachybase, 数据表 → Data table/Collection, 字段 → Field, 卡片 → Block, 工作流 → Workflow, 触发器 → Trigger, 节点 → Node, 关系字段 → Relationship field/Association field, 数据范围 → Data scope, 联动规则 → Linkage rules, 操作 → Action/Operation, 弹窗 → Modal/Popup/Drawer)
Use proper heading hierarchy (H1 → H2 → H3) in documentation
Include code language tags in code blocks (e.g., typescript, bash)
Use relative paths for internal links in documentation
Include alt text for images in documentation for accessibility
Translate code comments only if they contain important explanations; preserve variable names, function names, and API calls

Files:

• docs/zh/changelog/changelog.md
• docs/en/changelog/changelog.md

docs/en/**/*.md

📄 CodeRabbit inference engine (.cursorrules)

Verify the Chinese version in docs/zh/ is up-to-date when modifying docs/en/; the Chinese version is the source of truth

Files:

• docs/en/changelog/changelog.md

🧠 Learnings (1)

📓 Common learnings

Learnt from: CR
Repo: tegojs/docs PR: 0
File: .cursorrules:0-0
Timestamp: 2025-11-28T16:18:24.928Z
Learning: Applies to docs/en/**/*.md : Verify the Chinese version in docs/zh/ is up-to-date when modifying docs/en/; the Chinese version is the source of truth

🔇 Additional comments (6)

docs/en/changelog/changelog.md (2)

8-17: Verify English changelog matches Chinese source of truth.

Per coding guidelines, the Chinese version in docs/zh/changelog/changelog.md is the authoritative source. Please confirm that the v1.6.6 release entry and all changes here accurately reflect the Chinese version. The added section appears correctly formatted with proper bug fix entry and PR reference, but synchronization with the Chinese source must be verified.

---

2919-2920: Comparison links properly updated for v1.6.6 release.

The [Unreleased] link correctly updated to v1.6.6...HEAD, and the new [1.6.6] release tag entry added to the version index. This maintains proper reference structure for changelog navigation.

docs/zh/changelog/changelog.md (4)

12-16: Verify corresponding English changelog was updated per coding guidelines.

According to the coding guidelines, when modifying content in docs/zh/, you MUST update the corresponding file in docs/en/ in the same commit. The AI summary mentions both English and Chinese changelogs were updated, but the English file (docs/en/changelog/changelog.md) is not included in this review context.

Please confirm that docs/en/changelog/changelog.md has been updated with the same v1.6.6 release entry and link changes in this pull request.

---

12-12: Clarify date discrepancy between consecutive release versions.

Lines 12 and 18 both show the release date as 2026-01-08 for v1.6.6 and v1.6.5. Typically, consecutive releases have different dates. Please verify whether v1.6.5 should have an earlier date.

Also applies to: 18-18

---

12-16: Changelog entry format looks good.

The v1.6.6 release entry follows the Keep a Changelog specification correctly, with proper emoji markers (🐛), a feature description with PR reference, and author attribution.

---

2919-2920: Version links properly updated.

The reference links at the bottom have been correctly updated: the [未发布] link now points to v1.6.6...HEAD and a new [1.6.6] link was added for the release tag.

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}