Repository navigation
Closes #23273: Note the removal of custom script write operations in the v4.6.8 release notes - #23662
Merged
Merged
Conversation
…the v4.6.8 release notes
jeremystretch
marked this pull request as ready for review
November 10, 2026 18:54
jeremystretch
requested review from
a team and
arthanson
and removed request for
a team
November 10, 2026 18:54
arthanson
approved these changes
Nov 10, 2026
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
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.
Closes: #23273
Adds a warning to the v4.6.8 release notes about the REST API methods removed from the scripts endpoint by #22777, and points to the module upload endpoint for managing scripts.
The OpenAPI diff between v4.6.7 and v4.6.8 matches the issue:
POST /api/extras/scripts/andPUT/PATCH/DELETE /api/extras/scripts/{id}/were removed (they now return 405). The one operation added to the schema,POST /api/extras/scripts/{id}/, isn't new behavior: scripts could already be run that way, but the endpoint was missing from the schema.