chore: updated changelog to new syntax

[Vedantsahai18]

PR Type

Enhancement, Documentation

---

Description

• Enhanced changelog generation to preserve HTML structure.

• Updated changelog template syntax for better readability.

• Improved insertion logic for new changelog content.

---

Changes walkthrough 📝

	Relevant files
Enhancement	generate_changelog.py Enhance changelog preservation and insertion logic              scripts/generate_changelog.py Adjusted logic to preserve HTML structure in changelog. Added logic to insert new changelog after specific HTML tags. Removed unnecessary blank line in the function. +4/-2
Documentation	changelog.yaml Update changelog template syntax and formatting                    scripts/templates/changelog.yaml Updated template syntax for dynamic date formatting. Added f-string formatting for user content placeholders. Improved clarity and readability of the changelog template. +6/-2

---

Need help?

Type /help how to ... in the comments thread for any questions about Qodo Merge usage.

Check out the documentation for more information.

---

Important

Enhances changelog generation by preserving HTML structure and updating template syntax for better readability.

• Changelog Generation:
  • generate_changelog.py: Adjusted logic to preserve HTML structure and insert new changelog after specific HTML tags.
  • Removed unnecessary blank line in preserve_and_update_changelog().
• Template Syntax:
  • changelog.yaml: Updated template syntax for dynamic date formatting and added f-string formatting for placeholders.
  • Improved clarity and readability of the changelog template.

^{This description was created by for 583c913. It will automatically update as commits are pushed.}

[qodo-merge-pro-for-open-source]

PR Reviewer Guide 🔍

Here are some key observations to aid the review process:

⏱️ Estimated effort to review: 2 🔵🔵⚪⚪⚪

🧪 No relevant tests

🔒 No security concerns identified

⚡ Recommended focus areas for review Error Handling The div tag search assumes the tag exists in the content. Should handle case where "" is not found to avoid potential index errors. # Find the end of the div tag div_end = existing_content.find("</div>") + 6 # Insert new changelog after the div

[qodo-merge-pro-for-open-source]

PR Code Suggestions ✨

Explore these optional code suggestions:

Category	Suggestion	Impact
Possible issue	Add missing error handling Add error handling for when the "" tag is not found in the existing content to prevent potential IndexError. scripts/generate_changelog.py [102-105] # Find the end of the div tag -div_end = existing_content.find("</div>") + 6 +div_end = existing_content.find("</div>") +if div_end == -1: + raise ValueError("Missing </div> tag in changelog file") +div_end += 6 # Insert new changelog after the div content = f"{existing_content[:div_end]}\n\n{new_changelog}{existing_content[div_end:]}" Apply this suggestion Suggestion importance[1-10]: 8 __ Why: The suggestion addresses a critical error handling case where the "" tag might be missing, which could lead to an IndexError and corrupt the changelog file. Adding proper validation improves robustness and maintainability.	Medium

[ellipsis-dev]

❌ Changes requested. Reviewed everything up to 2765b1a in 1 minute and 46 seconds

More details

• Looked at 62 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 6 drafted comments based on config settings.

1. scripts/templates/changelog.yaml:8

• Draft comment:
  Ensure f-string syntax in template is supported and secure. Intended '$ f'''' might be misinterpreted.
• Reason this comment was not posted:
  Confidence changes required: 50% <= threshold 50%
  None

2. scripts/templates/changelog.yaml:86

• Draft comment:
  Update of PR data interpolation from '{{inputs[0]['pr_data']}}' to '{steps[0].input.pr_data}' looks intentional; confirm consistency with agent API.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

3. scripts/generate_changelog.py:102

• Draft comment:
  Guard against missing '' tag; if not found, find() returns -1, causing improper insertion index.
• Reason this comment was not posted:
  Marked as duplicate.

4. scripts/templates/changelog.yaml:8

• Draft comment:
  New '$ f''' ' syntax for f-string interpolation is introduced. Ensure your template engine supports f-string evaluation and required modules (e.g., datetime) are available.
• Reason this comment was not posted:
  Marked as duplicate.

5. scripts/templates/changelog.yaml:67

