Skip to content

COG-4286: Change GITHUB_TOKEN to GH_RELEASE_TOKEN in workflow#2360

Merged
pazone merged 2 commits intodevfrom
ci/release_pat
Mar 11, 2026
Merged

COG-4286: Change GITHUB_TOKEN to GH_RELEASE_TOKEN in workflow#2360
pazone merged 2 commits intodevfrom
ci/release_pat

Conversation

@pazone
Copy link
Contributor

@pazone pazone commented Mar 10, 2026

Updated GITHUB_TOKEN to use GH_RELEASE_TOKEN for releases.

Description

Acceptance Criteria

Type of Change

  • Bug fix (non-breaking change that fixes an issue)
  • New feature (non-breaking change that adds functionality)
  • Code refactoring
  • Other (please specify):

Screenshots

Pre-submission Checklist

  • I have tested my changes thoroughly before submitting this PR (See CONTRIBUTING.md)
  • This PR contains minimal changes necessary to address the issue/feature
  • My code follows the project's coding standards and style guidelines
  • I have added tests that prove my fix is effective or that my feature works
  • I have added necessary documentation (if applicable)
  • All new and existing tests pass
  • I have searched existing PRs to ensure this change hasn't been submitted already
  • I have linked any relevant issues in the description
  • My commits have clear and descriptive messages

DCO Affirmation

I affirm that all code in every commit of this pull request conforms to the terms of the Topoteretes Developer Certificate of Origin.

Summary by CodeRabbit

  • Chores
    • Updated release automation authentication configuration (changed token source).
  • Style
    • Minor whitespace formatting change with no behavioral impact.
  • No user-facing changes in this release.

Updated GITHUB_TOKEN to use GH_RELEASE_TOKEN for releases.
@pazone pazone requested a review from lxobr March 10, 2026 11:20
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Mar 10, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 6724ab68-a37e-4c1d-9865-e1441d09fd91

📥 Commits

Reviewing files that changed from the base of the PR and between 945d362 and 3be854d.

📒 Files selected for processing (1)
  • cognee/shared/data_models.py
✅ Files skipped from review due to trivial changes (1)
  • cognee/shared/data_models.py

Walkthrough

Replaced the token used in the GitHub Actions release workflow from GITHUB_TOKEN to GH_RELEASE_TOKEN; additionally, a whitespace-only edit was made in cognee/shared/data_models.py (no behavioral changes).

Changes

Cohort / File(s) Summary
Release workflow
.github/workflows/release.yml
Changed release step authentication token from GITHUB_TOKEN to GH_RELEASE_TOKEN.
Data model whitespace
cognee/shared/data_models.py
Whitespace-only adjustment near Node model __init__; no logic or behavioral changes.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~5 minutes

Possibly related PRs

Suggested labels

run-checks

Suggested reviewers

  • dexters1
  • lxobr
🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (2 warnings)

Check name Status Explanation Resolution
Description check ⚠️ Warning The PR description includes the template structure but lacks substantive content in key sections: the Description section is empty, Acceptance Criteria are unfilled, Type of Change is unchecked, and the Pre-submission Checklist items are all unchecked with no evidence of testing or verification. Fill in the Description section with reasoning for the token change, complete the Acceptance Criteria, select the appropriate Type of Change, and check Pre-submission Checklist items with supporting evidence of testing.
Docstring Coverage ⚠️ Warning Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (1 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main change: replacing GITHUB_TOKEN with GH_RELEASE_TOKEN in the release workflow, which is the primary modification in the changeset.

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

✨ Finishing Touches
  • 📝 Generate docstrings (stacked PR)
  • 📝 Generate docstrings (commit on current branch)
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch ci/release_pat

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

lxobr
lxobr previously approved these changes Mar 10, 2026
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@pull-checklist
Copy link

Please make sure all the checkboxes are checked:

  • I have tested these changes locally.
  • I have reviewed the code changes.
  • I have added end-to-end and unit tests (if applicable).
  • I have updated the documentation and README.md file (if necessary).
  • I have removed unnecessary code and debug statements.
  • PR title is clear and follows the convention.
  • I have tagged reviewers or team members for feedback.

@pazone pazone merged commit 8b8ee0f into dev Mar 11, 2026
138 of 141 checks passed
@pazone pazone deleted the ci/release_pat branch March 11, 2026 13:38
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.

3 participants