Skip to content

Conversation

@Charan-BS
Copy link
Contributor

@Charan-BS Charan-BS commented Nov 14, 2025

Description

Added a complete CHANGELOG.md file for the Resonate app.
This includes:

  • Versioned changelogs for v1.0.0, v2.0.0, and v3.0.0
  • Fully localized release notes in:
    • en-US
    • hi-IN
    • gu-IN
    • mr-IN
    • kn-IN
  • Clean markdown formatting with consistent sections:
    • New Features
    • Language Support (where applicable)

This provides a single place for maintainers and contributors to track feature changes, language additions, and version updates.

Fixes #585

Type of change

New feature (documentation addition — non-breaking)

How Has This Been Tested?

  • Verified formatting with GitHub markdown preview
  • Checked consistency across all versions (1.0.0 → 3.0.0)
  • Ensured all translations are clean, correct, and follow app’s localization style
  • Confirmed all sections follow project’s documentation standards

Checklist:

  • My code follows the style guidelines of this project
  • I have performed a self-review of my own work
  • I have commented my code / documentation where needed
  • I have made corresponding changes to the documentation
  • My changes generate no new warnings
  • I have added tests (N/A — documentation change only)
  • New and existing unit tests pass locally (N/A — documentation change only)
  • Any dependent changes have been merged and published in downstream modules
  • I have checked my changes for typos and formatting issues

Maintainer Checklist

Summary by CodeRabbit

  • Documentation

    • Updated changelog for v1.0.0–v3.0.0 with multilingual release notes.
  • New Features

    • Announced core features: Voice Stories, Live Audio Rooms, Events, Pair Chat, Rooms chat, Live Chapters, search, moderation, follow/call features, and app settings.
  • Localization

    • Added Gujarati, Marathi, and Kannada support; updated Hindi and English entries.
    • Refreshed translation keys and search-related translations across locales.

@github-actions
Copy link
Contributor

🎉 Welcome @Charan-BS!
Thank you for your pull request! Our team will review it soon. 🔍

  • Please ensure your PR follows the contribution guidelines. ✅
  • All automated tests should pass before merging. 🔄
  • If this PR fixes an issue, link it in the description. 🔗

We appreciate your contribution! 🚀

@coderabbitai
Copy link

coderabbitai bot commented Nov 14, 2025

Walkthrough

Added a multi-language CHANGELOG.md documenting releases 1.0.0–3.0.0 and updated localization resources: android/untranslated.txt was replaced from an empty object to populated multilingual keys; untranslated.txt had reordering/additions/removals of translation keys. No code or public API declarations changed.

Changes

Cohort / File(s) Change Summary
Changelog Documentation
CHANGELOG.md
Added a multi-locale changelog for versions 1.0.0–3.0.0 with feature lists in en-US, hi-IN, gu-IN, mr-IN, kn-IN.
Android untranslated resource
android/untranslated.txt
Replaced the prior empty object ({}) with a populated JSON object adding language keys gu, kn, and mr and arrays of translation entries.
Project untranslated resource
untranslated.txt
Modified translation key arrays: added several search-related keys to gu; reordered kn and mr lists by removing and re-adding failedToRemoveRoom and roomRemovedSuccessfully (position changed). No code changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

  • Verify CHANGELOG.md formatting and locale consistency.
  • Confirm android/untranslated.txt JSON structure and encoding are correct.
  • Ensure untranslated.txt key reordering is intentional and not referenced by tooling that depends on ordering.

Possibly related PRs

  • Translation kn #583 — Related updates to Kannada localization assets/config; likely overlaps with kn entries here.
  • Release v3.0.0 #601 — Broad localization and release changes for v3.0.0 affecting similar locale and resource files.

Suggested reviewers

  • M4dhav

Poem

🐰 I hopped through keys both new and old,

A changelog sown in fonts and bold,
I nudged translations into place,
Tidied lists with gentle pace,
A rabbit cheers — the repo’s told 🥕✨

Pre-merge checks and finishing touches

❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Out of Scope Changes check ❓ Inconclusive The PR includes changes to android/untranslated.txt and untranslated.txt that add translation keys but are not addressed in the linked issue objectives; these appear to be ancillary to the primary CHANGELOG.md documentation goal. Clarify whether the changes to untranslated.txt files are necessary for the changelog feature or represent separate translation work that should be in a different PR.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title 'added changelog file' accurately describes the primary change—adding a CHANGELOG.md file. It is concise, clear, and directly related to the main objective of the changeset.
Linked Issues check ✅ Passed The PR fully addresses issue #585 by creating a CHANGELOG.md with versioned entries (v1.0.0, v2.0.0, v3.0.0) in multiple languages, enabling change tracking and providing release notes for GitHub Releases.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment

📜 Recent review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 6d2b9d3 and 9ad8481.

📒 Files selected for processing (2)
  • android/untranslated.txt (1 hunks)
  • untranslated.txt (3 hunks)
🚧 Files skipped from review as they are similar to previous changes (1)
  • untranslated.txt
🔇 Additional comments (1)
android/untranslated.txt (1)

1-71: Verify the untranslated key sets are intentionally different across languages.

The file populates Gujarati ("gu"), Kannada ("kn"), and Marathi ("mr") with untranslated translation keys. However, there's a significant disparity: "gu" has 33 untranslated keys (including appPreferences through modelDownloadInfo), while "kn" and "mr" each have only 16 untranslated keys. The additional keys in "gu" (e.g., appPreferences, transcriptionModel variants, modelDownloadInfo) are not present in the "kn" and "mr" lists.

Ensure this difference is intentional—i.e., that "gu" legitimately has more untranslated keys while "kn" and "mr" are more complete, or that this reflects the actual translation status for each language. If all three languages should have the same set of untranslated keys, this needs to be corrected.


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

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

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 1

🧹 Nitpick comments (1)
CHANGELOG.md (1)

106-108: Standardize language listing order across v3.0.0 sections.

The "New Language Support" subsections list languages in inconsistent orders:

  • en-US (lines 106–108): Gujarati, Marathi, Kannada
  • mr-IN (lines 146–148): मराठी, गुजराती, कन्नड (Marathi, Gujarati, Kannada)
  • kn-IN (lines 159–161): ಕನ್ನಡ, ಗುಜರಾತಿ, ಮರಾಠಿ (Kannada, Gujarati, Marathi)

Choose one consistent order (e.g., alphabetical by language name, or by addition date) and apply it across all language subsections for clarity and maintainability.

Also applies to: 146-148, 159-161

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between b063ecb and e19c2de.

📒 Files selected for processing (1)
  • CHANGELOG.md (1 hunks)
🧰 Additional context used
🪛 LanguageTool
CHANGELOG.md

[grammar] ~15-~15: Ensure spelling is correct
Context: ...onate का प्रथम संस्करण - आवाज़ कहानियाँ बनाएं और सुनें - सीधा ऑडियो कमरों में शामिल ह...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~15-~15: Ensure spelling is correct
Context: ... संस्करण - आवाज़ कहानियाँ बनाएं और सुनें - सीधा ऑडियो कमरों में शामिल हों - अपने आयोजन ...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~42-~42: Ensure spelling is correct
Context: ...್ಯಗಳು - Resonate ನ ಮೊದಲ ಬಿಡುಗಡೆ - ಧ್ವನಿ ಕಥೆಗಳು ರಚಿಸಿ ಮತ್ತು ಕೇಳಿ - ನೇರ ಧ್ವನಿ ಕೋಣೆಗಳಿಗೆ ...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~44-~44: Ensure spelling is correct
Context: ... ಕೋಣೆಗಳಿಗೆ ಸೇರಿ - ನಿಮ್ಮ ಕಾರ್ಯಕ್ರಮಗಳನ್ನು ನಿಗದಿಪಡಿ - ಪೇರ್ ಚಾಟ್ ಮೂಲಕ ಹೊಸಜನರನ್ನು ಪರಿಚಯಿಸಿಕೊಳ್ಳಿ...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~45-~45: Ensure spelling is correct
Context: ...ರ್ಯಕ್ರಮಗಳನ್ನು ನಿಗದಿಪಡಿ - ಪೇರ್ ಚಾಟ್ ಮೂಲಕ ಹೊಸಜನರನ್ನು ಪರಿಚಯಿಸಿಕೊಳ್ಳಿ - ಮುಕ್ತ ಮೂಲದ ಸಾಮಾಜಿಕ ಧ್ವ...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~84-~84: Ensure spelling is correct
Context: ...र जोडून थेट कॉल करा - कथा आणि वापरकर्ते यांची जलद शोध ### kn-IN #### ಹೊಸ ವೈಶಿಷ್ಟ್ಯಗಳ...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~159-~159: Ensure spelling is correct
Context: ...ೊಸ ಆಯ್ಕೆಗಳು #### ಹೊಸ ಭಾಷಾ ಬೆಂಬಲ - ಕನ್ನಡ - ಗುಜરಾತಿ - ಮರಾಠಿ

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