• Draft comment:
  Changelog title now uses f-string syntax. Ensure that 'datetime' is in scope during evaluation or imported where necessary.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 20% <= threshold 50%
  The comment is asking the author to ensure that 'datetime' is in scope or imported, which is a general reminder rather than a specific suggestion or question. It doesn't provide a specific code suggestion or ask for a test to be written. It seems to be more of a general cautionary note, which violates the rule against asking the author to ensure something.

6. scripts/templates/changelog.yaml:86

• Draft comment:
  PR data interpolation updated from '{{inputs[0]['pr_data']}}' to '{steps[0].input.pr_data}'. Confirm that the 'steps' object with field 'input.pr_data' exists as expected.
• Reason this comment was not posted:
  Comment did not seem useful. Confidence is useful = 0% <= threshold 50%
  The comment is asking the PR author to confirm the existence of a specific object and field, which violates the rule against asking for confirmation of intentions or existence. It does not provide a specific code suggestion or ask for a test to be written.

Workflow ID: wflow_spQM7RzAt5jaMFHD

---

Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[ellipsis-dev]

❌ Changes requested. Incremental review on 583c913 in 1 minute and 47 seconds

More details

• Looked at 69 lines of code in 2 files
• Skipped 0 files when reviewing.
• Skipped posting 6 drafted comments based on config settings.

1. CHANGELOG.md:46

• Draft comment:
  Verify new changelog block ordering and spacing; ensure the intended chronological order and readability.
• Reason this comment was not posted:
  Confidence changes required: 50% <= threshold 50%
  None

2. scripts/generate_changelog.py:104

• Draft comment:
  Ensure removal of newline in changelog insertion is intentional; check readability.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 20% vs. threshold = 50%
  The removal of newlines appears intentional as part of the change. The readability of the final HTML output may not be significantly impacted since HTML generally ignores whitespace. The comment is asking to "ensure" something rather than pointing out a clear issue. Without seeing the actual output format requirements, we can't be certain this is a real problem.
  I might be underestimating the importance of source HTML readability. There could be tools or processes that expect certain formatting.
  Even if HTML readability is important, this is a minor formatting preference rather than a functional issue. The comment asks to "ensure" rather than pointing out a clear problem.
  Delete the comment as it violates the rule against asking authors to "ensure" things and doesn't point out a clear issue requiring changes.

3. scripts/generate_changelog.py:4

• Draft comment:
  Unused import 'le' from operator; remove it if not needed.
• Reason this comment was not posted:
  Confidence changes required: 50% <= threshold 50%
  None

4. scripts/generate_changelog.py:104

• Draft comment:
  Good use of len('') and removal of extra newlines; verify that the merged changelog formatting meets intended HTML structure.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

5. CHANGELOG.md:46

• Draft comment:
  Changelog sections are reordered: 'Julep AI Changelog for 14 February 2025' now appears before the '31 January 2025' section. Confirm this ordering aligns with desired release chronology.
• Reason this comment was not posted:
  Confidence changes required: 33% <= threshold 50%
  None

6. CHANGELOG.md:57

• Draft comment:
  Consider appending a newline at the end of the file for POSIX compliance and consistent diff output.
• Reason this comment was not posted:
  Decided after close inspection that this draft comment was likely wrong and/or not actionable: usefulness confidence = 10% vs. threshold = 50%
  The missing newline was introduced by moving the January changelog section to the bottom. While technically correct about POSIX compliance, this is a very minor issue that would likely be automatically handled by most editors and git configurations. It doesn't affect functionality and is more of a style/convention issue.
  The comment is technically correct and follows a common convention. Missing trailing newlines can cause minor issues with some tools.
  While technically valid, this is too minor of an issue to warrant a PR comment. Most development environments handle this automatically.
  Delete this comment as it's too minor of an issue to warrant attention in code review.

Workflow ID: wflow_BPYcUGBfJflP5FF4

---

Want Ellipsis to fix these issues? Tag @ellipsis-dev in a comment. You can customize Ellipsis with 👍 / 👎 feedback, review rules, user-specific overrides, quiet mode, and more.

[ellipsis-dev]

Remove unused import of 'le' to clean up the code.

Suggested change

from operator import le