Skip to content

Issues 16060 upgrade docs mixed up version numbers - #16074

Merged
jdaugherty merged 2 commits into
8.0.xfrom
issues-16060-Upgrade-docs-mixed-up-version-numbers
Aug 1, 2026
Merged

Issues 16060 upgrade docs mixed up version numbers#16074
jdaugherty merged 2 commits into
8.0.xfrom
issues-16060-Upgrade-docs-mixed-up-version-numbers

Conversation

@dauer

@dauer dauer commented Jul 31, 2026

Copy link
Copy Markdown
Contributor

Description

Contributor Checklist

Please review the following checklist before submitting your pull request. Pull requests that do not meet these requirements may be closed without review.

Issue and Scope

  • This PR is linked to an existing issue that has been acknowledged or approved by the project team. If no approved issue exists, please give background on why this change is necessary. Tickets are preferred for release change log history.
  • This PR addresses the complete scope of the linked issue. Partial implementations or unfinished work should not be submitted for review.
  • This PR contains a single, focused change. Unrelated changes should be submitted as separate pull requests.
  • This PR targets the correct branch for the type of change:
    • Patch release branches (e.g., 7.0.x): Bug fixes only. No new features or API changes.
    • Minor release branches (e.g., 7.1.x): New features are welcome, but breaking existing APIs must be avoided.
    • Major release branches (e.g., 8.0.x): Reserved for major changes. Breaking API changes are permitted.

Code Quality

  • I have added or updated tests that cover the changes introduced in this PR. All code contributions are expected to include appropriate test coverage.
  • I have verified that all existing tests pass by running ./gradlew build --rerun-tasks.
  • My code follows the project's code style guidelines. I have run ./gradlew codeStyle and resolved any violations. See Code Style for details.
  • This PR does not include mass reformatting, style-only changes, or large-scale refactoring unless it was explicitly approved in the linked issue. Unsolicited reformatting will not be accepted.
  • If generative AI tooling was used in preparing this contribution, a quality model was used to ensure contributions are consistent with the project's quality standards.

Licensing and Attribution

Documentation

  • If this PR introduces user-facing changes, I have included or updated the relevant documentation.
  • If this PR adds a new feature, I have updated the What's New section of the Grails Guide.
  • If this PR introduces breaking changes or changes that require user action during an upgrade, I have updated the Upgrade Notes for the corresponding version in the Grails Guide.
  • The PR description clearly explains what was changed and why.

First-time contributors: Please read our Contributing Guide before submitting.
Pull requests that appear to be auto-generated, incomplete, or unrelated to an approved issue may be
closed to help maintainers focus on reviewed and planned work. We appreciate your understanding.

dauer added 2 commits July 31, 2026 18:08
Upgrade documentation: Mixed-up version numbers in headings for Spring and
Spring Boot in upgrading70x.adoc
@testlens-app

testlens-app Bot commented Jul 31, 2026

Copy link
Copy Markdown

🚨 TestLens detected 1 failed test 🚨

Here is what you can do:

  1. Inspect the test failures carefully.
  2. If you are convinced that some of the tests are flaky, you can mute them below.
  3. Finally, trigger a rerun by checking the rerun checkbox.

Test Summary

CI / Build Grails-Core (macos-latest, 21) > :grails-async-core:test

Test Runs Flakiness
FutureTaskPromiseFactorySpec > Test promise onError handling 1% 🟡

🏷️ Commit: ebe6614
▶️ Tests: 55887 executed
⚪️ Checks: 60/60 completed

Test Failures

FutureTaskPromiseFactorySpec > Test promise onError handling (:grails-async-core:test in CI / Build Grails-Core (macos-latest, 21))
Expected exception of type 'java.util.concurrent.ExecutionException', but got 'java.lang.RuntimeException'
	at grails.async.FutureTaskPromiseFactorySpec.Test promise onError handling(FutureTaskPromiseFactorySpec.groovy:118)
Caused by: java.lang.RuntimeException: bad
	at grails.async.FutureTaskPromiseFactorySpec.Test promise onError handling_closure17(FutureTaskPromiseFactorySpec.groovy:110)
	at grails.async.FutureTaskPromiseFactorySpec.Test promise onError handling_closure17(FutureTaskPromiseFactorySpec.groovy)

Muted Tests

Select tests to mute in this pull request:

  • FutureTaskPromiseFactorySpec > Test promise onError handling

Reuse successful test results:

  • ♻️ Only rerun the tests that failed or were muted before

Click the checkbox to trigger a rerun:

  • Rerun jobs

Learn more about TestLens at testlens.app.

@codecov

codecov Bot commented Jul 31, 2026

Copy link
Copy Markdown

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 51.8572%. Comparing base (57883c4) to head (ebe6614).

Additional details and impacted files

Impacted file tree graph

@@               Coverage Diff                @@
##             8.0.x     #16074         +/-   ##
================================================
+ Coverage         0   51.8572%   +51.8572%     
- Complexity       0      18112      +18112     
================================================
  Files            0       2046       +2046     
  Lines            0      96274      +96274     
  Branches         0      16727      +16727     
================================================
+ Hits             0      49925      +49925     
- Misses           0      38980      +38980     
- Partials         0       7369       +7369     

see 2046 files with indirect coverage changes

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
  • 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

@jdaugherty
jdaugherty merged commit 2e2ce06 into 8.0.x Aug 1, 2026
62 of 63 checks passed
@jdaugherty
jdaugherty deleted the issues-16060-Upgrade-docs-mixed-up-version-numbers branch August 1, 2026 21:45
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

Status: Done

Development

Successfully merging this pull request may close these issues.

2 participants