⏰ Context from checks skipped due to timeout of 90000ms. You can increase the timeout in your CodeRabbit configuration to a maximum of 15 minutes (900000ms). (1)
  • GitHub Check: Run Software Tests
🔇 Additional comments (1)
CHANGELOG.md (1)

1-161: Verify version ordering convention.

The changelog lists versions in ascending order (1.0.0, 2.0.0, 3.0.0). Most changelogs follow descending order (newest first) for quick access to recent changes. Verify this is intentional or if you'd prefer to reverse the order for better UX. Either way, ensure consistency with your project's conventions.

CHANGELOG.md Outdated
Comment on lines 105 to 123
### New Language Support
- Gujarati
- Marathi
- Kannada


### hi-IN
### नई सुविधाओं
- लाइव चैप्टर्स: स्टोरी चैप्टर्स लाइव शुरू करें
- रूम सर्च: आप जिन कमरों को खोज रहे हैं, उन्हें तेज़ी से ढूँढें
- होस्ट मॉडरेशन और यूजर रिपोर्टिंग: होस्ट के लिए बेहतर मॉडरेशन और एक उपयोगकर्ता रिपोर्टिंग प्रणाली।
- रूम हटाएँ: उपयोगकर्ता अब कमरों को हटा सकते हैं।
- अतिरिक्त ऐप सेटिंग्स: आपके अनुभव पर अधिक नियंत्रण के लिए हमने सेटिंग्स मेनू में और विकल्प जोड़े हैं।

### नई भाषा का समर्थन
- गुजराती
- मराठी
- कन्नड़

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟠 Major

Fix v3.0.0 structure and heading levels for consistency with v1.0.0 and v2.0.0.

Two structural issues in v3.0.0:

  1. Lines 105–109: The "New Language Support" subsection breaks the established pattern. In v1.0.0 and v2.0.0, each language subsection contains only that language's features. This generic section interrupts the language-specific organization and duplicates information found in each language's subsection. Move language support details into each language subsection (e.g., as a separate subheading under the language).

  2. Lines 111–123 (hi-IN): The section uses ### नई सुविधाओं and ### नई भाषा का समर्थन, but should use #### (four hashes) to maintain consistency with other language subsections (see lines 3–4 for en-US, lines 12–13 for hi-IN in v1.0.0, etc.).

Apply this structure for each language section:

### [Language-Code]
#### [Feature Category Header]
- [features]
🤖 Prompt for AI Agents
In CHANGELOG.md around lines 105 to 123, move the three language bullets under
"New Language Support" into each language’s own subsection and change the hi-IN
subheadings from ### नई सुविधाओं and ### नई भाषा का समर्थन to use #### (four
hashes) so they match the established pattern; restructure so each language
block follows the pattern "### [Language-Code]" then one or more "#### [Feature
Category]" headers with their bullets (i.e., remove the separate generic "New
Language Support" section and place those language entries as a #### subheading
within each language section).

@M4dhav M4dhav self-requested a review November 15, 2025 13:45
@M4dhav M4dhav added documentation Improvements or additions to documentation good first issue Good for newcomers labels Nov 15, 2025
@M4dhav
Copy link
Contributor

M4dhav commented Nov 15, 2025

Hey @Charan-BS , like CodeRabbit suggested, the formatting needs to be such that Workflows can easily detect what are release notes and what aren't

Copy link
Contributor

@M4dhav M4dhav left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please change formatting for the changelogs. You can use Angular Brackets to wrap notes, like so:

@Charan-BS
Copy link
Contributor Author

I will do it now

Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
CHANGELOG.md (1)

48-93: Minor stylistic observation: language support handling differs between v2.0.0 and v3.0.0.

