Repository navigation
Fix start.spring.io pr bugs for existing entries - #41
Merged
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
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.
There was an issue in the post release workflow for 2025.1.4 and the PR that was created for start.spring.io. It added a new entry for the release instead of bumping the version of the existing entry for the 2025.1.x release (which was 2025.1.3 when the PR was created)
Here is the PR that was created
spring-io/start.spring.io#2311
Here is the post release run for 2025.1.4
https://github.com/spring-cloud/spring-cloud-github-actions/actions/runs/39878023893
Here is what the PR should have done
spring-io/start.spring.io@2d7f97c
In addition the version bump for 2026.0.0-RC1 changed the compatibility range when it shouldn't have
See spring-io/start.spring.io#2312