Repository navigation
Remove gae-initializer-parent (#1587) - #1609
Merged
Merged
Conversation
dashorst
force-pushed
the
remove-gae-initializer-parent
branch
from
October 14, 2026 15:16
c566748 to
b41a018
Compare
Generated-by: Claude Haiku 5.5
dashorst
force-pushed
the
remove-gae-initializer-parent
branch
from
October 14, 2026 15:34
b41a018 to
fc82a0e
Compare
This branch was successfully deployed
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
1 participant
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.
The gae-initializer module configures Wicket for the first-generation App Engine sandbox, which is built on the Java 8 runtime. Google blocked Java 8 deployments on 31 January 2026, and Wicket 10 requires Java 17, so the module cannot be deployed where it was written for.
Fixes #1587
Part of #1592
Stacked on #1600
Generated-by: Claude Haiku 5.5