In v2.0.0, Hindi language support is listed as a feature item under "New Features" (line 53: "Hindi language support"). In v3.0.0, new language support is separated into its own #### New Language Support section. This inconsistency is likely intentional—reflecting that v3.0.0 adds multiple languages simultaneously, warranting a distinct section—but be aware that tooling or CI pipelines expecting consistent section structures might need adjustment.

If consistency is critical for CI workflows parsing release notes, consider either (a) retroactively adding a dedicated "New Language Support" section to v2.0.0 with Hindi, or (b) consolidating v3.0.0's language support back into "New Features" as individual items. This is optional and depends on your release note automation requirements.

📜 Review details

Configuration used: CodeRabbit UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e19c2de and 6d2b9d3.

📒 Files selected for processing (3)
  • CHANGELOG.md (1 hunks)
  • android/untranslated.txt (0 hunks)
  • untranslated.txt (0 hunks)
💤 Files with no reviewable changes (2)
  • android/untranslated.txt
  • untranslated.txt
🧰 Additional context used
🪛 LanguageTool
CHANGELOG.md

[grammar] ~15-~15: Ensure spelling is correct
Context: ...onate का प्रथम संस्करण - आवाज़ कहानियाँ बनाएं और सुनें - सीधा ऑडियो कमरों में शामिल ह...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~42-~42: Ensure spelling is correct
Context: ...್ಯಗಳು - Resonate ನ ಮೊದಲ ಬಿಡುಗಡೆ - ಧ್ವನಿ ಕಥೆಗಳು ರಚಿಸಿ ಮತ್ತು ಕೇಳಿ - ನೇರ ಧ್ವನಿ ಕೋಣೆಗಳಿಗೆ ...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~44-~44: Ensure spelling is correct
Context: ... ಕೋಣೆಗಳಿಗೆ ಸೇರಿ - ನಿಮ್ಮ ಕಾರ್ಯಕ್ರಮಗಳನ್ನು ನಿಗದಿಪಡಿ - ಪೇರ್ ಚಾಟ್ ಮೂಲಕ ಹೊಸಜನರನ್ನು ಪರಿಚಯಿಸಿಕೊಳ್ಳಿ...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~45-~45: Ensure spelling is correct
Context: ...ರ್ಯಕ್ರಮಗಳನ್ನು ನಿಗದಿಪಡಿ - ಪೇರ್ ಚಾಟ್ ಮೂಲಕ ಹೊಸಜನರನ್ನು ಪರಿಚಯಿಸಿಕೊಳ್ಳಿ - ಮುಕ್ತ ಮೂಲದ ಸಾಮಾಜಿಕ ಧ್ವ...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~84-~84: Ensure spelling is correct
Context: ...र जोडून थेट कॉल करा - कथा आणि वापरकर्ते यांची जलद शोध ### kn-IN #### ಹೊಸ ವೈಶಿಷ್ಟ್ಯಗಳ...

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)


[grammar] ~159-~159: Ensure spelling is correct
Context: ...ೊಸ ಆಯ್ಕೆಗಳು #### ಹೊಸ ಭಾಷಾ ಬೆಂಬಲ - ಕನ್ನಡ - ಗುಜરಾತಿ - ಮರಾಠಿ

(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)

🔇 Additional comments (1)
CHANGELOG.md (1)

97-161: Structural improvements applied; heading levels now consistent across all versions.

The v3.0.0 section now properly maintains the established heading hierarchy—each language subsection uses #### (four hashes) for feature categories, consistent with v1.0.0 and v2.0.0. Language support is now localized within each language section (e.g., "नई भाषा का समर्थन" under hi-IN, "નવી ભાષા આધાર" under gu-IN) rather than as a single generic section, which improves clarity and parallelism.

@Charan-BS
Copy link
Contributor Author

Charan-BS commented Nov 15, 2025

I made the changes just how the coderabbit suggested, hope that works

but i have deleted untranslated.txt files, should i add it real quick and push the changes?

@Charan-BS Charan-BS requested a review from M4dhav November 16, 2025 09:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

documentation Improvements or additions to documentation good first issue Good for newcomers

Projects

None yet

Development

Successfully merging this pull request may close these issues.

DOC: Make a CHANGELOG.md Document to track changes in new releases

2 participants