chore: remove changelog (#2112)

Signed-off-by: exploreriii <133720349+exploreriii@users.noreply.github.com>

Author: exploreriii

.github/ISSUE_TEMPLATE/00-good-first-issue-candidate.yml

@@ -55,7 +55,7 @@ body:
       value: |
         <!-- Describe the issue here -->
 
-        <!-- Identify which files to look at -->  
+        <!-- Identify which files to look at -->
     validations:
       required: true
 
@@ -169,8 +169,6 @@ body:
 
         - [ ] **Commit with Conventional format and DCO, GPG signing:**  commit changes using: `git commit -S -s -m "chore: your message"`, [Guide](https://github.com/hiero-ledger/sdk-collaboration-hub/blob/main/guides/issue-progression/for-developers/contributor-workflow.md#3-commit-your-changes)
 
-        - [ ] **Add a `CHANGELOG.md` entry:** under the appropriate **[UNRELEASED]** section and commit as `git commit -S -s -m "chore: changelog entry"` [Guide](https://github.com/hiero-ledger/sdk-collaboration-hub/blob/main/guides/issue-progression/for-developers/contributor-workflow.md#4-create-a-changelog-entry)
-
         #### 🚀 Create the pull request
 
         - [ ] **Push your commits:**  push your branch to your fork `git push origin your-branch-name` [Guide](https://github.com/hiero-ledger/sdk-collaboration-hub/blob/main/guides/issue-progression/for-developers/contributor-workflow.md#5-submitting-a-pull-request)
@@ -197,7 +195,6 @@ body:
         - [ ] I have worked from a branch that is up to date with main
         - [ ] I have not made changes outside the scope of this issue
         - [ ] My commits are signed: `git commit -S -s -m "chore: description"` — [Signing guide](https://github.com/hiero-ledger/sdk-collaboration-hub/blob/main/guides/issue-progression/for-developers/signing.md)
-        - [ ] I added a CHANGELOG.md entry (if appropriate) under `[Unreleased]` — [Changelog guide](https://github.com/hiero-ledger/sdk-collaboration-hub/blob/main/guides/issue-progression/for-developers/changelog-guide.md)
         - [ ] I linked the issue in my PR description using `Fixes #issue_number` to automatically close it when merged
         - [ ] I have applied appropriate linting, code quality, and formatting tools used in this repo (if applicable).
 

.github/ISSUE_TEMPLATE/01-good-first-issue.yml

@@ -42,7 +42,7 @@ body:
       value: |
         <!-- Describe the issue here -->
 
-        <!-- Identify which files to look at -->  
+        <!-- Identify which files to look at -->
     validations:
       required: true
 
@@ -156,8 +156,6 @@ body:
 
         - [ ] **Commit with Conventional format and DCO, GPG signing:**  commit changes using: `git commit -S -s -m "chore: your message"`, [Guide](https://github.com/hiero-ledger/sdk-collaboration-hub/blob/main/guides/issue-progression/for-developers/contributor-workflow.md#3-commit-your-changes)
 
-        - [ ] **Add a `CHANGELOG.md` entry:** under the appropriate **[UNRELEASED]** section and commit as `git commit -S -s -m "chore: changelog entry"` [Guide](https://github.com/hiero-ledger/sdk-collaboration-hub/blob/main/guides/issue-progression/for-developers/contributor-workflow.md#4-create-a-changelog-entry)
-
         #### 🚀 Create the pull request
 
         - [ ] **Push your commits:**  push your branch to your fork `git push origin your-branch-name` [Guide](https://github.com/hiero-ledger/sdk-collaboration-hub/blob/main/guides/issue-progression/for-developers/contributor-workflow.md#5-submitting-a-pull-request)
@@ -184,7 +182,6 @@ body:
         - [ ] I have worked from a branch that is up to date with main
         - [ ] I have not made changes outside the scope of this issue
         - [ ] My commits are signed: `git commit -S -s -m "chore: description"` — [Signing guide](https://github.com/hiero-ledger/sdk-collaboration-hub/blob/main/guides/issue-progression/for-developers/signing.md)
-        - [ ] I added a CHANGELOG.md entry (if appropriate) under `[Unreleased]` — [Changelog guide](https://github.com/hiero-ledger/sdk-collaboration-hub/blob/main/guides/issue-progression/for-developers/changelog-guide.md)
         - [ ] I linked the issue in my PR description using `Fixes #issue_number` to automatically close it when merged
         - [ ] I have applied appropriate linting, code quality, and formatting tools used in this repo (if applicable).
 

.github/ISSUE_TEMPLATE/02-beginner-issue.yml

@@ -3,7 +3,6 @@ description: Create a beginner issue for contributors ready to learn the codebas
 labels: ["beginner"]
 assignees: []
 body:
-
   - type: markdown
     attributes:
       value: |
@@ -40,16 +39,15 @@ body:
       label: 🐞 Problem Description
       description: |
         Describe the issue so it is easy for a beginner contributor to understand what needs to be done and why. 
-        Include which file(s) to look at, what the current behaviour is, and what the desired behaviour is.    
+        Include which file(s) to look at, what the current behaviour is, and what the desired behaviour is.
       value: |
         <!-- Describe the issue here -->  
 
-        <!-- Identify which files to look at and patterns to recognise -->  
+        <!-- Identify which files to look at and patterns to recognise -->
 
     validations:
       required: true
 
-
   - type: textarea
     id: solution
     attributes:
@@ -160,7 +158,6 @@ body:
         - Run the example script and confirm output matches expected behavior
         - You will need a [Hedera Portal](https://portal.hedera.com/) account for testnet credentials
 
-
   - type: textarea
     id: quality_standards
     attributes:
@@ -199,7 +196,6 @@ body:
         - [ ] I did not modify files unrelated to this issue
         - [ ] Clean git history — no rebase artifacts, merge commits, or unrelated files
         - [ ] My commits are signed: `git commit -S -s -m "chore: description"` — [Signing guide](https://github.com/hiero-ledger/sdk-collaboration-hub/blob/main/guides/issue-progression/for-developers/signing.md)
-        - [ ] I added a CHANGELOG.md entry (if appropriate) under `[Unreleased]` — [Changelog guide](https://github.com/hiero-ledger/sdk-collaboration-hub/blob/main/guides/issue-progression/for-developers/changelog-guide.md)
         - [ ] I have included appropriate tests and all CI checks pass.
 
   - type: textarea

.github/ISSUE_TEMPLATE/03-intermediate-issue.yml

@@ -3,7 +3,6 @@ description: Create a well-documented issue for contributors ready to own larger
 labels: ["intermediate"]
 assignees: []
 body:
-
   - type: markdown
     attributes:
       value: |
@@ -40,9 +39,9 @@ body:
       description: |
         Clearly articulate the problem and its impact.
         Assume the reader can navigate src/, tests/, and examples/.
-        Explain: what is wrong or missing, where it lives, and why it matters.      
+        Explain: what is wrong or missing, where it lives, and why it matters.
       value: |
-        <!-- Describe the issue here -->      
+        <!-- Describe the issue here -->
     validations:
       required: true
 
@@ -104,7 +103,6 @@ body:
         - [ ] **Protobuf Alignment** (reading `.proto` files, `_to_proto()` / `_from_proto()` correctness)
         - [ ] **Testing** (unit, integration, mocking, test coverage for edge cases and failure modes)
 
-
   - type: textarea
     id: intermediate_contributors
     attributes:
@@ -169,7 +167,6 @@ body:
         - Compare your example with similar existing examples for consistency
         - You will need a [Hedera Portal](https://portal.hedera.com/) account for testnet credentials
 
-
   - type: textarea
     id: quality_standards
     attributes:
@@ -215,7 +212,6 @@ body:
         - [ ] I did not modify files unrelated to this issue
         - [ ] Clean git history — no rebase artifacts, merge commits, or unrelated files
         - [ ] My commits are signed: `git commit -S -s -m "chore: description"` — [Signing guide](https://github.com/hiero-ledger/sdk-collaboration-hub/blob/main/guides/issue-progression/for-developers/signing.md)
-        - [ ] I added a CHANGELOG.md entry (if appropriate) under `[Unreleased]` — [Changelog guide](https://github.com/hiero-ledger/sdk-collaboration-hub/blob/main/guides/issue-progression/for-developers/changelog-guide.md)
         - [ ] I have verified naming, types, and field ordering against pinned Protobufs.
         - [ ] I have applied appropriate linting, code quality, and formatting tools used in this repo.
         - [ ] I have included appropriate tests and all CI checks pass.

.github/scripts/bot-merge-conflict.js

@@ -23,7 +23,7 @@ module.exports = async ({ github, context, core }) => {
 
       if (pr.mergeable_state !== 'unknown') return pr;
 
-      console.log(`PR #${prNumber} state is 'unknown'. Retrying (${i+1}/10)...`);
+      console.log(`PR #${prNumber} state is 'unknown'. Retrying (${i + 1}/10)...`);
       await new Promise(r => setTimeout(r, 2000));
     }
     const { data: pr } = await github.rest.pulls.get({ owner, repo, pull_number: prNumber });
@@ -44,7 +44,7 @@ module.exports = async ({ github, context, core }) => {
       return;
     }
 
-    const body = `Hi, this is MergeConflictBot.\nYour pull request cannot be merged because it contains **merge conflicts**.\n\nPlease resolve these conflicts locally and push the changes.\n\n### Quick Fix for CHANGELOG.md Conflicts\nIf your conflict is only in **CHANGELOG.md**, you can resolve it easily using the [GitHub web editor](https://docs.github.com/en/codespaces/the-githubdev-web-based-editor):\n1. Click on the "Resolve conflicts" button in the PR\n2. Accept both changes (keep both changelog entries)\n3. Click "Mark as resolved"\n4. Commit the merge\n\nFor all other merge conflicts, please read:\n- [Resolving Merge Conflicts](https://github.com/${owner}/${repo}/blob/main/docs/sdk_developers/merge_conflicts.md)\n- [Rebasing Guide](https://github.com/${owner}/${repo}/blob/main/docs/sdk_developers/rebasing.md)\n\nThank you for contributing!\n<!-- \nFrom the Hiero Python SDK Team\n${BOT_SIGNATURE} -->`;
+    const body = `Hi, this is MergeConflictBot.\nYour pull request cannot be merged because it contains **merge conflicts**.\n\nPlease resolve these conflicts locally and push the changes.\n\n### \n\nThank you for contributing!\n<!-- \nFrom the Hiero Python SDK Team\n${BOT_SIGNATURE} -->`;
     if (dryRun) {
       console.log(`[DRY RUN] Would post comment to PR #${prNumber}: ${body}`);
       return;