Skip to content

ci: clear changelog after every release - #716

Merged
akshaydeo merged 1 commit into
mainfrom
10-29-ci_clear_changelog_after_every_release
Oct 30, 2025
Merged

ci: clear changelog after every release#716
akshaydeo merged 1 commit into
mainfrom
10-29-ci_clear_changelog_after_every_release

Conversation

@Pratham-Mishra04

Copy link
Copy Markdown
Collaborator

Summary

Improve the Mintlify changelog generation script to clear changelog files after processing and handle empty changelog content gracefully.

Changes

  • Modified the append_section function to check if the changelog content is empty before adding it to the output
  • Added functionality to clear changelog files after they've been processed, preventing duplicate entries in future runs
  • Improved error handling by removing the early return when content retrieval fails

Type of change

  • Bug fix
  • Feature
  • Refactor
  • Documentation
  • Chore/CI

Affected areas

  • Core (Go)
  • Transports (HTTP)
  • Providers/Integrations
  • Plugins
  • UI (Next.js)
  • Docs

How to test

Run the changelog generation script and verify:

  1. Empty changelog files are handled properly
  2. Changelog files are cleared after processing
  3. The generated output contains only non-empty sections
# Run the changelog generation script
.github/workflows/scripts/push-mintlify-changelog.sh

Breaking changes

  • Yes
  • No

Security considerations

No security implications as this only affects the documentation build process.

Checklist

  • I read docs/contributing/README.md and followed the guidelines
  • I verified the CI pipeline passes locally if applicable

@coderabbitai

coderabbitai Bot commented Oct 29, 2025

Copy link
Copy Markdown
Contributor

Warning

Rate limit exceeded

@Pratham-Mishra04 has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 2 minutes and 2 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 44eab36 and 5ae4245.

📒 Files selected for processing (1)
  • .github/workflows/scripts/push-mintlify-changelog.sh (1 hunks)
✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch 10-29-ci_clear_changelog_after_every_release

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

Copy link
Copy Markdown
Collaborator Author

This stack of pull requests is managed by Graphite. Learn more about stacking.

akshaydeo commented Oct 30, 2025

Copy link
Copy Markdown
Contributor

Merge activity

  • Oct 30, 3:15 AM UTC: A user started a stack merge that includes this pull request via Graphite.
  • Oct 30, 3:16 AM UTC: @akshaydeo merged this pull request with Graphite.

@akshaydeo
akshaydeo merged commit 1d4eed6 into main Oct 30, 2025
3 of 4 checks passed
@akshaydeo
akshaydeo deleted the 10-29-ci_clear_changelog_after_every_release branch October 30, 2025 03:16
akshaydeo added a commit that referenced this pull request Nov 17, 2025
## Summary

Improve the Mintlify changelog generation script to clear changelog files after processing and handle empty changelog content gracefully.

## Changes

- Modified the `append_section` function to check if the changelog content is empty before adding it to the output
- Added functionality to clear changelog files after they've been processed, preventing duplicate entries in future runs
- Improved error handling by removing the early return when content retrieval fails

## Type of change

- [x] Bug fix
- [ ] Feature
- [ ] Refactor
- [ ] Documentation
- [x] Chore/CI

## Affected areas

- [ ] Core (Go)
- [ ] Transports (HTTP)
- [ ] Providers/Integrations
- [ ] Plugins
- [ ] UI (Next.js)
- [x] Docs

## How to test

Run the changelog generation script and verify:
1. Empty changelog files are handled properly
2. Changelog files are cleared after processing
3. The generated output contains only non-empty sections

```sh
# Run the changelog generation script
.github/workflows/scripts/push-mintlify-changelog.sh
```

## Breaking changes

- [ ] Yes
- [x] No

## Security considerations

No security implications as this only affects the documentation build process.

## Checklist

- [x] I read `docs/contributing/README.md` and followed the guidelines
- [x] I verified the CI pipeline passes locally if applicable
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