jamesfredley commented on code in PR #380: URL: https://github.com/apache/grails-static-website/pull/380#discussion_r2261685286
########## posts/2025-08-10-grails-7-rc1.md: ########## @@ -0,0 +1,250 @@ +--- +version: 7.0.0-RC1 +priorVersion: 7.0.0-M5 +title: Apache Grails (Incubating) [%version] - Release Announcement +date: July 10, 2025 +description: The Apache Grails (incubating) community is excited to announce the Milestone [%version] release of the Grails Framework! +author: James Fredley +image: grails-blog-index-3.png + +--- + +# [%title] + +[%author] + +[%date] + +[%description] \ +We encourage you to try this pre-release version and provide your feedback [here](https://github.com/apache/grails-core/issues). + +## Download Source Code and Binary Distributions + +[Apache Grails Downloads](/download.html) + +## What's Changed +For changes made in Grails 7 prior to [%version], check out the following blog posts: +* [Grails 7.0.0-M1](/blog/2024-12-23-grails-7-m1.html) +* [Grails 7.0.0-M3](/blog/2025-03-05-grails-7-m3.html) +* [Grails 7.0.0-M4](/blog/2025-06-10-grails-7-m4.html) +* [Grails 7.0.0-M5](/blog/2025-07-15-grails-7-m5.html) + +### [%version] Changes: +* Add permissions to release environments by @jdaugherty in #14795 +* Asset plugin forking compiler @jdaugherty (#14948) +* Update base, web and rest-api profiles to more closely match Forge @jamesfredley (#14942) +* #14886 - add licensing to distributed shadowJar @jdaugherty (#14945) +* Add non-default, optional virtual thread feature to Forge for Java 24+ @jamesfredley (#14941) +* remove: pdf publishing due to licensing issues & no longer using inside of Grails documentation @jdaugherty (#14940) +* Update to spring-boot 3.5.4 & groovy 4.0.28 @jamesfredley (#14934) +* feature: add grails-dependency proposal @jdaugherty (#14924) +* Enhance CreateReleaseDropDownTask so it can be reused by grails-spring-security @jamesfredley (#14929) +* remove old asm & AnnotationMetadataReader supporting classes; adopt SimpleMetadataReaderFactory @jdaugherty (#14922) +* Set spring boot dev tools as a default feature in forge to match profiles @jamesfredley (#14921) +* Use version variables + minor copy and formatting adjustments @jamesfredley (#14908) +* Dependency minor/patch version updates before 7.0.0-RC1 @jamesfredley (#14909) +* Fix build performance issues @jprinet (#14895) +* Merge 7.0.0 m5 release tag @jamesfredley (#14907) +* Enhance documentation for grails-shell vs grails-forge CLIs, plus Gra… @jamesfredley (#14906) +* Add version support message for IntelliJ Grails Plugin @jamesfredley (#14905) +* Update GitHub repository homepage URL @jamesfredley (#14902) +* Deprecated Removals @jdaugherty (#14901) +* Fix snapshot docs URL, currently only appears on snapshot docs @jamesfredley (#14900) +* Restore Sitemesh3GrailsPlugin @jdaugherty (#14891) +* Wrapper Improvements found by M5 Release @jdaugherty (#14896) +* Fix issue reported by GitHub CodeQL @matrei (#14936) +* fix: #14918 adjust the class loader used for command loading to ensure the delegating cli can find all commands @jdaugherty (#14926) +* fix: #14910 - make property files reproducible by default (per day) @jdaugherty (#14919) +* fix: issues found by M5 release verification @jdaugherty (#14904) +* fix: #13705 - revert changes to Metadata from micronaut removal @jdaugherty (#14897) +* fix: #13668 - update for SpringBoot resource split into subclass @jdaugherty (#14888) +* #14930 - make views reproducible by sorting views always @jdaugherty (#14946) +* build(deps): bump google-github-actions/auth from 2.1.10 to 2.1.11 @dependabot[bot] (#14939) +* build(deps): bump google-github-actions/setup-gcloud from 2.1.4 to 2.1.5 @dependabot[bot] (#14938) +* fix: #14910 - make property files reproducible by default (per day) @jdaugherty (#14919) +* doc: #14892 - update RELEASE.md for workflow changes and grails-forge repo merge @jdaugherty (#14893) +* fix: #13705 - revert changes to Metadata from micronaut removal @jdaugherty (#14897) + +Full Changelog: [v[%priorVersion]...v[%version]](https://github.com/apache/grails-core/compare/v[%priorVersion]...v[%version]) + +Upgrade instructions are available in the [documentation](https://docs.grails.org/[%version]/guide/single.html#upgrading60x). + +## Dependency Upgrades +In this release, we've upgraded several dependency versions, including but not limited to the following: + +* Asset Pipeline 5.0.12 (now cloud.wondrify.asset-pipeline) +* Groovy 4.0.28 +* Spring Framework 6.2.9 +* Spring Boot 3.5.4 +* Gradle 8.14.3 +* See all in the [grails-bom](https://docs.grails.org/[%version]/ref/Versions/Grails%20BOM.html). + +## Generating a new Grails [%version] application with Grails Forge +Try out Grails today by visiting our online application generator [Grails Forge](https://start.grails.org/). This is the quickest and the recommended way to get started with Grails. + +After installing JetBrains' IntelliJ IDEA 2025.2 or later and the [Grails Plugin](https://plugins.jetbrains.com/plugin/18504-grails), the Grails Application Forge will also be available under New Project in IntelliJ IDEA. + +Within your newly generated project you can access the Grails CLIs with the grails wrapper + +See [Types of CLI](https://docs.grails.org/[%version]/guide/gettingStarted.html#downloadingAndInstalling) for details on each CLI + +grail-shell-cli + +```shell +grailsw +``` + +grails-forge-cli + +```shell +grailsw -t forge +``` + +## Installing Grails CLIs [%version] with SDKMan +Alternatively, you can quickly install Grails [%version] CLIs (grails-shell-cli and grails-forge-cli) using [SDKMan](https://sdkman.io/). + +See [Types of CLI](https://docs.grails.org/[%version]/guide/gettingStarted.html#downloadingAndInstalling) for details on each CLI + +1. If you don't have SDKMan installed, follow the instructions at [SDKMan Installation Guide](https://sdkman.io/install/) + to set it up. +2. Once SDKMan is installed, open your terminal and run the following command to install Grails [%version]: + + ```shell + sdk install grails [%version] + ``` + +3. You're all set! To verify the installation, run: + + ```shell + grails --version + ``` + +The Grails Shell CLI can be accessed as: + +```shell +grails +``` +or +```shell +grails-shell-cli +``` +The Grails Forge CLI can be accessed as: +```shell +grails -t forge +``` +or +```shell +grails-forge-cli +``` + +## Upgrading Your Existing Applications to Grails [%version] +If you already have a Grails application and want to upgrade to the latest version, follow these steps: + +1. Open the project in your favorite IDE (preferably JetBrains' IntelliJ IDEA 2025.2 or later). +2. Update your application's `gradle.properties` file to specify Grails [%version] as the desired version. + + ```properties + grailsVersion=[%version] + ``` + +3. Make any necessary adjustments to your application code, configuration, and dependencies to ensure compatibility with + the new version. [See Upgrade Guide](https://docs.grails.org/[%version]/guide/single.html#upgrading60x) + +Normally, Grails Core dependencies are automatically updated using the Grails Bill of Materials (BOM). However, if you +have specific versions defined in your build configuration, you may need to manually update them to align with +Grails [%version]. + +By following these steps, you should be able to transition your existing Grails application to Grails [%version]. + +### Exploring Alternative Approaches +If manual dependency updates seem daunting, or you want a more streamlined approach, consider the following alternatives: + +#### 1. Use Grails Forge Website +Visit [Grails Forge](https://start.grails.org) and generate a new Grails application with Grails [%version]. Compare the +versions in the newly generated application with your existing one to identify any discrepancies. This can serve as a +reference point for your update. + +#### 2. Automated Dependency Update Bots +Configure automated dependency update bots like [Renovate](https://docs.renovatebot.com/) or +[Dependabot](https://dependabot.com/) with your source control platform (e.g., GitHub). These bots can automatically Review Comment: With the slash is technically correct, since without the slash is missing the path portion of the URL, but both render as URLs in the html and the browser makes it work the same. I am committing this change given it does look better to the eyes. **devtools shows the appended slash** <img width="1147" height="258" alt="image" src="https://github.com/user-attachments/assets/e721e54f-925f-4f3e-827f-0a369247afab"; /> **chrome hides the slash in the URL bar too** <img width="1543" height="168" alt="image" src="https://github.com/user-attachments/assets/a07d68fa-7b98-426c-9944-b92dfe9cc6d8"; /> -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@grails.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
