4.31.0 release note meta data update

liquibase · Feb 6, 2025 · f4debc4 · f4debc4
1 parent e5fbc36
commit f4debc4
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/Content/start/release-notes/liquibase-release-notes/liquibase-4.31.0.htm b/Content/start/release-notes/liquibase-release-notes/liquibase-4.31.0.htm
@@ -2,7 +2,7 @@
 <html xmlns:MadCap="http://www.madcapsoftware.com/Schemas/MadCap.xsd" MadCap:searchable="False">
     <head><title><MadCap:variable name="Heading.Level1" /></title>
         <link rel="canonical" href="https://docs.liquibase.com/start/release-notes/liquibase-release-notes/liquibase-4.30.0.html" />
-        <meta name="description" content="Liquibase 4.30.0 release notes." />
+        <meta name="description" content="Liquibase 4.31.0 release notes." />
         <meta name="viewport" content="width=device-width, initial-scale=1" />
     </head>
     <body>
@@ -19,7 +19,7 @@ <h2>UPDATE: Reported Problems with LogicalFilePath February 6, 2025</h2>
         <h3>The Bug</h3>
         <p>The standard Liquibase practice is to accept the attribute closest to the changeset. But in 4.31.0, the parent <code>logicalfilepath</code> value will be used in DBCL/DBCLH as the <code>changelogfilepath</code> value.</p>
         <h3>What's Next?</h3>
-        <p class="warning" MadCap:autonum="&lt;b&gt;Warning: &lt;/b&gt;">If your workflow meets the conditions mentioned above, please avoid upgrading to version 4.31.0. The issue will be resolved in the upcoming 4.31.1 release.</p>
+        <p class="warning">If your workflow meets the conditions mentioned above, please avoid upgrading to version 4.31.0. The issue will be resolved in the upcoming 4.31.1 release.</p>
         <p class="note" MadCap:autonum="&lt;b&gt;Note: &lt;/b&gt;"><MadCap:variable name="General.Liquibase" /> 4.31.0 contains an expanded Checks Extension, and so the artifact size has increased.</p>
         <h2>Breaking Change</h2>
         <p><b>Changesets with entirely blank IDs will now fail validation.</b> This change improves the reliability and diagnosability of database changes, and enforces the best practices specified in documentation and training.</p>