dependabot[bot] opened a new pull request, #45:
URL: https://github.com/apache/grails-intellij-plugin/pull/45

   Bumps [org.grails:grails-plugin-gsp](https://github.com/grails/grails-core) 
from 2.0.0.RC1 to 3.2.12.
   <details>
   <summary>Changelog</summary>
   <p><em>Sourced from <a 
href="https://github.com/apache/grails-core/blob/8.0.x/RELEASE.md";>org.grails:grails-plugin-gsp's
 changelog</a>.</em></p>
   <blockquote>
   <!-- raw HTML omitted -->
   <h1>Apache Grails Release Process</h1>
   <p>This document outlines the steps to release a new version of Apache 
Grails. It is important to follow these steps
   carefully to ensure a smooth release process. The release process can be 
divided into 4 stages across the <code>grails-core</code>
   repository. The history &amp; requirements of our release setup can be found
   in <a 
href="https://github.com/apache/grails-core/blob/8.0.x/#appendix-release-setup-requirements--history";>Appendix:
 Release Setup Requirements &amp; History</a>.</p>
   <h2>Prerequisites</h2>
   <p>Prior to starting the release process, ensure that any other dependent 
library is set to a non-snapshot version in <code>dependencies.gradle</code>. 
Per the <a href="https://www.apache.org/legal/release-policy.html";>Apache 
Release Policy</a>, all dependencies must be official releases and cannot be 
snapshots. The build will fail if any snapshot dependencies are present. The 
verification process will also now check for SNAPSHOT versions. Additionally, 
<code>./gradlew validateDependencyVersions</code> is run during the release 
workflow and verification to ensure all BOM dependency versions resolve 
correctly.</p>
   <p>Due to a limitation with GitHub, private groups cannot be used as 
approvers for an environment.  For this reason, prior to performing the 
release, add GitHub username to asf.yaml in the environment section for 
approvers. Only 6 approvers may exist on a given environment.</p>
   <h2>1. Staging</h2>
   <p>During the staging step, we must create a source distribution &amp; stage 
any binary artifacts that end users will consume.</p>
   <ol>
   <li>Create a release in <code>grails-core</code>:
   <ul>
   <li>Click &quot;Draft a new release&quot; here: <a 
href="https://github.com/apache/grails-core/releases";>https://github.com/apache/grails-core/releases</a></li>
   <li>On the draft new release screen, we execute the following steps:
   <ul>
   <li>The tag will have the prefix 'v', so for our release it would be 
'v7.0.0-M4'</li>
   <li>The &quot;Target&quot; will be the branch we build out of (this case 
it's the default, 7.0.x)</li>
   <li>Previous tag will be auto</li>
   <li>Click &quot;Generate Release Notes&quot;
   <ul>
   <li>This will then scan our commit history and we adjust the release notes 
per project agreement.</li>
   </ul>
   </li>
   <li>Check &quot;pre-release&quot;</li>
   <li>Click &quot;Publish Release&quot;</li>
   </ul>
   </li>
   </ul>
   </li>
   <li>The Github workflow from <code>release.yml</code>, titled 
<code>Release</code>, will kick off. This workflow contains many jobs. The 
first 3 jobs will run without delay.  Further jobs, require approval to 
proceed.</li>
   <li>(no approval required) The <code>publish</code> job will:
   <ul>
   <li>checkout the project</li>
   <li>setup gradle</li>
   <li>extract the version # from the tag</li>
   <li>run the pre-release workflow (updates gradle.properties to be the 
version specified by the user)</li>
   <li>extract signing secrets from github action variables</li>
   </ul>
   </li>
   </ol>
   <!-- raw HTML omitted -->
   </blockquote>
   <p>... (truncated)</p>
   </details>
   <details>
   <summary>Commits</summary>
   <ul>
   <li><a 
href="https://github.com/apache/grails-core/commit/8f35326c9dfd364dd6b7a160368672771cf9610e";><code>8f35326</code></a>
 Set version to 3.2.12</li>
   <li><a 
href="https://github.com/apache/grails-core/commit/ed30f181cd866e2e1dae3fcf9625083f181f88d5";><code>ed30f18</code></a>
 Merge pull request <a 
href="https://redirect.github.com/grails/grails-core/issues/10852";>#10852</a> 
from davydotcom/patch-osx-filewatcher</li>
   <li><a 
href="https://github.com/apache/grails-core/commit/b298f089cdb1f87b50093a3bbe97637016a68314";><code>b298f08</code></a>
 Use updated version of grails-java8</li>
   <li><a 
href="https://github.com/apache/grails-core/commit/17a828ccde0de2413844bc57eb8cde1946f7916a";><code>17a828c</code></a>
 changing scope to agent scope for directory watcher</li>
   <li><a 
href="https://github.com/apache/grails-core/commit/102868f45561a9505acd76fa8e46503e08b96433";><code>102868f</code></a>
 Merge pull request <a 
href="https://redirect.github.com/grails/grails-core/issues/10872";>#10872</a> 
from grails/open-test-report</li>
   <li><a 
href="https://github.com/apache/grails-core/commit/f86b733621972dfe3015b76f376bfcda372ace1f";><code>f86b733</code></a>
 Fix path to tests</li>
   <li><a 
href="https://github.com/apache/grails-core/commit/56b517510a85ca4eb6c6ece8aef1dea4c5fca1fa";><code>56b5175</code></a>
 moving directory-watcher dependency to bom and loads onto classpath on 
bootRu...</li>
   <li><a 
href="https://github.com/apache/grails-core/commit/339595feef6e2d1d1068964a44c2c22ea9d1ff81";><code>339595f</code></a>
 With the work done by <a 
href="https://github.com/erichelgeson";><code>@​erichelgeson</code></a> we now 
have native OS X File Watching ser...</li>
   <li><a 
href="https://github.com/apache/grails-core/commit/39b825960c15cab17936e2d6fd944c1ce4396d30";><code>39b8259</code></a>
 Add PdfPublisher test</li>
   <li><a 
href="https://github.com/apache/grails-core/commit/4f1b5913a05faebb746e4823ebef481635ad47f5";><code>4f1b591</code></a>
 Fix PdfBuilder test</li>
   <li>Additional commits viewable in <a 
href="https://github.com/grails/grails-core/compare/v2.0.0.RC1...v3.2.12";>compare
 view</a></li>
   </ul>
   </details>
   <br />
   
   
   [![Dependabot compatibility 
score](https://dependabot-badges.githubapp.com/badges/compatibility_score?dependency-name=org.grails:grails-plugin-gsp&package-manager=gradle&previous-version=2.0.0.RC1&new-version=3.2.12)](https://docs.github.com/en/github/managing-security-vulnerabilities/about-dependabot-security-updates#about-compatibility-scores)
   
   Dependabot will resolve any conflicts with this PR as long as you don't 
alter it yourself. You can also trigger a rebase manually by commenting 
`@dependabot rebase`.
   
   [//]: # (dependabot-automerge-start)
   [//]: # (dependabot-automerge-end)
   
   ---
   
   <details>
   <summary>Dependabot commands and options</summary>
   <br />
   
   You can trigger Dependabot actions by commenting on this PR:
   - `@dependabot rebase` will rebase this PR
   - `@dependabot recreate` will recreate this PR, overwriting any edits that 
have been made to it
   - `@dependabot show <dependency name> ignore conditions` will show all of 
the ignore conditions of the specified dependency
   - `@dependabot ignore this major version` will close this PR and stop 
Dependabot creating any more for this major version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this minor version` will close this PR and stop 
Dependabot creating any more for this minor version (unless you reopen the PR 
or upgrade to it yourself)
   - `@dependabot ignore this dependency` will close this PR and stop 
Dependabot creating any more for this dependency (unless you reopen the PR or 
upgrade to it yourself)
   
   
   </details>


-- 
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: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to