Temporarily disable release notes generation #5463
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
Release creation fails with this error: ``` HTTP 422: Validation Failed (https://api.github.com/repos/RustPython/RustPython/releases) body is too long (maximum is 125000 characters) Error: Process completed with exit code 1. ``` Most likely because there's no previous release to diff of from. Disabling, getting a green release & enabling back might fix this.
|
@youknowone can you please check ? This & another follow up PR might fix the release notes character limit we are currently hitting. |
|
@theshubhamp Releasing binary for every PR merge seems too much. Can this be a cron job like a weekly release? Also, to distinguish from periodic release from stable release, can this always-runnning releases be marked as pre-release? |
|
@youknowone yes that makes sense. Had added on push main as a starting point, we should be able to swap that with a schedule. I'll send a PR with weekly schedule and notes generation enabled. Monday GMT morning sounds fine ? Do you see stable releases being manual short term ? |
|
@youknowone handled in #5466. Could you check ? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Release creation fails with this error:
Most likely because there's no previous release to diff of from.
Disabling, getting a green release & enabling back might fix this.