Skip to content

Conversation

@ReenigneArcher
Copy link
Member

Description

The updateChangelogFile function now checks if the changelog content has changed before committing updates. If the content is unchanged, it skips the commit and logs a message, preventing unnecessary updates.

Screenshot

Issues Fixed or Closed

Roadmap Issues

Type of Change

  • feat: New feature (non-breaking change which adds functionality)
  • fix: Bug fix (non-breaking change which fixes an issue)
  • docs: Documentation only changes
  • style: Changes that do not affect the meaning of the code (white-space, formatting, missing semicolons, etc.)
  • refactor: Code change that neither fixes a bug nor adds a feature
  • perf: Code change that improves performance
  • test: Adding missing tests or correcting existing tests
  • build: Changes that affect the build system or external dependencies
  • ci: Changes to CI configuration files and scripts
  • chore: Other changes that don't modify src or test files
  • revert: Reverts a previous commit
  • BREAKING CHANGE: Introduces a breaking change (can be combined with any type above)

Checklist

  • Code follows the style guidelines of this project
  • Code has been self-reviewed
  • Code has been commented, particularly in hard-to-understand areas
  • Code docstring/documentation-blocks for new or existing methods/components have been added or updated
  • Unit tests have been added or updated for any new or modified functionality

AI Usage

  • None: No AI tools were used in creating this PR
  • Light: AI provided minor assistance (formatting, simple suggestions)
  • Moderate: AI helped with code generation or debugging specific parts
  • Heavy: AI generated most or all of the code changes

The updateChangelogFile function now checks if the changelog content has changed before committing updates. If the content is unchanged, it skips the commit and logs a message, preventing unnecessary updates.
@codecov
Copy link

codecov bot commented Oct 18, 2025

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (066520e) to head (c0f3974).
⚠️ Report is 1 commits behind head on master.
✅ All tests successful. No failed tests found.

Additional details and impacted files
@@            Coverage Diff            @@
##            master       #50   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files            6         6           
  Lines          798       807    +9     
  Branches        79        82    +3     
=========================================
+ Hits           798       807    +9     
Flag Coverage Δ
Linux 100.00% <100.00%> (ø)
Windows 82.65% <100.00%> (+0.19%) ⬆️
macOS 100.00% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines Coverage Δ
actions/release_changelog/changelog.js 100.00% <100.00%> (ø)

Switches release workflow to use GH_BOT_TOKEN. Enhances changelog update tests to check for unchanged content and skip unnecessary commits, improving efficiency and test coverage.
Introduced test helper functions to mock GitHub API responses for changelog file operations, improving readability and reducing code duplication in updateChangelogFile and related tests.
Extracted repeated assertions for branch and file creation into a helper function `verifyBranchAndFileCreation` to improve test readability and reduce duplication in changelog generator tests.
@sonarqubecloud
Copy link

@ReenigneArcher ReenigneArcher merged commit 34a5411 into master Oct 18, 2025
66 checks passed
@ReenigneArcher ReenigneArcher deleted the fix/release_changelog/skip-update-if-unchanged branch October 18, 2025 01:25
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