Minor: Add docs to release/README.md about rate limits #18704
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alamb
added
documentation
github-actions
bot
removed
the
documentation
37 tasks
alamb
commented
Nov 14, 2025
| providing two commit ids or tags followed by the version number of the release being created. For example, | ||
| to generate a change log of all changes between the `50.3.0` tag and `branch-51`, in preparation for release `51.0.0`: | ||
|
|
||
| > [!NOTE] |
Contributor
Author
There was a problem hiding this comment.
You can see a rendered preview here: https://github.com/alamb/datafusion/blob/alamb/more_release_update/dev/release/README.md#changelog-generation
Contributor
There was a problem hiding this comment.
I wonder if we should use the GitHub CLI instead?
Contributor
Author
There was a problem hiding this comment.
sounds like a good idea to me
Jefffrey
approved these changes
Nov 14, 2025
adriangb
approved these changes
Nov 15, 2025
Member
|
Thank you @alamb |
xudong963
approved these changes
Nov 15, 2025
logan-keede
pushed a commit
to logan-keede/datafusion
that referenced
this pull request
Nov 23, 2025
## Which issue does this PR close? - related to apache#17558 ## Rationale for this change I have hit rate limit issues in the past when I didn't set my github token correctly, and @xudong963 reported something similar here: apache#17558 (comment) ## What changes are included in this PR? Add a note in the release docs about how to solve the rate limiting ## Are these changes tested? <!-- We typically require tests for all PRs in order to: 1. Prevent the code from being accidentally broken by subsequent changes 2. Serve as another way to document the expected behavior of the code If tests are not included in your PR, please explain why (for example, are they covered by existing tests)? --> ## Are there any user-facing changes? <!-- If there are user-facing changes then we may require documentation to be updated before approving the PR. --> <!-- If there are any breaking changes to public APIs, please add the `api change` label. -->
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Which issue does this PR close?
51.0.0(Nov 2025) #17558Rationale for this change
I have hit rate limit issues in the past when I didn't set my github token correctly, and @xudong963 reported something similar here: #17558 (comment)
What changes are included in this PR?
Add a note in the release docs about how to solve the rate limiting
Are these changes tested?
Are there any user-facing changes?