File tree Expand file tree Collapse file tree 1 file changed +22
-0
lines changed Expand file tree Collapse file tree 1 file changed +22
-0
lines changed Original file line number Diff line number Diff line change @@ -1228,6 +1228,28 @@ can’t apply the usual defaulting rules.)</para>
12281228<revhistory >
12291229<?db revhistory-style =" list" ?>
12301230<revision >
1231+ <revnumber >6.0.14</revnumber >
1232+ <date >2025-03-13</date >
1233+ <revdescription >
1234+ <itemizedlist >
1235+ <listitem >
1236+ <para >Fixed <link xlink : href =" https://github.com/xmlresolver/xmlresolver/issues/229" >#229</link >.
1237+ The interaction between the “always resolve” feature and namespace URI lookup
1238+ had the unfortunate consequence of returning the (almost always incorrect)
1239+ document at the namespace URI as the resource. I’ve adjusted the API so that
1240+ this is no longer the case. It’s now possible to configure “always resolve” on
1241+ a per-request basis. This changes an interface so it’s not binary backwards
1242+ compatible with previous 6.x releases.</para >
1243+ </listitem >
1244+ <listitem >
1245+ <para >Fixed <link xlink : href =" https://github.com/xmlresolver/xmlresolver/issues/230" >#230</link >.
1246+ When “always resolve” returned a resource, that URI wasn’t being logged which
1247+ lead to a confusing log trace.</para >
1248+ </listitem >
1249+ </itemizedlist >
1250+ </revdescription >
1251+ </revision >
1252+ <revision >
12311253<revnumber >6.0.13</revnumber >
12321254<date >2025-03-10</date >
12331255<revdescription >
You can’t perform that action at this time.
0 commit comments