<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Deprecation on ads' corner</title><link>https://andreas.scherbaum.la/tags/deprecation/</link><description>Recent content in Deprecation on ads' corner</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Fri, 09 May 2025 00:00:00 +0200</lastBuildDate><atom:link href="https://andreas.scherbaum.la/tags/deprecation/index.xml" rel="self" type="application/rss+xml"/><item><title>ERROR deprecated: site config key paginate was deprecated in Hugo v0.128.0 and subsequently removed. Use pagination.pagerSize instead.</title><link>https://andreas.scherbaum.la/post/2025-05-09_error-deprecated-site-config-key-paginate-was-deprecated-in-hugo-v0-128-0-and-subsequently-removed-use-pagination-pagersize-instead/</link><pubDate>Fri, 09 May 2025 00:00:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2025-05-09_error-deprecated-site-config-key-paginate-was-deprecated-in-hugo-v0-128-0-and-subsequently-removed-use-pagination-pagersize-instead/</guid><description>&lt;p&gt;While upgrading my &lt;em&gt;Arch&lt;/em&gt;/&lt;em&gt;Manjaro&lt;/em&gt; system I got &lt;em&gt;Hugo&lt;/em&gt; upgraded to version &lt;code&gt;0.128.0&lt;/code&gt; - and ran into yet another deprecated feature. This time a config option will go soon: &lt;code&gt;paginate&lt;/code&gt;, and replaced by a different option.&lt;/p&gt;&#10;&lt;p&gt;I can&amp;rsquo;t deploy the change right away, the setting is not yet supported on the LTS version on the webserver. But I can deal with it locally.&lt;/p&gt;&#10;&lt;p&gt;Te error message in question:&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;div style="background-color:#f7f7f7;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&#10;&lt;table style="border-spacing:0;padding:0;margin:0;border:0;"&gt;&lt;tr&gt;&lt;td style="vertical-align:top;padding:0;margin:0;border:0;"&gt;&#10;&lt;pre tabindex="0" style="background-color:#f7f7f7;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;1&#10;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&#10;&lt;td style="vertical-align:top;padding:0;margin:0;border:0;;width:100%"&gt;&#10;&lt;pre tabindex="0" style="background-color:#f7f7f7;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;ERROR deprecated: site config key paginate was deprecated in Hugo v0.128.0 and subsequently removed. Use pagination.pagerSize instead.&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;&#10;&lt;/div&gt;&#10;&lt;/div&gt;&lt;p&gt;The change is easy, change the following in &lt;code&gt;config.toml&lt;/code&gt; (or whichever config format you are using). From:&lt;/p&gt;</description></item><item><title>WARN deprecated: resources.ToCSS was deprecated in Hugo v0.128.0 and will be removed in a future release. Use css.Sass instead</title><link>https://andreas.scherbaum.la/post/2025-05-08_warn-deprecated-resources-tocss-was-deprecated-in-hugo-v0-128-0-and-will-be-removed-in-a-future-release-use-css-sass-instead/</link><pubDate>Thu, 08 May 2025 00:00:00 +0200</pubDate><guid>https://andreas.scherbaum.la/post/2025-05-08_warn-deprecated-resources-tocss-was-deprecated-in-hugo-v0-128-0-and-will-be-removed-in-a-future-release-use-css-sass-instead/</guid><description>&lt;p&gt;While upgrading my &lt;em&gt;Arch&lt;/em&gt;/&lt;em&gt;Manjaro&lt;/em&gt; system I got &lt;em&gt;Hugo&lt;/em&gt; upgraded to version &lt;code&gt;0.128.0&lt;/code&gt;. It comes with a number of new features - and of course also some deprecations. One of the features going away is &lt;code&gt;resources.ToCSS&lt;/code&gt;, or rather it is renamed. I&amp;rsquo;m using - or used - this in my code for &lt;a href="https://andreas.scherbaum.la/post/2024-05-23_client-side-comments-with-mastodon-on-a-static-hugo-website/"&gt;Mastodon comments&lt;/a&gt;.&lt;/p&gt;&#10;&lt;div class="highlight"&gt;&lt;div style="background-color:#f7f7f7;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&#10;&lt;table style="border-spacing:0;padding:0;margin:0;border:0;"&gt;&lt;tr&gt;&lt;td style="vertical-align:top;padding:0;margin:0;border:0;"&gt;&#10;&lt;pre tabindex="0" style="background-color:#f7f7f7;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;1&#10;&lt;/span&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;2&#10;&lt;/span&gt;&lt;span style="white-space:pre;-webkit-user-select:none;user-select:none;margin-right:0.4em;padding:0 0.4em 0 0.4em;color:#7f7f7f"&gt;3&#10;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&#10;&lt;td style="vertical-align:top;padding:0;margin:0;border:0;;width:100%"&gt;&#10;&lt;pre tabindex="0" style="background-color:#f7f7f7;-moz-tab-size:4;-o-tab-size:4;tab-size:4;-webkit-text-size-adjust:none;"&gt;&lt;code class="language-text" data-lang="text"&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;{{ $comments := resources.Get &amp;#34;css/comments.scss&amp;#34; }}&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;{{ $style := $comments | resources.ToCSS | resources.Fingerprint }}&#10;&lt;/span&gt;&lt;/span&gt;&lt;span style="display:flex;"&gt;&lt;span&gt;&amp;lt;link rel=&amp;#34;stylesheet&amp;#34; href=&amp;#34;{{ $style.Permalink }}&amp;#34; integrity=&amp;#34;{{ $style.Data.Integrity }}&amp;#34;&amp;gt;&#10;&lt;/span&gt;&lt;/span&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/table&gt;&#10;&lt;/div&gt;&#10;&lt;/div&gt;&lt;p&gt;The error message coming from the deprecated &lt;code&gt;resources.ToCSS&lt;/code&gt; is:&lt;/p&gt;</description></item><item><title>ERROR deprecated: data.GetJSON was deprecated in Hugo v0.123.0 and will be removed in Hugo 0.140.0. use resources.Get or resources.GetRemote with transform.Unmarshal</title><link>https://andreas.scherbaum.la/post/2025-03-20_error-deprecated-data-getjson-was-deprecated-in-hugo-v0-123-0-and-will-be-removed-in-hugo-0-140-0-use-resources-get-or-resources-getremote-with-transform-unmarshal/</link><pubDate>Thu, 20 Mar 2025 00:00:00 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2025-03-20_error-deprecated-data-getjson-was-deprecated-in-hugo-v0-123-0-and-will-be-removed-in-hugo-0-140-0-use-resources-get-or-resources-getremote-with-transform-unmarshal/</guid><description>&lt;p&gt;Every &lt;em&gt;goHugo&lt;/em&gt; update brings new surprises, most daring are the deprecated features which are now removed. This time I ran into the deprecated &lt;code&gt;data.GetJSON&lt;/code&gt; feature which was removed.&lt;/p&gt;&#10;&lt;p&gt;Occasionally removing features breaks my blogging workflow: my laptop is a rolling distribution, and keeps software mostly up to date. This means I have the latest and greatest running. The webserver however is running on LTS, which is lagging a bit behind in terms of software versions. What is working on the webserver is no longer working on my laptop. Worst case, the fix for the deprecated feature is not even working on the LTS version. But that&amp;rsquo;s life.&lt;/p&gt;</description></item><item><title>GitHub Actions: Node.js 12 actions are deprecated</title><link>https://andreas.scherbaum.la/post/2023-01-13_github-actions-node.js-12-actions-are-deprecated/</link><pubDate>Fri, 13 Jan 2023 16:42:00 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2023-01-13_github-actions-node.js-12-actions-are-deprecated/</guid><description>&lt;p&gt;If you use &lt;a href="https://github.com/features/actions"&gt;GitHub Actions&lt;/a&gt; to run Workflows and tests, you might have spotted this warning recently:&lt;/p&gt;</description></item><item><title>GitHub Actions: The `set-output` command is deprecated and will be disabled soon</title><link>https://andreas.scherbaum.la/post/2023-01-10_github-actions-the-set-output-command-is-deprecated-and-will-be-disabled-soon/</link><pubDate>Tue, 10 Jan 2023 13:42:00 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2023-01-10_github-actions-the-set-output-command-is-deprecated-and-will-be-disabled-soon/</guid><description>&lt;p&gt;If you use &lt;a href="https://github.com/features/actions"&gt;GitHub Actions&lt;/a&gt; to run Workflows and tests, you might have spotted this warning recently:&lt;/p&gt;</description></item><item><title>Ansible: Use errors="ignore" instead of skip</title><link>https://andreas.scherbaum.la/post/2020-02-24_ansible-use-errorsignore-instead-of-skip/</link><pubDate>Mon, 24 Feb 2020 02:44:00 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2020-02-24_ansible-use-errorsignore-instead-of-skip/</guid><description>&lt;p&gt;Another &lt;em&gt;Ansible&lt;/em&gt; upgrade deprecation warning, which appears in &lt;em&gt;Ansible&lt;/em&gt; 2.8:&lt;/p&gt;</description></item><item><title>_ansible_item_label changes in Ansible 2.8</title><link>https://andreas.scherbaum.la/post/2020-02-20__ansible_item_label-changes-in-ansible-2.8/</link><pubDate>Thu, 20 Feb 2020 22:03:00 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2020-02-20__ansible_item_label-changes-in-ansible-2.8/</guid><description>&lt;p&gt;The &lt;a href="https://www.ansible.com/"&gt;Ansible&lt;/a&gt; 2.8 upgrade brought a few failing Playbooks. I ran into the following error:&lt;/p&gt;</description></item><item><title>Ansible: TRANSFORM_INVALID_GROUP_CHARS deprecation warning</title><link>https://andreas.scherbaum.la/post/2020-01-25_ansible-transform_invalid_group_chars-deprecation-warning/</link><pubDate>Sat, 25 Jan 2020 16:39:00 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2020-01-25_ansible-transform_invalid_group_chars-deprecation-warning/</guid><description>&lt;p&gt;After upgrading &lt;a href="https://www.ansible.com/"&gt;Ansible&lt;/a&gt; to version 2.8.3, the following deprecation warning appeared many times:&lt;/p&gt;</description></item><item><title>Ansible: "apt" module and loops</title><link>https://andreas.scherbaum.la/post/2020-01-20_ansible-apt-module-and-loops/</link><pubDate>Mon, 20 Jan 2020 22:28:00 +0100</pubDate><guid>https://andreas.scherbaum.la/post/2020-01-20_ansible-apt-module-and-loops/</guid><description>&lt;p&gt;After upgrading &lt;a href="https://www.ansible.com/"&gt;Ansible&lt;/a&gt; to version 2.8.3, the &amp;ldquo;&lt;a href="https://docs.ansible.com/ansible/latest/modules/apt_module.html"&gt;apt&lt;/a&gt;&amp;rdquo; module started spitting out deprecation warnings:&lt;/p&gt;</description></item></channel></rss>